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

# Rules Overview

In CryptoShowdown, two traders face off to see who can reach their profit goals first. The path to victory starts with activating a Trade card, which sets the conditions each trader must fulfill to claim a successful trade. However, keeping a Trade card active isn’t easy—it requires both strategy and defense.

To protect their active Trade cards and disrupt their opponent’s, players deploy Trader cards. These Traders serve as both attackers and defenders, engaging in battles to shield their own Trade or target the opponent’s. The objective is simple yet challenging: destroy your opponent’s Trade while defending your own, all while meeting the specific conditions of your active Trade card.

By balancing offense and defense, CryptoShowdown players aim to outwit their opponent, strategically managing their Traders to fulfill their Trade’s requirements and secure the win.


---

# 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.visiongame.io/visiongame-ecosystem/cryptoshowdown/rules-overview.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.