# Road Technology Documentation

> Everything an agent needs to understand and support the Road EV-charging platform: a plain-English e-mobility primer, the platform data model and guides (including single sign-on and the application marketplace), and the Support Agent MCP tools. The full API reference is published separately under /docs. Point an agent at /llms-full.txt for the complete documentation in one file.

> Append `.md` to any documentation, blog or release page URL for its Markdown source.

## eMobility primer
- [What e-mobility is](https://technology.road.io/docs/emobility/what-emobility-is): How electric vehicle charging actually works, and why it is more than a card swipe.
- [Who's who](https://technology.road.io/docs/emobility/the-players): Drivers, charging stations, CPOs, eMSPs, roaming hubs, and where a platform like Road sits.
- [Anatomy of a charging session](https://technology.road.io/docs/emobility/anatomy-of-a-charging-session): What happens from plugging in to getting billed, end to end.
- [OCPP, talking to charging stations](https://technology.road.io/docs/emobility/ocpp): The open protocol between a charging station and the system that manages it.
- [OCPI, roaming between networks](https://technology.road.io/docs/emobility/ocpi): The open protocol that lets one provider's drivers charge on another operator's network.
- [Glossary](https://technology.road.io/docs/emobility/glossary): The vocabulary of EV charging, in one place.

## Platform
- [How the platform works](https://technology.road.io/docs/platform/introduction/overview): The platform's data model, the lifecycle of a charge, and how the CPO and eMSP sides meet.
- [Providers, accounts and users](https://technology.road.io/docs/platform/account-management/providers-accounts-and-users): The tenancy and ownership model, and how accounts and users are provisioned, billed and run.
- [Single Sign-On](https://technology.road.io/docs/platform/account-management/single-sign-on): How SSO works on Road, and when to choose SAML or OIDC.
- [SAML](https://technology.road.io/docs/platform/account-management/single-sign-on/saml): Corporate directory SSO at the Account level, over SAMLv2.
- [OpenID Connect (OIDC)](https://technology.road.io/docs/platform/account-management/single-sign-on/openid-connect): Customer identity and social login over OpenID Connect.
- [Custom domains](https://technology.road.io/docs/platform/account-management/custom-domains): Point a Private Label customer's own domain at Road over Cloudflare custom hostnames, with automatic TLS.
- [Data migration](https://technology.road.io/docs/platform/account-management/data-migration): Move an existing base of accounts, users, stations and cards onto Road, by CSV in the dashboard, with the migration team, or over the API.
- [Billing](https://technology.road.io/docs/platform/account-management/billing): How Road bills Accounts, the difference between tariffs and billing plans, and who pays what across charge card usage, running stations, and reimbursement.
- [Charging stations](https://technology.road.io/docs/platform/charge-point-operation/charge-stations): How the platform models physical charging hardware, and how that maps to OCPP and OCPI.
- [OCPP connectivity](https://technology.road.io/docs/platform/charge-point-operation/ocpp-connectivity): How to configure a charging station's OCPP settings to connect to Road's charging-station management backend.
- [Onboarding stations](https://technology.road.io/docs/platform/charge-point-operation/onboarding-stations): How a charging station comes onto the platform, from installation to going live, plus the pre-registration path for doing it ahead of time.
- [Tariffs and pricing](https://technology.road.io/docs/platform/charge-point-operation/tariffs-and-pricing): How a charge is priced, from the parts of a tariff to restrictions and caps, scheduled and dynamic pricing, tariff profiles, reimbursement, and where charging policies are heading.
- [Access control](https://technology.road.io/docs/platform/charge-point-operation/access-control): Who is allowed to charge at a station, how a charge is authorised at the moment it starts, and how RFID, roaming and car recognition fit in.
- [Charging sessions](https://technology.road.io/docs/platform/charge-point-operation/charging-sessions): How a charge is recorded on the platform, the two sides of a session, whether it is valid and billable, and how it becomes a CDR.
- [Managing and maintaining stations](https://technology.road.io/docs/platform/charge-point-operation/managing-stations): Running and maintaining a live fleet, remote actions, bulk jobs, configuration and presets, firmware, diagnostics, command history, maintenance access and the operational status lifecycle.
- [Charging station detected issues](https://technology.road.io/docs/platform/charge-point-operation/charging-station-detected-issues): How the platform detects faults, misconfigurations and connectivity problems on a station, who gets notified, and how to resolve them.
- [Reliability reporting](https://technology.road.io/docs/platform/charge-point-operation/reliability-reporting): Export how long each connector spent in each status over a period, the basis for measuring availability and for regulatory reliability reports.
- [Publishing to the roaming network](https://technology.road.io/docs/platform/charge-point-operation/publishing-to-roaming): How an operator's stations become reachable to other networks over roaming, what is shared, and the difference between a listed and an unlisted location.
- [ERE (Emissiereductie-eenheden)](https://technology.road.io/docs/platform/charge-point-operation/ere-integration): Read charging-session and charging-station data for Emission Reduction Units, over per-user OAuth or a provider API credential.
- [Cards, tokens and access](https://technology.road.io/docs/platform/e-mobility-services/cards-tokens-and-access): What authorises a charge, the card that carries it, and how an eMSP controls where a driver can charge.
- [Dispatching cards](https://technology.road.io/docs/platform/e-mobility-services/dispatching-cards): The two ways an eMSP puts charge cards in drivers' hands, physical branded cards and virtual cards.
- [Finding charging locations](https://technology.road.io/docs/platform/e-mobility-services/finding-locations): Show drivers where they can charge on an embeddable map covering your own network and every location Road reaches through roaming.
- [Sessions](https://technology.road.io/docs/platform/e-mobility-services/sessions): The eMSP-side record of a charge one of your drivers ran, and what you bill them from.
- [Credit sessions](https://technology.road.io/docs/platform/e-mobility-services/credit-sessions): A credit session is a durable record of a price correction to an eMSP session, created when a roaming partner withdraws or corrects a CDR.
- [Credit limits](https://technology.road.io/docs/platform/e-mobility-services/credit-limits): How the platform caps a driver's monthly charging on credit, when tokens are blocked, and how the limit resets.
- [Fleet management](https://technology.road.io/docs/platform/e-mobility-services/fleet-management): How an account groups its drivers, cards and vehicles into fleets and delegates the day-to-day running of each, without handing over account-wide access.
- [Overview](https://technology.road.io/docs/platform/payment-methods/overview): The ways a driver can pay for a charge on Road, from the roaming network to on-station card terminals, web checkout and the mobile app, and how each settles.
- [Charge cards and the roaming network](https://technology.road.io/docs/platform/payment-methods/charge-cards-and-roaming): Paying for a charge with an RFID card or contract, including drivers from other networks over roaming.
- [On-station card terminals](https://technology.road.io/docs/platform/payment-methods/on-station-terminals): Paying with a bank card at the charging station, the two kinds of terminal Road supports, and how Road handles the acquiring.
- [Web checkout](https://technology.road.io/docs/platform/payment-methods/web-checkout): Scan-to-Pay, ad-hoc card payment through a hosted web page reached by a QR code at the charging station, with no terminal hardware.
- [In the mobile app](https://technology.road.io/docs/platform/payment-methods/in-the-mobile-app): How a driver pays for a charge started from the Road mobile app, with a stored card, a wallet, or a linked charge card.
- [Application Marketplace](https://technology.road.io/docs/platform/integrations/marketplace): Connect third-party apps to Road on a customer's behalf, over standard OAuth 2.1 and OpenID Connect.
- [Registering an application](https://technology.road.io/docs/platform/integrations/marketplace/registration): Three ways to obtain an OAuth client: curated templates, provider installations, and dynamic self-registration.
- [Authenticating your application](https://technology.road.io/docs/platform/integrations/marketplace/authentication): The OAuth 2.1 Authorisation Code flow with PKCE: discovery, authorisation, and token exchange.
- [Consent, grants and data sharing](https://technology.road.io/docs/platform/integrations/marketplace/consent-and-sharing): What a customer consents to, managing connected apps, and choosing which data to share.
- [Using the API](https://technology.road.io/docs/platform/integrations/marketplace/using-the-api): Calling the API with an access token, refreshing tokens, and handling revocation and errors.
- [Charging Station Message Exchange (CSME)](https://technology.road.io/docs/platform/integrations/csme): A service that exchanges real-time charging-station telemetry and commands between Road and an external party such as a smart-charging service provider.

## Roaming Hub
- [Overview](https://technology.road.io/docs/roaming/concepts/overview): The Road Roaming Hub is a standalone OCPI hub that connects CPOs, eMSPs and CPMS platforms, so each integrates once and reaches the whole network.
- [Coverage](https://technology.road.io/docs/roaming/concepts/coverage): The Road Roaming Hub reaches CPOs and eMSPs across Europe through direct integrations and partnerships with established roaming hubs.
- [Joining the Road network as a CPO](https://technology.road.io/docs/roaming/guides/joining-as-a-cpo): How a Charge Point Operator connects to the Roaming Hub, peer-to-peer, as a hub extension, or through Roaming-as-a-Service.
- [Joining the Road network as an eMSP](https://technology.road.io/docs/roaming/guides/joining-as-an-emsp): How an eMobility Service Provider connects to Road over a peer-to-peer OCPI agreement to reach Road's CPO locations.
- [Roaming as a Platform-as-a-Service (PaaS)](https://technology.road.io/docs/roaming/guides/roaming-paas): Run your own roaming network on Road's hub, with full control over your own agreements and configuration.

## ChargeNow
- [ChargeNow (Early Access)](https://technology.road.io/docs/charge-now/concepts/overview): A unified API for adding EV charging to your product, without integrating directly with individual charging networks.
- [Authentication](https://technology.road.io/docs/charge-now/guides/authentication): How to authenticate with the ChargeNow API using a Bearer token issued by the ChargeNow team.
- [Sandbox](https://technology.road.io/docs/charge-now/guides/sandbox): An isolated environment with simulated charge points for building and testing your integration without real charging infrastructure or charges.
- [Quality Metrics](https://technology.road.io/docs/charge-now/guides/quality-metrics): A data-driven view of how reliably each charge point performs.
- [Errors](https://technology.road.io/docs/charge-now/guides/errors): ChargeNow uses standard HTTP status codes and returns a consistent RFC 7807 problem body for every failure.
- [Sessions](https://technology.road.io/docs/charge-now/guides/sessions): A session tracks a complete charging cycle, from the moment you request it to the final confirmed cost.
- [Start a session](https://technology.road.io/docs/charge-now/guides/sessions/start-session): Find a charge point, start a session, monitor it in real time, and stop it.
- [Settlement & Corrections](https://technology.road.io/docs/charge-now/guides/sessions/settlement): How final billing data arrives after charging ends, how to detect corrections using settlementVersion, and what a correction means for your billing.
- [Webhooks](https://technology.road.io/docs/charge-now/guides/webhooks): Receive signed HTTPS notifications when things happen in your integration, instead of polling.
- [session.updated](https://technology.road.io/docs/charge-now/guides/webhooks/session-updated): The session.updated webhook fires whenever a charging session changes state or its energy and cost figures are updated.

## Support Agent MCP
- [Overview](https://technology.road.io/docs/support-agent-mcp/overview): What the Support Agent MCP is, how to connect and get access, and the access model behind the tools.
- [Customer verification](https://technology.road.io/docs/support-agent-mcp/customer-verification): How an agent verifies a customer and threads the conversation token so customer-scoped tools can run.

## Blog
- [How we fixed large exports](https://technology.road.io/blog/async-exports): As the platform scaled, synchronous CSV exports went from quick to unusable. Here is how we moved them to background jobs, and why Temporal did the heavy lifting.

## Full text
- [All documentation as one file](https://technology.road.io/llms-full.txt): the complete documentation in a single Markdown document.