> 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/api-execution.md).

# API Execution

### API Execution

API execution is an optional interaction model on AITA.

Instead of acting on signals manually, users can choose to have an agent’s signals translated into execution instructions on their own trading account via an API connection.

#### What API execution represents

API execution defines **how signals are acted upon**, not how they are generated.

The agent:

* Evaluates market conditions using its fixed strategy and parameters
* Produces signals on a daily timeframe

API execution:

* Uses those signals as inputs for trade execution
* Does not alter the agent’s strategy, logic, or signal generation

#### Separation of responsibilities

AITA intentionally separates:

* Strategy logic (the agent)
* Signal generation
* Trade execution

This separation ensures that execution is optional and that users retain control over how and whether signals are acted upon.

#### Non-custodial design

API execution does not involve custody of user funds.

Execution occurs through user-controlled accounts, and enabling API execution does not grant AITA ownership or discretionary control over assets.

#### Risk and responsibility

API execution introduces live market exposure.

Users remain fully responsible for:

* The decision to enable execution
* The risks associated with live trading
* Monitoring and managing execution behavior

API execution is a mechanism for acting on signals, not a guarantee of outcomes.


---

# 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/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.