OpenStreetMap
OpenStreetMap (OSM) is a collaborative project to create a free, editable map of the world. The OSM ecosystem exposes a family of public REST APIs: the main editing API (v0.6) for CRUD operations on map data, the Overpass API for complex read-only geospatial queries, and the Nominatim API for forward and reverse geocoding. Map data is licensed under the Open Database License (ODbL) 1.0 and tile imagery under CC BY-SA 2.0.
OpenStreetMap publishes 11 API contracts indexed on the APIs.io network, including Capabilities API, Changesets API, Map Data API, and 8 more. Tagged areas include Geospatial, Mapping, Open Data, Geocoding, and Editing.
The OpenStreetMap catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.
OpenStreetMap’s developer surface includes authentication, developer portal, documentation, engineering blog, support, and 24 more developer resources.
What this lets a business do 1
Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →
Kin Score
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 |
|---|---|---|---|---|
| Geospatial and Maps (OGC standards) | mixed | 29.3 | - | - |
| Open Data Portals (CKAN / DCAT) | mixed | 29.3 | - | - |
| Raycast Store Extensions (first-party publishers + community-wrapped products) | mixed | 29.3 | - | - |
| Obsidian Community Plugins (third-party APIs the Obsidian plugin ecosystem integrates) | mixed | 29.3 | - | - |
| Overture Maps Foundation (members + data contributors) | mixed | 29.3 | - | - |
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 2
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.
APIs 11
Individual APIs this provider publishes, each with its own machine-readable definition.
OpenStreetMap Overpass API
The Overpass API is a read-only database engine for complex geospatial queries against the OSM dataset. Accepts Overpass QL or XML queries and returns results in XML, JSON, GeoJ...
OpenStreetMap Capabilities API
API version and limits
OpenStreetMap Changesets API
Changeset management for grouped edits
OpenStreetMap Map Data API
Bulk map data retrieval by bounding box
OpenStreetMap Nodes API
OSM node (point) operations
OpenStreetMap Notes API
Community map notes
OpenStreetMap Relations API
OSM relation operations
OpenStreetMap Users API
User account information
OpenStreetMap Ways API
OSM way (line/polygon) operations
OpenStreetMap Geocoding API
Forward geocoding, reverse geocoding, and OSM object lookup
OpenStreetMap Status API
Server status and version information
Scroll for all 11
Postman Collections 8
Ready-to-run Postman collections for exercising this provider's APIs.
Scroll for all 8
Open Collections 11
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
OpenStreetMap API v0.6 Capabilities API
OPEN COLLECTIONOpenStreetMap API v0.6 Capabilities Changesets API
OPEN COLLECTIONOpenStreetMap Nominatim Geocoding API
OPEN COLLECTIONOpenStreetMap API v0.6
OPEN COLLECTIONOpenStreetMap API v0.6 Capabilities Map Data API
OPEN COLLECTIONOpenStreetMap API v0.6 Capabilities Nodes API
OPEN COLLECTIONOpenStreetMap API v0.6 Capabilities Notes API
OPEN COLLECTIONOpenStreetMap API v0.6 Capabilities Relations API
OPEN COLLECTIONOpenStreetMap Nominatim Geocoding Status API
OPEN COLLECTIONOpenStreetMap API v0.6 Capabilities Users API
OPEN COLLECTIONOpenStreetMap API v0.6 Capabilities Ways API
OPEN COLLECTIONScroll for all 11
OpenStreetMap API pricing
Not yet checked against OpenStreetMap's own pricing page. Compiled by API Evangelist on 2026-05-04 from www.openstreetmap.org/; confirm before you rely on a figure. A free plan or tier is listed.
| Plan | Price |
|---|---|
| Public API (Acceptable Use) freemium | Free |
| Self-Hosted (Recommended for Production) freemium | — |
| Third-Party Providers paid | — |
Plan details, limits and sources →
Rate limits
- Tile server (osm.org): 2 requests per second
- Nominatim (osm.org): 1 requests per second
- Overpass API (overpass-api.de): 2 concurrent
Compiled by API Evangelist, not yet checked against OpenStreetMap's documentation. All 4 limits →
Pricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Openstreetmap Rate Limits
RATE LIMITSService Levels 1
Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.
FinOps 1
Cost, billing, and metering signals for API financial operations.
Openstreetmap Finops
FINOPSFeatures 16
Notable capabilities this provider offers.
Scroll for all 16
Semantic Vocabularies 1
JSON-LD contexts and semantic vocabularies used across these APIs.
Openstreetmap Context
JSON-LDSpectral Rules 1
Spectral governance rulesets for linting and validating these APIs.
OpenStreetMap — jsonschema rules
SPECTRALJSON Schema 9
Standalone JSON Schema definitions for this provider's data models.
Capabilities
JSON SCHEMAChangeset
JSON SCHEMAOpenStreetMap Node
JSON SCHEMANote
JSON SCHEMANoteCollection
JSON SCHEMAOSMData
JSON SCHEMARelation
JSON SCHEMAUser
JSON SCHEMAWay
JSON SCHEMAScroll for all 9
JSON Structure 1
JSON Structure definitions describing this provider's data shapes.
Openstreetmap Structure
JSON STRUCTURESecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 6
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 6
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
Source (apis.yml)
OpenStreetMap API — frequently asked questions
Does OpenStreetMap have an API?
Yes. APIs.io lists 11 APIs from OpenStreetMap, including OpenStreetMap Overpass API, OpenStreetMap Capabilities API and OpenStreetMap Changesets API, and 8 more.
Is there an OpenAPI specification for the OpenStreetMap API?
Yes. APIs.io indexes 10 OpenAPI specifications for OpenStreetMap, each linked for download from this page.
How do I authenticate with the OpenStreetMap API?
OpenStreetMap documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Openstreetmap Authentication.
How much does the OpenStreetMap API cost?
APIs.io lists 3 pricing plans for OpenStreetMap, with each plan's price, limits and inclusions under Pricing on this page.
Is the OpenStreetMap API ready for AI agents?
OpenStreetMap has a Kin Score of 44.4 out of 100 (developing) and an Agent Readiness score of 28.8 (agent-ready), 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.