Open Charge Map
Open Charge Map is the global public registry of electric vehicle charging locations, established in 2011 as a non-commercial, community-driven project. The platform maintains a crowdsourced dataset of 300,000+ charging points worldwide, combining manually entered data with imported open data from government registries and charging networks. The REST API enables developers to search and retrieve POI (Points of Interest) data on EV charging stations, including location details, equipment specifications, connection types, operator information, and user-submitted check-ins and photos. Data can be filtered by geographic coordinates, bounding box, country, operator, connection type, charging level, and operational status. The API is free to use with an API key registration and supports both read (GET) and write (POST) operations for contributing new charging location data.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Open Charge Map the way a machine reads it — 47 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Open Charge Map scores 34.1/100 (thin), with a separate agent-readiness read of 25/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Open Charge Map's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/openchargemap/"
title="Open Charge Map on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/openchargemap.svg"
alt="Open Charge Map Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/openchargemap/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/openchargemap/"
title="Open Charge Map on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/openchargemap/card.svg"
alt="Open Charge Map Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Open Charge Map
Each block below is one kind of artifact we hold for Open Charge Map. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 9
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Open Charge Map POI API
Primary REST API for searching and retrieving EV charging station data (Points of Interest) from the Open Charge Map global registry. Supports geographic search by latitude/long...
Open Charge Map Reference Data API
REST API endpoint returning core reference data used for interpreting POI results, including connection types, charging levels, operators, countries, status types, usage types, ...
Open Charge Map POI Submit API
REST API endpoint for contributing new EV charging station data or updating existing POI records in the Open Charge Map global registry. Requires an authenticated API key associ...
Open Charge Map Comment API
The Comment API from Open Charge Map — 1 operation(s) for comment.
Open Charge Map Mediaitem API
The Mediaitem API from Open Charge Map — 1 operation(s) for mediaitem.
Open Charge Map Openapi API
The Openapi API from Open Charge Map — 1 operation(s) for openapi.
Open Charge Map Poi API
The Poi API from Open Charge Map — 1 operation(s) for poi.
Open Charge Map Profile API
The Profile API from Open Charge Map — 1 operation(s) for profile.
Open Charge Map Referencedata API
The Referencedata API from Open Charge Map — 1 operation(s) for referencedata.
Scroll within the panel for all 9 ·
Open Collections 7
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONOpen Charge Map Comment API
OPEN COLLECTIONOpen Charge Map Comment Mediaitem API
OPEN COLLECTIONOpen Charge Map Comment Openapi API
OPEN COLLECTIONOpen Charge Map Comment Poi API
OPEN COLLECTIONOpen Charge Map Comment Profile API
OPEN COLLECTIONOpen Charge Map Comment Referencedata API
OPEN COLLECTIONScroll within the panel for all 7 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Openchargemap Plans
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Openchargemap Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Openchargemap Finops
FINOPSSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Open Charge Map API Rules
SPECTRALJSON Schema 20
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AddressInfo
JSON SCHEMAAuthenticationResult
JSON SCHEMACheckinStatusType
JSON SCHEMAConnectionInfo
JSON SCHEMAConnectionType
JSON SCHEMACoreReferenceData
JSON SCHEMACountry
JSON SCHEMADataProvider
JSON SCHEMALevelType
JSON SCHEMAMediaItem
JSON SCHEMAOperatorInfo
JSON SCHEMAPOI
JSON SCHEMAStatusType
JSON SCHEMASubmissionStatusType
JSON SCHEMASupplyType
JSON SCHEMAUsageType
JSON SCHEMAUserComment
JSON SCHEMAUserCommentType
JSON SCHEMAUserInfo
JSON SCHEMAUserProfile
JSON SCHEMAScroll within the panel for all 20 ·
Examples 4
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Open Charge Map — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/openchargemap · machine-readable index on apis.io
This is an independent, third-party profile of Open Charge Map, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.