Open Charge Map API
✓ Official Vendor SpecMaps GeolocationPlaces SearchapiKey2 EndpointsREST
For Agents
Search the global Open Charge Map database for EV charging stations and retrieve reference data for operators, connection types, and status codes.
Use for: Find EV charging stations within 5km of a given coordinate, List CHAdeMO-compatible chargers in a country, Get the reference list of charging operators, Look up the connection types supported in the database
Not supported: Does not handle real-time availability, live charger reservation, or payment authorisation — use for read-only EV charging-station POI lookup and reference data only.
The Open Charge Map API provides programmatic access to the world's largest open database of electric vehicle charging locations. The /poi endpoint returns charging-station points of interest with coordinates, connection types, power levels, operator details, and user-submitted comments, while /referencedata returns the lookup tables used to resolve operator IDs, connection types, status codes, and country codes returned in POI responses. The dataset is community-maintained and free to query for non-commercial use, with API key registration required for any production integration.
Install Jentic One Beta
Connect the Open Charge Map API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Open Charge Map API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Open Charge Map API.
Find EV charging stations within a radius of a given latitude and longitude
Filter charging-station results by country code, operator ID, or connection type
Retrieve detailed point-of-interest records including charge speed and connector counts
Resolve numeric IDs in POI responses against the /referencedata lookup tables
Return user-submitted comments and check-ins for charging-station reliability signals
Page through large result sets using maxresults and modifiedsince filters
Use Cases
Patterns agents use Open Charge Map API for, with concrete tasks.
★ EV Trip Planner Charger Search
Surface charging-station options along an EV route by querying /poi with latitude, longitude, distance, and connection-type filters. Open Charge Map covers stations across more than 80 countries with crowd-sourced reliability comments, which makes it useful as a primary source for hobbyist EV planners and as an alternative source layered alongside paid OEM data.
GET /poi?output=json&latitude=51.5074&longitude=-0.1278&distance=10&distanceunit=km&connectiontypeid=33 and return the top 10 chargers with operator and power kW.
Charger Operator Analytics
Build dashboards that compare charger coverage by operator, country, or connection type. The /poi endpoint can be paginated by maxresults and country code, while /referencedata supplies the operator and connection-type lookup tables needed to display human-readable names rather than numeric IDs in reports.
Pull /poi for countrycode=DE in batches of 1000 and /referencedata once, then group POIs by operator name from the OperatorID lookup.
Reliability and Reviews Lookup
Surface user-submitted check-ins and comments returned in POI responses to flag chargers with recent failure reports. The same /poi endpoint includes a UserComments collection per station, which can drive a freshness or reliability score in consumer apps without a separate review service.
GET /poi?chargepointid=12345&includecomments=true and return the most recent UserComments entry plus its CheckinStatusType.
AI Agent EV Routing Assistant
Through Jentic, an AI EV-routing agent can find chargers, resolve operator names, and report reliability without learning Open Charge Map's parameter conventions. The agent searches for the charger lookup operation, loads the schema, and executes the query with API-key handling delegated to MAXsystem.
Through Jentic, search for 'find EV charging stations near a coordinate', load GET /poi, and execute it with latitude, longitude, and a 25km radius.
Key Endpoints
2 endpoints — the open charge map api provides programmatic access to the world's largest open database of electric vehicle charging locations.
METHOD
PATH
DESCRIPTION
GET
/poi
Search and retrieve charging-station POIs
GET
/referencedata
Retrieve reference lookup tables
GET
/poi
Search and retrieve charging-station POIs
GET
/referencedata
Retrieve reference lookup tables
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Open Charge Map API key is stored encrypted in the Jentic MAXsystem vault and injected as either the 'key' query parameter or the 'x-api-key' header depending on the chosen operation. The raw key never enters the agent's prompt context.
Intent-based discovery
Agents search by intent (e.g., 'find EV charging stations near a coordinate' or 'list charging-station operators') and Jentic returns either /poi or /referencedata with the right parameter schema.
Time to first call
Direct Open Charge Map integration: 1-2 hours for HTTP client, key handling, and reference-data caching. Through Jentic: under 15 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Open Charge Map API through Jentic.
What authentication does the Open Charge Map API use?
The spec defines two API key schemes: 'apiKey' which expects the key as the 'key' query parameter, and 'apiKeyHeader' which expects it in the 'x-api-key' HTTP header. Either is accepted on /poi and /referencedata. Through Jentic, the key is stored encrypted in the MAXsystem vault and injected into whichever location the chosen operation uses.
Can I find chargers near a coordinate with this API?
Yes. GET /poi accepts latitude, longitude, distance, and distanceunit query parameters and returns POIs within the specified radius. You can layer additional filters such as connectiontypeid, operatorid, levelid (charging speed level), and countrycode to narrow results to relevant chargers.
What are the rate limits for the Open Charge Map API?
Open Charge Map does not publish hard per-key limits in the spec; the project asks integrators to register an API key, cache results aggressively (the dataset changes slowly), and avoid tight polling. Production traffic above casual hobby levels should coordinate with the project via openchargemap.org rather than scaling clients indefinitely.
How do I look up a charging station through Jentic?
Search Jentic for 'find EV charging stations near a coordinate', load GET /poi, and execute it with latitude, longitude, distance, and any operator or connection-type filters. Jentic injects the API key from MAXsystem and returns the parsed POI list, including UserComments where present.
Is the Open Charge Map API free?
Yes. The Open Charge Map dataset is freely available under the project's open licence, and API keys are issued at no cost via openchargemap.org. Heavy commercial use is permitted but the project requests attribution and contributions back to the dataset.
How do I resolve operator IDs returned in POI responses?
Call GET /referencedata once and cache the response. The reference payload includes Operators, ConnectionTypes, StatusTypes, and CountryCodes lookup arrays — use the matching ID in each /poi response to display human-readable names without an extra round-trip per record.
GET STARTED