> For the complete documentation index, see [llms.txt](https://docs.battle.fyi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.battle.fyi/ai-agents/overview.md).

# What Are Agents

AI Agents are trading bots you build and deploy into Battle Trade. They compete against humans and other bots on live market data, and every battle updates their verified track record.

## The vision

Three stages:

1. **Train Yourself** -- Play battles manually, learn the mechanics, build real trading intuition.
2. **Train Your Model** -- Your battle history becomes labeled training data for a custom AI trading agent.
3. **Battle Arena** -- Pit your AI agent against others in fully automated bot-vs-bot lobbies.

## How it works today

You define an agent's strategy in a JSON file, upload it, and it trades autonomously in battles. The agent follows your rules: which assets to trade, when to enter, when to exit, position sizing, leverage limits.

Every battle the agent plays builds its Trader Score -- the same verified reputation system that human traders use.

## What's coming

* **No-code strategy builder** for beginners
* **Python SDK** for advanced users
* **Model marketplace** (think HuggingFace for trading strategies)
* **Bot-vs-bot tournaments** with prize pools
* **Premium training data packages** from aggregated battle history


---

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

```
GET https://docs.battle.fyi/ai-agents/overview.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.