# Using AddOn- and package-indicators in scripted components

When you for example have purchased an AddOn like COT-, Volume-, Rimes,…. you might want to script your individual extensions for that.

Due to technical reasons it is not possible to address those indicators directly e.g. in Scripted Indicators, Strategies or Conditions via Intellisense, as it is possible with the directly integrated system indicators.

But you can use the SignalBuilder to set the correct signature of the respective AddOn indicators in your scripted components.

Therefore please do the following:

1\) Create a pseudo-condition in SignalBuilder with exact those settings as you want to use the respective component in your scripting code and save this condition:

<figure><img src="https://docs.agenatrader.com/~gitbook/image?url=https%3A%2F%2F2805764894-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-legacy-files%2Fo%2Fassets%252F-MKZSsJBtSP9L4sqIe_q%252F-MQuyUOvSDf10S_TO9Zp%252F-MQw372sI7WTG7bQE5_Y%252FPic1.png%3Falt%3Dmedia%26token%3De45b3661-fe8e-4920-90f6-211de7719b3e&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=b8ecc37e&#x26;sv=1" alt=""><figcaption></figcaption></figure>

2\) Switch to your usercode file in the Scanns-folder and open the condition with the notepad-editor:

<figure><img src="https://docs.agenatrader.com/~gitbook/image?url=https%3A%2F%2F2805764894-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-legacy-files%2Fo%2Fassets%252F-MKZSsJBtSP9L4sqIe_q%252F-MQuyUOvSDf10S_TO9Zp%252F-MQw3BCrB8GVggLdlPJB%252Fpic2.png%3Falt%3Dmedia%26token%3Ddcfa10de-bade-4273-8087-4f90d912a198&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=bb8e9297&#x26;sv=1" alt=""><figcaption></figcaption></figure>

3\) Select and copy the indicator signature from the condition:

<figure><img src="https://docs.agenatrader.com/~gitbook/image?url=https%3A%2F%2F2805764894-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-legacy-files%2Fo%2Fassets%252F-MKZSsJBtSP9L4sqIe_q%252F-MQuyUOvSDf10S_TO9Zp%252F-MQw3I_G5ymXiN-WzObj%252Fpic3.png%3Falt%3Dmedia%26token%3D6211b4d1-9e8f-487a-8d8a-d9879f7c76d9&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=d2f05dd0&#x26;sv=1" alt=""><figcaption></figcaption></figure>

4\) Now add it to the scripting environment where you want to script your own component:

<figure><img src="https://docs.agenatrader.com/~gitbook/image?url=https%3A%2F%2F2805764894-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-legacy-files%2Fo%2Fassets%252F-MKZSsJBtSP9L4sqIe_q%252F-MQuyUOvSDf10S_TO9Zp%252F-MQw3OdRd3F-f4mIJuj3%252Fpic4.png%3Falt%3Dmedia%26token%3D97743896-e8d2-4073-bd8b-fcc6a2000091&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=d2ac8338&#x26;sv=1" alt=""><figcaption></figcaption></figure>

<br>


---

# Agent Instructions: 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:

```
GET https://docs.agenatrader.com/package/using-addon-and-package-indicators-in-scripted-components.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
