> 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/tariff-overview-for-emsps.md).

# Tariff Overview for eMSPs

A summary view of a CPO's pricing across their network — useful for evaluating partners before signing, and spot-checking pricing on active connections.

### Where to find it

The **Tariffs** tab on CPO's partner detail page in the ENAPI Portal.

### Why this exists

OCPI tariffs are complex. A single tariff can combine several price components (energy, flat fees, time, parking) with restrictions by time of day, day of week, current, power, and energy thresholds. A CPO's network usually has many tariffs assigned to different connectors across different countries and currencies — so it's hard to get a feel for what a partner actually charges without trawling through every connector or running OCPI calls yourself.

The Tariff Overview rolls the full tariff catalogue up into a small set of charts so you can see the shape of a CPO's pricing at a glance.

### How the view is structured

Tariffs are grouped first by **country**, then by **currency**. Tariffs in different currencies are never mixed in the same chart — you'll see each currency in its own block.

Within each country/currency block, there's one chart per **price component**:

* **Energy.** Per-kWh charging cost.
* **Flat.** Start fees, transaction fees.
* **Time.** Charging duration cost
* **Parking time.** Idle / occupancy fees after charging ends.

### Reading the histogram

Each chart is a histogram of prices for that component:

* **X-axis (bins).** Pricing ranges. Each bin groups tariffs that fall within that range.
* **Y-axis (bar height).** How often that price range is applied across the CPO's connector base. Tall bars = many connectors are exposed to that price; short bars = niche pricing.
* **Color split (AC vs. DC).** AC and DC are shown as separate colored bars in each bin so you can compare how the same component is priced across charging speeds.

<figure><img src="https://303450155-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FheBP0sH0U1Rrp1jIot9S%2Fuploads%2FKuL5NrTQeZHePMGBXG26%2FScreenshot%202026-05-04%20at%2018.23.44.png?alt=media&amp;token=1d818c25-3986-4e69-a1de-53c4617f3c05" alt="" width="563"><figcaption><p>Tariff Overview.</p></figcaption></figure>

### The AC / DC badges and median

Two pieces of summary information sit on the chart header:

* **AC and DC coverage badges** (next to the component title). Show the percentage of connectors that have this component priced. If 100% of connectors of that current type apply the component, the badge is hidden — its absence means "applies everywhere." When the badge appears (e.g., *AC 62%*), it's a signal that this component only applies to a subset of connectors.
* **AC / DC median** (top right of the chart). The median price of this component across the CPO's connectors, split by AC and DC. Useful for a one-number gut check on what a typical session would cost.

### What this view does and doesn't tell you

**It does:**

* Show how a CPO's pricing is distributed across their network — and where the bulk of their connectors sit.
* Surface AC vs. DC pricing differences.
* Compare pricing exposure across countries and currencies in one place.

**It doesn't:**

* Replicate the exact billing logic of every tariff: Tariffs can have time-of-day restrictions, current/power thresholds, tiered energy pricing, and step-size rounding — the histogram flattens those conditional rules so they can be compared. Two tariffs with the same per-kWh price can still produce different session costs depending on step size and restrictions.

**Use this view for partner evaluation, not session-level cost prediction.** It's the right tool to assess whether a CPO's pricing fits your roaming strategy. For exact session costs, you still need the underlying tariff and the session details.

### FAQ

<details>

<summary>Why is the Tariffs tab missing on some partners?</summary>

Some CPOs opt out of having their pricing displayed in this overview. Their tariffs continue to be exchanged via OCPI as usual — only this summary view is hidden on their detail page.

</details>

<details>

<summary>Why don't I see a chart for a component?</summary>

The CPO's tariffs don't price that component. Many CPOs only charge for energy and a flat fee, for example.

</details>

<details>

<summary>Why is an AC or DC badge missing?</summary>

100% of connectors of that current type have this component priced — the badge is only shown when coverage is partial.

</details>

<details>

<summary>Does this include tariffs from CPOs we're not yet connected to?</summary>

Yes. The Tariffs tab is available on every partner's detail page, including CPOs you haven't signed a roaming agreement with — that's the point. Use it to evaluate fit before opening an offer.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.enapi.com/pricing-and-tariffs/tariff-overview-for-emsps.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
