How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
OpenStreetMap

OpenStreetMap Geocoding API

Forward geocoding, reverse geocoding, and OSM object lookup

Documentation Provider Profile APIs.io OpenAPI GitHub

OpenStreetMap Geocoding API is one of 11 APIs that OpenStreetMap publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Geocoding. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 3 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 4.4.0.

Requests are made against a single base URL, https://nominatim.openstreetmap.org.

3 operations 3 paths 4 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
4.4.0
Base URL
https://overpass-api.de/api
Contact
Nominatim Project
License
ODbL 1.0
Resource Areas
1

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 GET. Each is listed below with its method, path, parameters, and response codes.

Geocoding 3

Forward geocoding, reverse geocoding, and OSM object lookup

GET
/search
Forward geocode (search by address/name)
geocodeSearch 18 params → 200429
GET
/reverse
Reverse geocode (coordinates to address)
geocodeReverse 8 params → 200404
GET
/lookup
Look up OSM objects by ID
lookupOSMObjects 5 params → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are SearchResult (15 properties), Address (15 properties). Each schema is shown below with its type and property counts.

Address
object
Structured address components
15 properties
ReverseResult
SearchResult
object
A single geocoding result
15 properties
SearchResults
array

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openstreetmap-geocoding-api-openapi.yml Raw ↑

Other APIs OpenStreetMap publishes across the network.

OpenStreetMap Overpass API
AE Profile APIs.io
OpenStreetMap Capabilities API
AE Profile APIs.io
OpenStreetMap Changesets API
AE Profile APIs.io
OpenStreetMap Map Data API
AE Profile APIs.io
OpenStreetMap Nodes API
AE Profile APIs.io
OpenStreetMap Notes API
AE Profile APIs.io
OpenStreetMap Relations API
AE Profile APIs.io
OpenStreetMap Users API
AE Profile APIs.io
OpenStreetMap Ways API
AE Profile APIs.io
OpenStreetMap Status API
AE Profile APIs.io
#Geocoding
← Back to O APIs
API Details
ID
openstreetmap:openstreetmap-geocoding-api
Base URL
https://overpass-api.de/api
Docs
https://wiki.openstreetmap.org/wiki/Overpass_API
Provider
OpenStreetMap
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=openstreetmap-geocoding-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/openstreetmap-geocoding-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of OpenStreetMap Geocoding API, 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.