> 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/enapi-documentation-pt/precos-e-tarifas.md).

# Preços e Tarifas

As tarifas são o ponto em que a realidade comercial se encontra com o OCPI. Um CPO define o preço; um eMSP precisa de o ver; um condutor acaba por pagá-lo; ambas as partes precisam de que a fatura corresponda. Esta secção aborda como as tarifas fluem no ENAPI e o que é possível quando diferentes eMSPs precisam de preços diferentes do mesmo CPO.

### Nesta secção

Use estas páginas para compreender tanto os preços standard como os diferenciados:

* [Como Funcionam as Tarifas na ENAPI](https://docs.enapi.com/enapi-documentation-pt/precos-e-tarifas/como-funcionam-as-tarifas-na-enapi.md) — compreender como as tarifas são publicadas e consumidas.
* [Tarifas Específicas por Parceiro Geridas pelo CPO](https://docs.enapi.com/enapi-documentation-pt/precos-e-tarifas/tarifas-especificas-por-parceiro-geridas-pelo-cpo.md) — publicar tarifas específicas por parceiro a partir do seu próprio sistema.
* [Ajustes de tarifas](https://docs.enapi.com/enapi-documentation-pt/precos-e-tarifas/ajustes-de-tarifas.md) — deixar o ENAPI gerir descontos e sobretaxas por si.
* [Visão Geral das Tarifas para eMSPs](https://docs.enapi.com/enapi-documentation-pt/precos-e-tarifas/visao-geral-das-tarifas-para-emsps.md) — consultar rapidamente os preços por parceiro.


---

# 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/enapi-documentation-pt/precos-e-tarifas.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.
