> For the complete documentation index, see [llms.txt](https://docs.hollaex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hollaex.com/plugins/develop-plugins/advanced/final-plugin-product.md).

# Final Plugin Product

The final product of your plugin is a JSON file that can easily be [installed](/plugins/installing-plugin.md) in HollaEx Kit in the exchange operator controls, following the third-party plugin installation process. 

This JSON file includes all the information required for the plugin to run on the server. Once installed on your exchange, the server runs the script on its backend and loads the web view to smart targets in the web app.

## Final JSON

When you run the plugin in dev mode it automatically builds the plugin JSON so all you need to do is to copy `hello-exchange.json` file in `/plugins/src/plugins/hello-exchange/server/hello-exchange.json` file and [install](/plugins/installing-plugin.md) it to your exchange operator control.

You can find the final hello-exchange plugin below. The final file must be in JSON format.

{% file src="/files/KbXLmKmr9Q1I6TqTfdns" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hollaex.com/plugins/develop-plugins/advanced/final-plugin-product.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.