Address search
Use Geocoding endpoints to turn address search into repeatable API requests with documented inputs and JSON responses.
Normalize location search, coordinate lookup, and OSM identifier enrichment through API-key protected geocoding endpoints.
Search addresses, reverse geocode coordinates, and look up Nominatim OSM identifiers through documented Crawlora API endpoints.
Endpoint families
3
Documented params
28
Examples
3
Live catalog snapshot
Active endpoints
3
Methods
GET
Required params
6
Schema refs
3
{
"platform": "Geocoding",
"endpoint": "geocoding-search",
"method": "GET",
"path": "/geocoding/search",
"auth": "apiKey"
}Related use cases
Use cases
Search addresses, reverse geocode coordinates, and look up Nominatim OSM identifiers through documented Crawlora API endpoints.
Use Geocoding endpoints to turn address search into repeatable API requests with documented inputs and JSON responses.
Use Geocoding endpoints to turn reverse geocoding into repeatable API requests with documented inputs and JSON responses.
Use Geocoding endpoints to turn location enrichment into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Geocoding endpoint catalog — 3 endpoints, 28 documented request parameters, and 3 published response schemas — the same catalog Docs and Playground run against.
3 documented Geocoding endpoints, grouped into 3 request families — Lookup, Reverse and Search.
28 request parameters are documented across those Geocoding endpoints, 6 of them required — the full input contract is public before you write any integration code.
3 of the 3 Geocoding endpoints ship a recorded example response, and 3 carry a documented response schema — you can code against the real JSON before the first request.
Geocoding endpoints document their error responses (400, 404, 502 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
3 hosted MCP tools back the Geocoding endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/geocoding/lookup
/geocoding/reverse
/geocoding/search
Endpoint catalog
/geocoding/searchSearches OpenStreetMap places by address. Pass either free-text `q` or structured fields (`street`, `city`, `county`, `state`, `country`, `postalcode`), not both. `limit` defaults to 10 and is clamped to 20; `countrycodes` restricts by ISO 3166-1 alpha-2 country. Each result has its display name, coordinates, category, type, bounding box, importance and address parts. No match returns `404`.
Sampled 14 Oct 2026: 1 item, 15 fields filled in every item. licence: “Data © OpenStreetMap contributors, ODbL 1.0. http://osm.org…”; display_name: median 138 characters.
MCP tool geocoding_search
/geocoding/reverseReturns the nearest OpenStreetMap place for the required `lat` and `lon`. `zoom` (0 to 18, default 18) sets the level of detail; `addressdetails` defaults to true, and `extratags`, `namedetails` and `accept_language` are optional. The place has its display name, category and type, OSM type and id, bounding box, importance and address parts. Out-of-range coordinates return `400`; no place found returns `404`.
Sampled 14 Oct 2026: 14 of 15 fields returned with a value. place_rank: 30; licence: “Data © OpenStreetMap contributors, ODbL 1.0. http://osm.org…”.
MCP tool geocoding_reverse
/geocoding/lookupLooks up OpenStreetMap objects by the required `osm_ids`, a comma-separated list prefixed `N` (node), `W` (way) or `R` (relation), such as `W34633854,N123`. Each place has its display name, category and type, coordinates, bounding box, importance and address parts; `addressdetails` defaults to true, and `extratags`, `namedetails` and `accept_language` are optional. Malformed ids return `400`; no match returns `404`.
Sampled 14 Oct 2026: 1 item, 15 fields filled in every item. licence: “Data © OpenStreetMap contributors, ODbL 1.0. http://osm.org…”; display_name: median 138 characters.
MCP tool geocoding_lookup
Related APIs
Maps & Local Data
Collect local business and place data from Google Maps for location intelligence workflows.
Maps & Local Data
Search ready-made scraped datasets for local business research with filters, facets, geo queries, and repeatable API output.
Maps & Local Data
Compare cities and countries with normalized Numbeo cost-of-living and quality indices. Retrieve city or country detail and current or historical rankings for location research, relocation products, market analysis, and local-data enrichment.
How to scrape Geocoding
Geocoding turns an address into coordinates and coordinates back into an address. Crawlora's 3 geocoding endpoints wrap Nominatim's typed JSONv2 responses — forward search, reverse lookup, and OpenStreetMap identifier resolution — behind one API key.
Pass a free-text q, or the structured street, city, county, state, country, and postalcode fields — use one form or the other, not both in the same call.
Send lat and lon to get the nearest matching place, with zoom controlling how coarse or fine the returned address is.
Pass osm_ids to look up known nodes, ways, or relations directly instead of searching for them again.
addressdetails, extratags, and namedetails add the structured address breakdown, the extra OSM tags, and alternate-language names; countrycodes and accept_language narrow and localize the results.
FAQ
OpenStreetMap, via Nominatim. Responses are typed JSONv2, so you get the same place, address, and bounding-box structure Nominatim returns, normalized and behind a single Crawlora key.
No. Use either the free-text q parameter or the structured street, city, county, state, country, and postalcode fields in a single call. Mixing them is not supported and will not narrow the search the way you expect.
Set accept_language for the response language and namedetails to include the place's alternate names. extratags adds the extra OpenStreetMap tags that are not part of the default response.
Nominatim is a shared community service with its own usage policy, and upstream capacity problems surface as 5xx responses rather than bad data. Design for occasional upstream unavailability and retry rather than assuming every call succeeds.