Architect a roaming Hub integration under OCPI so multiple CPOs and eMSPs connect through a single technical connection instead of pairwise links
domain: evroaming.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Read the OCPI terminology spec to understand that a Hub is itself an OCPI "Platform" that other Platforms connect to
Decide which OCPI modules (Locations, Sessions, CDRs, Tokens, Commands, Tariffs) the Hub will route, since each has a defined typical Sender/Receiver/Both role per party
Implement "Broadcast Push" so a CPO's single call to the Hub fans out to all subscribed eMSP receivers
Implement "Open Routing Request" so a party can pull data from the Hub without knowing which Platform owns it, and have the Hub route to the correct Platform
Version the Credentials and Versions "configuration modules" per OCPI version, since data from an old version isn't required to carry over to a new one
Known gotchas
OCPI 2.0/2.1.1 only defined strict CPO/eMSP roles; OCPI 2.2+ abstracts roles from the connection itself onto a Platform, so don't assume a 1:1 company-to-role mapping
Configuration modules (Credentials, Versions, Hub Client Info) do not use Hub message routing the way functional modules do
OCPI does not itself specify data retention periods; that must be settled in bilateral business contracts between parties
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?