> For the complete documentation index, see [llms.txt](https://aitaprotocol.gitbook.io/aita/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aitaprotocol.gitbook.io/aita/core-concepts/signals-vs-api-execution.md).

# Signals vs API Execution

### Signals vs API Execution

Signals and API execution represent two different ways users can interact with AI agents on AITA.

Both rely on the same underlying agent logic, strategy, and parameters. The difference lies in **how the agent’s outputs are used**.

#### Signals

Signals are informational outputs generated by an agent.

They reflect how the agent interprets market conditions based on its fixed strategy and parameters on the daily timeframe.

With signals:

* No trades are executed automatically
* No exchange accounts are connected
* Agent tokens are required to access and view signals

Signals do **not** require users to commit or connect trading capital.\
They provide informational output only, allowing users to retain full discretion over whether and how to act on the agent’s signals.

#### API Execution

API execution is a mechanism that allows signals to be acted upon automatically through a user-controlled trading account.

With API execution:

* Signals are translated into execution instructions
* Execution occurs on the user’s own account
* The agent’s strategy and logic remain unchanged

API execution changes the method of interaction, not the behavior of the agent.

#### Capital requirements for API execution

API execution requires sufficient capital in the connected account to function correctly.

At present, a **minimum balance of $2,000** is required in the connected account for API execution to operate properly.

If the available balance falls below this minimum:

* Trades may not be executed
* Orders may fail or be partially filled
* The agent’s intended behavior may not be reflected in live execution

Minimum balance requirements are practical constraints of live trading environments and are independent of the agent’s strategy or signal logic. Minimum balance requirements may change over time depending on execution environments and market conditions.

#### Key distinction

The core distinction is control:

* Signals provide information only
* API execution enables action based on that information

Users can choose either approach without modifying the agent itself.

#### Responsibility

In both cases, users remain responsible for:

* Interpreting agent outputs
* Managing risk and capital allocation
* Ensuring execution environments meet minimum requirements

Neither signals nor API execution imply guarantees or predictions of future performance.


---

# 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://aitaprotocol.gitbook.io/aita/core-concepts/signals-vs-api-execution.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.