> 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/getting-started/testing-your-connection/for-cpos.md).

# For CPOs

## Where your data lands

* **Locations → Your data** — the locations ENAPI pulled from your platform. Open one to inspect its EVSEs, connectors and capabilities as ENAPI parsed them.
* **Tariffs** — tariffs ENAPI pulled, with their associations to locations.

## What gets tested

### Inbound — ENAPI pulls from you

* **Locations** — structure, completeness, correct mapping of connectors and capabilities.
* **Tariffs** — pricing structure, tariff-to-location associations.

### Outbound — you pull from the eMSP simulator

* **Tokens** — authentication data, token states and types.

### Session flow

1. **Start** — the simulator uses test tokens to start sessions at your locations. State transitions and authorization flows are observed.
2. **Updates** — real-time updates from your side are routed through.
3. **Stop and CDR** — stop issued; CDR received; CDR routed to billing.

To drive a session yourself from the portal, see [Starting and stopping sessions in staging](https://docs.enapi.com/getting-started/testing-your-connection/starting-and-stopping-sessions-in-staging.md).


---

# 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/getting-started/testing-your-connection/for-cpos.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.
