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

# Pricing & Tariffs

Tariffs are where commercial reality meets OCPI. A CPO sets the price; an eMSP needs to see it; a driver ends up paying it; both sides need the invoice to match. This section covers how tariffs flow on ENAPI and what's possible when different eMSPs need different prices from the same CPO.

### In this section

Use these pages to understand both standard and differentiated pricing:

* [How Tariffs Work on ENAPI](https://docs.enapi.com/pricing-and-tariffs/how-tariffs-work-on-enapi.md) — understand how tariffs are published and consumed.
* [Partner Specific Tariffs CPO Managed](https://docs.enapi.com/pricing-and-tariffs/partner-specific-tariffs-cpo-managed.md) — publish partner-specific tariffs from your own system.
* [Tariff Adjustments](https://docs.enapi.com/pricing-and-tariffs/tariff-adjustments.md) — let ENAPI manage discounts and surcharges for you.
* [Tariff Overview for eMSPs](https://docs.enapi.com/pricing-and-tariffs/tariff-overview-for-emsps.md) — review partner pricing at a glance.


---

# 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.enapi.com/pricing-and-tariffs.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.
