Apply for Gireve hub connectivity through the Gireve partner registration process and receive your OCPI credentials (party ID, country code, and token).
Perform the OCPI credentials registration handshake with the Gireve hub endpoint: GET /ocpi/versions to discover version support, then POST your Credentials object to /ocpi/2.2.1/credentials to register your platform.
Query the Gireve Locations module by calling GET /ocpi/2.2.1/locations with pagination parameters to download the CPO's EVSE inventory and tariff IDs.
Retrieve tariff details using the Tariffs module GET endpoint to understand per-kWh, per-minute, and session fee pricing before initiating a session.
Send a START_SESSION command via the Commands module POST endpoint, specifying the EVSE UID, connector ID, and the driver's token UID.
Poll the session status via the Sessions module or subscribe to PUSH updates to monitor energy delivered and session state; retrieve the CDR after the session completes for billing reconciliation.
Known gotchas
Gireve acts as an OCPI hub/broker; your party ID must be unique across all Gireve-connected parties — coordinate with Gireve during onboarding to avoid party ID collisions.
Tariff objects reference currency explicitly; for cross-border EU roaming, tariffs may be in EUR or local currency depending on the CPO — normalize to a display currency before showing cost estimates to users.
OCPI hub connectivity through Gireve requires a signed framework agreement; all API paths and credentials are provided post-contract and should not be guessed.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp