> 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/marketplace/monitoring-performance.md).

# Monitoring Performance

### Monitoring Performance

Monitoring performance allows you to understand how an agent behaves over time and how its strategy responds to changing market conditions.

This applies whether you:

* Follow an agent for signals
* Use API execution for automation
* Are the creator of the agent

Performance monitoring is observational and informational. It does not imply optimization or prediction.

#### What performance data represents

All performance data shown on AITA is historical.

It reflects:

* How the agent’s fixed strategy behaved under past market conditions
* The outcomes of decisions made by that strategy
* The cumulative effects of wins, losses, and drawdowns over time

Performance data does not change the agent’s behavior and does not adapt or optimize the strategy.

#### Key things to monitor

When reviewing an agent’s performance, focus on:

* Consistency rather than isolated results
* Behavior during different market regimes
* Drawdowns and recovery patterns
* Stability of results over time

Short-term fluctuations are expected and should always be interpreted in context.

#### Performance for signal users

If you follow an agent for signals only:

* Performance metrics help you evaluate whether the strategy aligns with your expectations
* Signals reflect the same strategy used to generate historical results
* You remain fully responsible for execution and risk management

Performance monitoring helps you decide whether to continue following an agent.

#### Performance for API users

If you use API execution:

* Performance metrics help you track how the agent interacts with live markets
* Results may differ from historical backtests due to slippage, fees, and execution timing
* Sufficient balance is required for proper execution

API users should regularly monitor performance to ensure the setup behaves as expected.

#### Comparing agents over time

AITA allows you to compare agents using consistent metrics.

Comparisons can help you:

* Understand how different strategies respond to similar conditions
* Observe relative stability or volatility
* Identify long-term behavioral differences

Comparisons are descriptive tools, not recommendations.

#### What performance monitoring is not

Performance monitoring does not:

* Predict future outcomes
* Guarantee profitability
* Adjust or optimize strategies automatically
* Replace individual judgment or risk assessment

All metrics are historical and informational only.

#### Responsibility and interpretation

You are responsible for how you interpret and act on performance data.

AITA provides transparency and structure, but:

* Does not provide financial advice
* Does not manage your capital
* Does not intervene in agent behavior

Performance monitoring should always be combined with your own understanding of risk and market dynamics.


---

# 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/marketplace/monitoring-performance.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.
