voltbase
Developer-first open-core tooling for EV charging data — a normalisation library, a discovery API, and an MCP server over open data only.
How it works
1. Normalise
OCM, OSM extracts, OCPI 2.2.1 and DATEX II feeds map into one core row with a per-row source and licence partition key. Unknown licences are treated as closed and never served.
2. Serve
A stateless edge API serves servable rows only, each with source, retrieved-at and attribution. Stale rows carry a stale label, never silent empties.
3. Ask
The same four tools answer over CLI stdio (voltbase mcp) and over HTTP (POST /mcp), with typed errors where a capability is local-only.
Pricing
Free self-serve (v0.1): everything in these docs — normalisation, discovery API and MCP over open data. Paid self-serve: placeholder — no payments, sessions or billing exist in v0.1 (see Legal).
Open data only
Every example on this site uses open-licenced rows: NL NDW (CC0), LU Chargy KML (CC0), FR IRVE (Licence Ouverte / Etalab), OCM open rows (CC BY 4.0) and OSM extracts (ODbL). Provider-copyright and unclear-licence rows are excluded before serving — see Attributions.