Machine access
Developers and MCP
Machine access to the ChargeBridge catalogue: read-only public API, MCP server, OpenAPI specifications and llms.txt. Published catalogue only; no partner data. Every channel is generated from the same record set: same scope, same offer status, same evidence.
Three channels, one catalogue
- Catalogue version
- 2026-10-04 · 4 October 2026
REST
Public API
JSON, read-only, rate-limited, CORS open. No authentication is needed. Responses carry the catalogue version and verification dates; unknown fields are not filled by guessing.
| Endpoint | Parameters | Returns |
|---|---|---|
| GET /api/public/v1/modules | version, role, include_not_offered, locale, page, per_page | OCPI module coverage with sender/receiver per role, scope, offer status, evidence records and evidence level. |
| GET /api/public/v1/roles | role, locale | Public record of a partner role (cpo, emsp, nsp): needs, modules, portal views, requirements per gate, process and FAQs. Without role: all roles. |
| GET /api/public/v1/trust | entity_id, locale | Entity information, compliance programme status, agreement references and the relationship statement for e-gridium or electroop. |
| GET /api/public/v1/evidence | locale | Every evidence record with kind, level, what it supports, what it does not show, verification date and review status. |
Model Context Protocol
MCP
Read-only MCP server. Transport: streamable HTTP, stateless, JSON responses; no SSE and no sessions. It reaches only the published catalogue; no tool has side effects.
Endpoint
https://egridium.com/mcp
| Tool | Input | Returns |
|---|---|---|
| list_modules | version?, role?, include_not_offered?, locale? | OCPI module coverage of the ChargeBridge hub: module, OCPI version (2.2.1, 2.3.0, Türkiye extension), sender/receiver per role, scope, offer status (offered / offered in dry-run / not offered) and linked evidence. Includes the explicit not-offered rows. |
| get_module | module_id, locale? | Full public record of one module with scope, offer status, evidence records and evidence level. |
| get_role | role, locale? | Public record of a partner role (cpo, emsp, nsp): needs, modules used, portal views, requirements per gate, process and FAQs. |
| check_partner_requirements | role, have?, locale? | Checklist for connecting in a role. Pass what the applicant already has (requirement ids from get_role); returns readiness per gate (technical, financial) and what is missing. Guidance only; it does not replace the participation agreement. |
| get_trust_information | entity_id?, locale? | Entity information, compliance programme status (never certifications), agreement references and the relationship statement for e-gridium or electroop. |
| search_knowledge | query, locale?, limit? | Short excerpts from approved sources (modules, roles, FAQs, evidence, compliance, agreements, status) with URL and verification date. |
Add to a client
Add the server address to any MCP-capable client. No authentication is needed; rate limits apply.
claude mcp add --transport http egridium https://egridium.com/mcp{
"mcpServers": {
"egridium": {
"type": "http",
"url": "https://egridium.com/mcp"
}
}
}Raw JSON-RPC
Fetch the tool list over plain HTTP; the same endpoint also answers initialize, tools/call, resources/list and resources/read.
curl -X POST https://egridium.com/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'OpenAPI
OpenAPI specifications
Machine-readable API descriptions generated from the hub services. The documents are public; the endpoints themselves require partner credentials issued during onboarding.
-
32 paths
OCPI adapter
OCPI 2.2.1 and 2.3.0 version endpoints, sandbox routes and the Türkiye extension.
/api-specs/ocpi-adapter.openapi.json -
17 paths
Clearing platform
Settlement windows, statements, disputes and the ledger.
/api-specs/clearing-platform.openapi.json -
34 paths
Identity service
Partner identities, credentials and access management.
/api-specs/identity-service.openapi.json
Credentials are issued at onboarding; the documents grant no access.
llms.txt
A site map and content summary for language models; the full version carries the whole catalogue as plain text.
Partner documentation and status
Partner documentation and the status page are shared after application, together with the sandbox credentials.
- Published catalogue only: modules, roles, evidence, compliance status, agreement references. No partner data, no charging session, CDR or settlement record is served through these channels.
- No partner names or counts, fee rates, numeric service levels or go-live dates are published; the tools do not produce them.
- Size, time and request limits apply; no personal data is expected in requests.
How it proceeds
- 01Apply with your role and versions endpoint
- 02Sign the participation agreement and DPA
- 03Handshake in the sandbox, then accept relationships