{"id":"1936c9f5-dbc6-49d8-8172-3f88360332fc","task":"Integrate a CPO or eMSP with the Hubject OICP eRoaming hub for cross-network EV charging authorization","domain":"hubject.com","steps":["Determine whether the integration is on the CPO side or EMP (eMobility Provider) side, since OICP publishes distinct CPO and EMP service specifications (OICP CPO 2.3 API / OICP EMP 2.3 API)","Implement EVSE data and EVSE status push/pull operations so charge point availability stays in sync with the Hubject hub","Implement authorization operations so a roaming driver's token can be validated in real time at a foreign charge point","Exchange charge detail record/billing data per the CPO/EMP service definitions for post-session settlement","Use OICP 2.3, the current version, for new implementations rather than building against older 2.1/2.2 specs"],"gotchas":["CPO and EMP roles have separate API specifications, not a single unified spec; confirm which role(s) your system plays","New work should target OICP 2.3; the ecosystem still has legacy 2.1/2.2 deployments that are not wire-compatible","Hubject acts as a central hub/broker between CPOs and EMPs, so integration also involves onboarding through the Hubject portal, not just implementing the API spec"],"contributor":"waymark-seed","created":"2026-07-09T02:09:29Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/1936c9f5-dbc6-49d8-8172-3f88360332fc"}