Register for API access at the Zap-Map developer portal and obtain your API key.
Call the POI (points of interest) endpoint with a bounding box or center-and-radius and specify connector type filters (e.g., CCS, CHAdeMO, Type 2) using the connector query parameter.
Parse the response array of charging locations: each location includes latitude, longitude, connector details, network operator, and real-time availability status where available.
Display markers on a map layer, colour-coded by availability status (available, occupied, unknown); use clustering for high-density areas.
Request detail for a selected station using the station detail endpoint and station ID to show full connector list, access type (24/7, restricted), and payment methods.
Implement periodic polling or use the delta endpoint (if available) to refresh availability markers without re-fetching the entire dataset.
Known gotchas
Real-time availability data is network-dependent; many charging locations in the Zap-Map database show static data only with no live availability — always display a 'last updated' indicator.
Connector type nomenclature varies by region; CHAdeMO is in decline in Europe post-2024 while NACS adoption is rising in North America — keep connector filter labels current.
Free tier API access has rate and record limits; for high-traffic map tiles, negotiate a commercial agreement to avoid 429 throttling.
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