> For the complete documentation index, see [llms.txt](https://bluurdoc.bluur.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bluurdoc.bluur.ai/en/system/billing-and-licensing/pages.md).

# Pages

Each plan has a specified limit of pages that can be anonymized in a given billing period.

Adding documents and performing **AI classification** do not reduce the limit. Pages are billed only after anonymization is started.

The system bills all pages in the document, including those on which no data was selected for anonymization.

**Example:** Adding and classifying a document containing 10 pages does not reduce the limit. Performing anonymization results in billing for 10 pages, even if the data intended to be hidden is only on part of the document.

If anonymization requires using more pages than the plan limit, the system will display information about an additional fee. Continuing the process requires confirming the charge.

<figure><img src="https://572977165-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKPbZABdmwpFq6bAJuwUC%2Fuploads%2FdoqeLGcMN6Fgpu4izoWe%2Fimage.png?alt=media&amp;token=22be09bd-4602-4cdf-a314-ef9952045bff" alt=""><figcaption><p>Window informing about exceeding the anonymization limit.</p></figcaption></figure>


---

# 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://bluurdoc.bluur.ai/en/system/billing-and-licensing/pages.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.
