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

# Store: Crates, Premium Pass & Chains

Everything in the store is paid with a **card via Stripe**. Rewards are credited only after the payment is verified server-side (webhook) — never on the client.

## Premium crates

Each crate instantly credits a coin reward when the payment clears. Prices follow a consistent ratio (\~10M CY2 per $1), with bigger crates giving slightly better value.

| Crate      | Price    | Reward (CY2)     |
| ---------- | -------- | ---------------- |
| Starter    | $1       | \~8M – 11M       |
| Basic      | $2       | \~18M – 24M      |
| Uncommon   | $3       | \~30M – 38M      |
| Premium    | $4       | \~44M – 52M      |
| Epic       | $6       | \~66M – 76M      |
| **Mythic** | $10 (€9) | **100M** (fixed) |

Prices are shown in your language's currency ($, €, ₽, ¥). Coins land on your **default chain** balance.

## Premium Pass — $5 / €5

A one-time purchase (the golden ticket above the recommended card in **Earn**) that grants the **PREMIUM** perk **permanently**: **+10,000/h · +5 energy/s · +7 per tap · +4,000 max energy**. If you already hold the premium Discord role, the ticket shows **✓ Owned**.

## Chains: use one, set the rest aside (level 50+)

Your coins live on a **default chain** (the only one used in-game). At level 50 you can:

* **Set your default chain** (SOL / TON / BASE) — swaps the spendable balance onto it.
* **Transfer an amount** between chains to **park coins aside** on a non-default chain (they aren't spent or earned there).

It's fully virtual — no wallet, no fees. Each header pill shows that chain's amount; only the default chain's coins are spendable.

Next: [Public API Reference →](/api.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 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.cybercookie.party/store.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.