> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tolk.every-day.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Plan and usage

> Your plan sets limits on keys, projects, users and the AI budget. See how much you use and what happens at a limit.

Every customer has one plan. The plan determines:

* the **maximum number of keys**, across all of the customer's projects together;
* the **maximum number of active projects**;
* the **maximum number of users**: the external people who can work in the customer's projects;
* the **AI budget per month**, in euros.

You see your plan read-only, on the project overview and on the [Usage](#the-usage-page) page. Need a larger plan? Contact Every Day, your Tolk contact.

## What counts

| Limit | Counts | Does not count |
| - | - | - |
| Keys | Active keys in all of the customer's projects, including archived projects (they can come back) | Archived keys, and projects that have been deleted |
| Active projects | Projects that are neither archived nor deleted | Archived projects |
| Users | External users with a role in one of the customer's projects (archived projects included), and the email addresses of pending invitations to those projects. Each person counts once, however many projects they work in | Every Day colleagues, deactivated and deleted users, expired and accepted invitations, and projects that have been deleted |
| AI budget | The actual costs of AI translations in the current calendar month | |

## When a limit is reached

Existing keys, projects and users always keep working: translating, exporting and the API remain available. Only **new** keys, projects or users are refused.

| Where | What you see |
| - | - |
| Project overview | The **Plan** card shows keys, projects and users with a progress bar; from 90% **Almost full** (*Bijna vol*), at the limit **Limit reached** (*Limiet bereikt*) |
| Restoring a project | Restoring an archived project fails if the number of active projects would then exceed the limit |
| Import | The preview says that the new keys do not fit and how much room is left. You can then only import with **Create unknown keys** (*Onbekende keys aanmaken*) off; see [Importing](/guide/importing) |
| API (`POST /keys/sync`) | `422` with `reason: key_limit_reached`, the limit, the usage and the number of keys requested. Nothing is written; see [Syncing keys](/developers/syncing-keys#key-limit) |
| API import | The job fails with `key_limit_reached` |
| Adding a member or inviting someone | A person who does not count yet for the customer is refused, with a message under the email address. Adding someone who already works in another project of the customer, inviting an address again whose invitation is still pending, or adding an Every Day colleague always works. See [Team](/guide/team) |
| Resending an invitation | An expired invitation no longer counts, so resending it needs room; a pending invitation can always be resent |
| AI translation | A translation does not start if the estimate no longer fits in the budget; if the budget runs out during the translation, it stops |

You make room by archiving keys (for example with a push that archives keys that have disappeared), archiving a project, removing someone from the team, revoking a pending invitation or asking Every Day for a larger plan. Accepting an invitation is never refused: the invitation already counted.

## The AI budget

AI translation costs are tracked per customer, in euros, against the monthly budget of the plan.

* When an AI translation starts, Tolk reserves the estimated costs. If the estimate does not fit in what is left, the translation does not start.
* Afterwards, the actual usage counts. Whatever is left of the reservation goes back into the budget.
* If the budget runs out during a translation, Tolk stops and the project's managers get an email. What has already been translated stays.
* The budget starts again every calendar month.

See [Translating with AI](/guide/ai-translation) for the estimate you see before you start.

## The Usage page

The **Usage** (*Gebruik*) page in the navigation bar shows for the active customer:

* the **plan**, with the keys, active projects and users against the limits, and the notices **Almost full** (*Bijna vol*) and **Limit reached** (*Limiet bereikt*);
* the number of **glossary terms**;
* the **keys per project**, with their share. Archived projects count towards the limit;
* the **AI costs** of this month against the budget, with a chart of the last 12 months (also as a table for screen readers).

Amounts are shown in euros and numbers in Dutch notation (`€ 1.234,56`, `2.412 keys`), or in English notation if you use Tolk in English.

### Who sees the page

| Who | Sees |
| - | - |
| Manager of at least one of the customer's projects | Everything, but only their own projects by name; the keys of the other projects are grouped as **Other projects** (*Andere projecten*), so the totals add up |
| Developer and translator | Nothing |

The project overview shows the same plan card, with a **View usage** (*Bekijk gebruik*) link for those who may see this page.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.