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.

Open Charge Map publishes 9 API contracts indexed on the APIs.io network, including Comment API, Mediaitem API, Poi API, and 6 more. Tagged areas include Electric Vehicles, EV Charging, Charging Stations, Points of Interest, and Open Data.

The Open Charge Map catalog on APIs.io includes 1 Spectral governance ruleset.

Open Charge Map’s developer surface includes authentication, documentation, GitHub presence, and 12 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

24.7/100 emerging ▬ flat Agent 26/100 agent aware Front door AI 2/6 trace Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreeSelf serve⚡ Free to try

1 published contract

Electric Vehicles EV Charging Charging Stations Points of Interest Open Data Geospatial Transportation Clean Energy Crowdsourced Registry

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 24.7/100 · emerging

Contract Quality 9.3 / 19

Developer Ergonomics 2.1 / 15

Access Clarity 0.8 / 15

Operational Transparency 1.3 / 10

Contract Governance 0.9 / 9

Discoverability 5.0 / 8

Regulatory Posture 1.5 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 26/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Energy & Utilities regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/openchargemap/"><img src="https://apis.io/badge/openchargemap/card.svg" alt="Open Charge Map on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 5.3 — up to +18.9 composite points
Developer Ergonomics scores 14.3 — up to +17.1 composite points
Contract Quality scores 49.8 — up to +12.6 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/openchargemap/apis.yml: open an issue on github.com/api-evangelist/openchargemap to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
EV Charging (charging, roaming, e-mobility)	coverage	46.6	-	-
LF Energy Projects and Members (grid, DER, EV charging open source)	coverage	46.6	-	-
Overture Maps Foundation (members + data contributors)	coverage	46.6	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 9

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 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 Open API

The Open API API from Open Charge Map — 1 operation(s) for open api.

Open Charge Map Reference Data API

The Reference Data API from Open Charge Map — 1 operation(s) for reference data.

Results Per Request Limit: 250
API Calls Per Connection (Connector Throttle): 100

Compiled by API Evangelist, not yet checked against Open Charge Map's documentation. All 4 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Openchargemap Plans

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Openchargemap Rate Limits

4 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Open Charge Map

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Openchargemap Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Open Charge Map — jsonschema rules

5 rules · 3 warnings 2 info

SPECTRAL

14 properties

JSON SCHEMA

Scroll for all 20

Examples 4

Example request and response payloads for these APIs.

Authenticate

3 fields

EXAMPLE

Geo Bounding Box Search

3 fields

EXAMPLE

Poi Search

3 fields

EXAMPLE

Reference Data

3 fields

EXAMPLE

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Openchargemap Authentication

apiKey/http · 3 schemes

SECURITY

Openchargemap Domain Security

TLSv1.3 · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Openchargemap Agentic Access

6 operations · 3 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Build 2

SDKs, sample code, and the tooling you integrate with

GitHub

GitHub

GitHubOrg

GitHubOrg

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

Community

Community

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

Plans

Plans

FinOps

FinOps

Company 2

The organization behind the API

Website

Website

About

About

Other 2

Properties that don't map to a standard resource type

Developer

Developer

Apps

Apps

Source (apis.yml)

aid: openchargemap
name: Open Charge Map
description: '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.

  '
type: Index
deliveryModel:
  model: saas
  license_evidence:
    not_product:
    - openchargemap/ocm-system
  open_source: unknown
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: low
  source:
  - openapi
  - pricing
  - repository-not-product
  generated: '2026-09-25'
  method: derived
accessModel:
  pricing: free
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Free · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/openchargemap.png
url: https://raw.githubusercontent.com/api-evangelist/openchargemap/refs/heads/main/apis.yml
created: '2026-06-13'
modified: '2026-06-13'
specificationVersion: '0.23'
tags:
- Electric Vehicles
- EV Charging
- Charging Stations
- Points of Interest
- Open Data
- Geospatial
- Transportation
- Clean Energy
- Crowdsourced
- Registry
apis:
- name: Open Charge Map POI API
  description: '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/longitude with distance radius, bounding box filtering,
    country filtering, and filtering by operator, connection type, charging level, usage type, and operational status. Returns
    full POI data including address, equipment details, connection types, power levels, operator info, and user comments.
    Supports compact and verbose output formats in JSON. An API key is required and passed as a query parameter or HTTP header.

    '
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://openchargemap.org/site/develop/api
  baseURL: https://api.openchargemap.io/v3
  tags:
  - EV Charging
  - Points of Interest
  - Geospatial Search
  - Charging Stations
  properties:
  - type: Documentation
    url: https://openchargemap.org/site/develop/api
  - type: GitHub
    url: https://github.com/openchargemap/ocm-system
- name: Open Charge Map Reference Data API
  description: 'REST API endpoint returning core reference data used for interpreting POI results, including connection types,
    charging levels, operators, countries, status types, usage types, supply types (AC/DC), and submission status types. This
    data provides the lookup tables needed to decode numeric ID fields returned in POI results. Can be filtered by country.
    Returns reference data in JSON format with an API key.

    '
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://openchargemap.org/site/develop/api
  baseURL: https://api.openchargemap.io/v3
  tags:
  - Reference Data
  - Connection Types
  - Operator
  - Countries
  tags_raw:
  - Reference Data
  - Connection Types
  - Operators
  - Countries
  properties:
  - type: Documentation
    url: https://openchargemap.org/site/develop/api
