> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spirii.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Platform overview
> The components the platform is built on, the interfaces you work through, and the roles involved.
These docs are organised around the platform itself:
* **Components** are the platform's core objects (locations, chargers, tariffs, tokens, sessions), and they map directly to the resources in the API reference.
* **Capabilities** are what the platform does with those objects: roaming, billing, energy management, and the rest.
* **Guides** put them to work end to end, so you can get started straight away.
Charge point operators (CPOs) and e-mobility service providers (eMSPs) share the same components. A location, a tariff, or a session means the same thing to a CPO and to an eMSP, but each reaches them through different endpoints and features. Capabilities connect the two: roaming, for example, takes a location and tariff a CPO has published and makes them reachable to an eMSP's drivers, then settles the session between them.
## Interfaces
The admin web app. Operators manage locations, chargers, pricing, and access; eMSP and fleet admins manage tokens and drivers.
Build the platform's capabilities directly into your own systems and front-ends.
The driver app (Spirii's own, or an eMSP's branded version) for finding, starting, and paying for a charge.
Spirii's point-of-sale software for in-person card payments, running on Payter Apollo terminals.
## Roles
| Role | Description |
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Charge Point Operator (CPO) | The business that runs the chargers: brings them online, sets pricing and access, and earns the charging revenue. |
| e-Mobility Service Provider (eMSP) | The business that gives drivers access to charging, across its own and other networks. |
| Customer | The organisation that owns locations, chargers, or drivers in the platform. Depending on the use case, this is a fleet, a site or asset owner, or another partner. |
| Driver | The person charging an EV. On the platform, a driver is represented by an app user or a token (an RFID, virtual, or vehicle key). |
## Charging
| Component | Description |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Locations | The container for one or more chargers at a geographical site, and the entity that pricing and access are connected to. |
| Charge boxes | An individual charge box that can serve electricity to one or more EVs at a time. |
| EVSEs | The part of a charge box that can serve one EV at a time. |
| Connectors | The socket or cable a single EV plugs into. |
| Charge detail records (CDRs) | The immutable, billable record of a completed charging session. |
| Sessions | The flow of electricity during a charging session, including sessions still running. |
## Access
| Component | Description |
| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Tenants | A single eMSP organisation on the platform — the account boundary that owns its eMSP identities, networks, and subscriptions. |
| Networks | Govern which charging infrastructure an eMSP tenant can reach, and how each connection is established, prioritised, and priced. Spirii's roaming portfolio is published to every tenant by default; a tenant can also keep networks that stay private to it. |
| Tokens | The authentication ID used to start a charging session: an RFID, virtual, or vehicle key (Autocharge). Shown as charge keys in Connect. Token groups can limit which tokens charge at selected locations. |
| Vouchers | A code entered in Spirii Go or a branded app to unlock access at selected locations. Voucher groups set the access and price conditions that apply to a user group. |
| App users | A driver with an account in Spirii Go or a branded app. |
## Commercial
| Component | Description |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Tariffs | The gross price and conditions for charging. Supports flat and dynamic (spot) pricing with conditional fees. A separate roaming tariff sets the price for charging via roaming partners, who add their own margin on top. |
| Payment terminals | The card payment terminals at a location that take in-person payments. Spirii POS runs on Payter Apollo hardware; other terminals and point-of-sale systems are also supported. |
## Where each component is defined
Each object above has its own component page with the full detail: attributes, states, and how it's used. Capabilities act on these objects, and guides walk you through using them end to end.
The full definitions, one page per object.
What the platform does with these objects: roaming, energy management, billing.
Start-to-finish walkthroughs to get you up and running.