> For the complete documentation index, see [llms.txt](https://usermanual.ergonode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usermanual.ergonode.com/system/your-plan.md).

# Your plan

See your plan's usage of AI credits, products, automations and users against its limits, and how AI credits are counted.

The ***Plan usage*** section shows how much of each resource you use and how much your plan includes: ***AI Credits*** (monthly AI usage for content generation, image generation and translation), ***Products***, ***Automations***, ***Users*** (active users) and ***Storage space***. The ***Ergonode Plans*** button opens the Ergonode pricing page in a new tab.

<figure><img src="https://171427267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9BbYBbDPiJapb75xJ2k%2Fuploads%2FGU2rX33HFXhLJBzFmKic%2Fee92f4ce5dde.png?alt=media&amp;token=0a4bd977-3c07-46f1-988b-3611a7be2b7e" alt=""><figcaption></figcaption></figure>

### How we count the AI usage

Any operation, based on one so-called atom, requires one credit. An atom is a single resource used. This means 1 change in 1 product, in 1 language, in 1 attribute, counts as one credit.

**Examples:**

* Creating a description in a single attribute for one product uses 1 credit.
* Creating a description in a single attribute for two products uses 2 credits.
* Translating 10 options in a single attribute in one language uses 10 credits.


---

# 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://usermanual.ergonode.com/system/your-plan.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.