- name: Open Charge Map POI Submit API
  description: '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 associated with a registered Open Charge Map user account.
    Submitted data is reviewed and integrated into the community dataset. Supports adding new charging locations with full
    address, equipment, connection type, and operator details.

    '
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://openchargemap.org/site/develop/api
  baseURL: https://api.openchargemap.io/v3
  tags:
  - Submit
  - Contribute
  - Crowdsourced
  - Data Entry
  properties:
  - type: Documentation
    url: https://openchargemap.org/site/develop/api
- aid: openchargemap:openchargemap-comment-api
  name: Open Charge Map Comment API
  description: The Comment API from Open Charge Map — 1 operation(s) for comment.
  humanURL: https://openchargemap.org/site/develop/api
  baseURL: https://api.openchargemap.io/v3
  tags:
  - Comment
  properties:
  - type: OpenAPI
    url: openapi/openchargemap-comment-api-openapi.yml
- aid: openchargemap:openchargemap-mediaitem-api
  name: Open Charge Map Mediaitem API
  description: The Mediaitem API from Open Charge Map — 1 operation(s) for mediaitem.
  humanURL: https://openchargemap.org/site/develop/api
  baseURL: https://api.openchargemap.io/v3
  tags:
  - Mediaitem
  properties:
  - type: OpenAPI
    url: openapi/openchargemap-mediaitem-api-openapi.yml
- aid: openchargemap:openchargemap-poi-api
  name: Open Charge Map Poi API
  description: The Poi API from Open Charge Map — 1 operation(s) for poi.
  humanURL: https://openchargemap.org/site/develop/api
  baseURL: https://api.openchargemap.io/v3
  tags:
  - POI
  tags_raw:
  - Poi
  properties:
  - type: OpenAPI
    url: openapi/openchargemap-poi-api-openapi.yml
- aid: openchargemap:openchargemap-profile-api
  name: Open Charge Map Profile API
  description: The Profile API from Open Charge Map — 1 operation(s) for profile.
  humanURL: https://openchargemap.org/site/develop/api
  baseURL: https://api.openchargemap.io/v3
  tags:
  - Profiles
  tags_raw:
  - Profile
  properties:
  - type: OpenAPI
    url: openapi/openchargemap-profile-api-openapi.yml
- aid: openchargemap:openchargemap-open-api-api
  name: Open Charge Map Open API
  description: The Open API API from Open Charge Map — 1 operation(s) for open api.
  humanURL: https://openchargemap.org/site/develop/api
  baseURL: https://api.openchargemap.io/v3
  tags:
  - OpenAPI
  tags_raw:
  - Open API
  properties:
  - type: OpenAPI
    url: openapi/openchargemap-open-api-api-openapi.yml
- aid: openchargemap:openchargemap-reference-data-api
  name: Open Charge Map Reference Data API
  description: The Reference Data API from Open Charge Map — 1 operation(s) for reference data.
  humanURL: https://openchargemap.org/site/develop/api
  baseURL: https://api.openchargemap.io/v3
  tags:
  - Reference Data
  properties:
  - type: OpenAPI
    url: openapi/openchargemap-reference-data-api-openapi.yml
common:
- type: AgenticAccess
  url: agentic-access/openchargemap-agentic-access.yml
- type: DomainSecurity
  url: security/openchargemap-domain-security.yml
- type: Authentication
  url: authentication/openchargemap-authentication.yml
- type: Website
  url: https://openchargemap.org/
- type: Documentation
  url: https://openchargemap.org/site/develop/api
- type: Developer
  url: https://openchargemap.org/site/develop
- type: GitHub
  url: https://github.com/openchargemap/ocm-system
- type: GitHubOrg
  url: https://github.com/openchargemap
- type: Community
  url: https://community.openchargemap.org/
- type: Apps
  url: https://openchargemap.org/site/develop/apps
- type: TermsOfService
  url: https://openchargemap.org/site/about/terms
- type: About
  url: https://openchargemap.org/site/about
- type: Plans
  url: plans/openchargemap-plans.yml
- type: RateLimits
  url: rate-limits/openchargemap-rate-limits.yml
- type: FinOps
  url: finops/openchargemap-finops.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Open Charge Map API — frequently asked questions

Does Open Charge Map have an API?

Yes. APIs.io lists 9 APIs from Open Charge Map, including Open Charge Map POI API, Open Charge Map Reference Data API and Open Charge Map POI Submit API, and 6 more.

Is there an OpenAPI specification for the Open Charge Map API?

Yes. APIs.io indexes 6 OpenAPI specifications for Open Charge Map, each linked for download from this page.

How do I authenticate with the Open Charge Map API?

Open Charge Map uses bearer-token authentication (apiKey/http · 3 schemes). The details are profiled on APIs.io as Openchargemap Authentication.

How much does the Open Charge Map API cost?

APIs.io lists 2 pricing plans for Open Charge Map, with each plan's price, limits and inclusions under Pricing on this page.

Is the Open Charge Map API ready for AI agents?

Open Charge Map has a Kin Score of 24.7 out of 100 (emerging) and an Agent Readiness score of 25.6 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/openchargemap"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/openchargemap/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/openchargemap/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.