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

# Welcome

Battle Trade is a competitive trading game where you trade crypto on real market prices against real people. No real money at risk. Just skill, strategy, and a leaderboard that doesn't lie.

## The loop

**Learn.** Start with paper money and live price feeds from Pyth Network. Place trades, get wrecked, figure out what went wrong. Repeat.

**Compete.** Join lobbies with other traders. Survive elimination rounds. Use sabotage weapons to mess with the leader. Win.

**Prove.** Every battle builds your Trader Score, a verified track record that follows you everywhere. Top traders unlock verified trader status, where followers mirror your trades and you earn a cut of their profits.

## Why it exists

Trading skill is invisible. You can't prove you're good without risking real money. Battle Trade fixes that. Play for free, build a verified reputation, graduate to real markets when you're ready.

## Start playing

Head to [battle.fyi](https://battle.fyi) and tap **Play Now**. You'll be in a match in under 30 seconds.

No wallet required. No deposit. No sign-up friction.

***

Next: [Your First Battle](/getting-started/first-battle.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.battle.fyi/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.