> 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/1v1-duels/matchmaking.md).

# Matchmaking & Stakes

## Finding opponents

Three ways to start a duel:

1. **Direct challenge** -- Visit a trader's profile and tap "Challenge." They get a notification and have 5 minutes to accept.
2. **Leaderboard challenge** -- Browse the global leaderboard and challenge anyone within 200 Trader Score points of you.
3. **Post-match rematch** -- After any battle, challenge someone you just competed against.

## Matchmaking queue

If you want a duel but don't have a specific opponent, join the matchmaking queue. The system pairs you with someone close to your Trader Score within a few minutes.

Matchmaking rules:

* Must be within **200 Trader Score points**
* Matched by **similar battle count** when possible
* **Battle Pass holders** get priority in the queue

## Stakes

Both players put up equal credits before the duel starts. The winner takes the combined pot minus a 5% platform fee.

Example:

* Both players stake 500 CR
* Total pot: 1,000 CR
* Platform fee: 50 CR (5%)
* Winner receives: 950 CR

## Decline and timeout

If a challenge isn't accepted within 5 minutes, it expires. Your credits are returned. No penalty for declining a challenge.


---

# 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/1v1-duels/matchmaking.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.