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

# Subscriptions

Separate purchases that save time — never power. Coming at release.

{% hint style="warning" %}
**Coming at release.** Subscriptions arrive only after Phase 1 and Phase 2. During both test phases the team hands out many speed-ups to everyone so that testing goes fast. See [Phases](https://electrum-decisions.gitbook.io/electrum-decisions-docs/getting-started/phases.md).
{% endhint %}

**The game sells time, never power.** A subscription gives no stronger troops, gear or skills — it gives you more done in the same time.

| Purchase                     | What it gives                                                                                                                                                               |
| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Second construction slot** | Your castle builds **two** things at a time instead of one                                                                                                                  |
| **Second research slot**     | The University researches **two** sciences at a time instead of one                                                                                                         |
| **Both slots**               | A bundle of the second construction slot and the second research slot                                                                                                       |
| **AI connection**            | We provide an AI that plays your account 24/7, the way you set it up. See [AI Agents](https://electrum-decisions.gitbook.io/electrum-decisions-docs/community/ai-agents.md) |

* Each is a **separate purchase** with its own price. Prices are in **euros** and will be published before release. AI connection is planned at about **€25 a month**; shorter periods, such as a day, will also be offered.
* Without a slot, the castle builds one thing at a time and the University researches one science at a time — see [Your Castle](https://electrum-decisions.gitbook.io/electrum-decisions-docs/your-castle/your-castle.md) and [Research](https://electrum-decisions.gitbook.io/electrum-decisions-docs/your-castle/research.md).

## Where you pay

* **Subscriptions** — in the game, through **Google Play** and the **App Store**.
* **Everything Amber** — only on the **website**, because the game apps cannot use crypto. See [Your Wallet](https://electrum-decisions.gitbook.io/electrum-decisions-docs/amber/your-wallet.md).

Speed-ups stay where they are today: see [Castle Quests and Speed-ups](https://electrum-decisions.gitbook.io/electrum-decisions-docs/your-castle/castle-quests-and-speed-ups.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://electrum-decisions.gitbook.io/electrum-decisions-docs/economy/subscriptions.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.
