> For the complete documentation index, see [llms.txt](https://peculiar.gitbook.io/odystorm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://peculiar.gitbook.io/odystorm/cards.md).

# Cards

We're bringing social tech where it's meant to be — **gaming**.

Our cards allow holders to benefit by **investing** in ships and earning **yields** from their winnings. There is **no cap** on the number of cards one can purchase. Prices scale according to a **fixed curve**, which is possible due to a pool model employed.

Card ownership provides several **profit avenues**:

1. **Selling** cards as their value appreciates based on player performance.
2. Earning **fees** from card trading.
3. Receiving yield — a portion of the player's **winnings**.

No matter how many cards are issued for a player, they receive **a cut** of their winnings. It is lucrative for players when their cards are traded, as they **earn fees**, their keys **gain value**, and their **$Ody** balance grows.

This system incentivizes players to **excel** so their keys remain desirable. Your performance as a player defines **the value** of your keys, as well as your **popularity**. The social connections formed between **key holders** and **players** create a mutually beneficial ecosystem fueled by shared financial upside.


---

# 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://peculiar.gitbook.io/odystorm/cards.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.