> For the complete documentation index, see [llms.txt](https://docs.altum.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.altum.ai/english/platform/credits-and-pricing.md).

# Credits and pricing

How credits and prices work on the Altum AI Platform.

On the Platform you pay with credits. Each API has a fixed credit value per call. 1 credit costs €0.05 excl. VAT. The price of a call is that credit value times €0.05.

A price of €0.05 per credit does not mean that every call is cheaper than before. Heavier APIs use more credits. How many credits an API costs per call is in the [Cost Calculator](https://platform.altum.ai/abonnement?tab=calculator) on the platform. That is the single source of truth.

## How credits work

* Your credit balance is in the dashboard on platform.altum.ai.
* A billed call deducts that API's credit value from your balance.
* The balance can lag by about 1 minute after a call.
* Sandbox calls do not use credits. See Sandbox.
* You authenticate with your API key in the `x-api-key` header on api.altum.ai.

The Usage API reports the number of calls, not the number of credits. Multiply the number of calls by the credit value of that API. That credit value is in the [Cost Calculator](https://platform.altum.ai/abonnement?tab=calculator) on the platform.

## Plans

| Plan                   | How you pay                                                                                                                                                  |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Free trial             | 1,000 credits, 30 days, no obligation.                                                                                                                       |
| Startup 5,000          | The platform activates Startup 5.000. The site price is €100 excl. VAT. Startup is still billed in calls, not credits, so customers can freely try all APIs. |
| Pay per use            | €50 per month excl. VAT, including 1,000 credits. Extra usage is billed afterwards on the next invoice.                                                      |
| Prepaid Growth and Pro | The price depends on volume and which APIs. Contact us for specific pricing.                                                                                 |
| Enterprise             | Custom contract.                                                                                                                                             |

When you upgrade, prepaid credits start immediately and any open pay per use amount is settled. When you downgrade, use remaining prepaid credits first. Those credits expire when the plan changes. Open pay per use is settled immediately.

Subscriptions run for one month. If you do not cancel, they renew for another month. You can cancel during the month. On early cancellation, open pay per use costs are settled immediately.

## Fair use

For pay per use and standard prepaid, the fair use guideline is about 10,000 calls per day. Enterprise follows the custom contract, with a fair use guideline of 10,000 calls per day.

## Billed outside the bundle

These APIs are outside your bundle: rebuild value, contents value, and PC6 average WOZ. The number of credits per call is in the [Cost Calculator](https://platform.altum.ai/abonnement?tab=calculator) on the platform.

Kadaster Transaction runs on credits within your paid subscription and is not available in the trial. See Kadaster Transaction API subscription.


---

# 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.altum.ai/english/platform/credits-and-pricing.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.
