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

# Account Management

- [Plans and Credits](https://docs.mindee.com/account-management/plans.md): Pricing plans, credits, and features comparison.
- [Support Levels](https://docs.mindee.com/account-management/support-levels.md): Mindee provides different levels of support depending on your subscription plan. Support options range from community-driven help to real-time chat with priority handling for urgent needs.
- [Account Settings](https://docs.mindee.com/account-management/account-settings.md): Manage your Mindee account.
- [Organization & Members](https://docs.mindee.com/account-management/organizations.md): Organizations in Mindee enable collaborative work: users can belong to an organization and participate in workspaces with role-based access control.
- [Billing](https://docs.mindee.com/account-management/billing.md): The Billing page in your Mindee account lets you manage your subscription and access past invoices.
- [Insights](https://docs.mindee.com/account-management/insights.md): The insights page allows you to view various data concerning your usage of the Mindee platform and API.


---

# 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://docs.mindee.com/account-management.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.