> For the complete documentation index, see [llms.txt](https://docs.maicrotrader.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maicrotrader.com/3.-how-maicrotrader-works/3.1-strategy-trading-agents-stas.md).

# 3.1 Strategy Trading Agents (STAs)

An STA is a deployed trading vault running on the MAE. Each STA is an independent instance: its own configuration, its own policy hash stored on-chain, its own capital, its own track record.

When a user builds and deploys an STA via the Strategy Builder, they are configuring the policy that governs each of the four sub-agents: which signals the Quant Agent monitors, how the Portfolio Agent manages concentration and rebalancing, what hard limits the Risk Agent enforces, and how the Execution Agent routes trades. That policy is hashed and recorded on-chain at deployment. It cannot be silently changed.

STAs that meet the seasoning requirements, a minimum period of live operation with real capital, can be published to the Permissionless Vault Network, where other users can deposit directly into their strategy.


---

# 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.maicrotrader.com/3.-how-maicrotrader-works/3.1-strategy-trading-agents-stas.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.