> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/education-and-training/licensing-education/learn-about-software-licensing-models/consumption-based-licensing.md).

# Consumption-Based Licensing

Find out how consumption-based licensing tracks software usage with consumption tokens, enabling pay-as-you-go pricing and fairer cost alignment.

Consumption-Based Licensing tracks and charges for actual software usage using units called consumption tokens, enabling flexible and fair pricing.

**Key Features:**

* Allocates tokens to license codes or users for purchasing software or features.
* Supports usage-tracked contracts and pay-as-you-go models.

**Benefits:**

* Aligns costs with value derived.
* Opens up new markets by making software accessible to light users.

**Trends:**

* Popular in SaaS and cloud services.
* AI/ML for usage predictions and dynamic pricing.
* Granular tracking, down to API calls or processing time.

Consumption-Based Licensing is ideal for organizations optimizing costs based on usage or offering flexible pricing to customers.


---

# 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.nalpeiron.com/education-and-training/licensing-education/learn-about-software-licensing-models/consumption-based-licensing.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.
