Developers and agents

A JSON API, an MCP server and docs written for LLMs.

Try the API

Response appears here.

Reference

EndpointParametersReturns
GET /searchq (required), limit 1–50, lat+lon to prefer nearby, geometry=true for street and river linesresults with name, kind, category, town, county, lat, lon, answer; plus confidence, more, near, postcode
GET /suggestq (required), limit 1–20, lat+lonresults with name, kind, town, county, lat, lon
GET /reverselat, lon (required), kind (settlement, street, feature, poi), limit 1–50postcode, areas, settlement, street, nearby results with distance_m

Send your key as X-API-Key. Errors are {"error": "…"} with 400, 401, 403 (key not allowed from this site), 429 (slow down; see Retry-After) or 503. Every response has an attribution string that must be shown wherever results are. The full spec is at /openapi.yaml.

Ties: several answer: true results with the same name are equally good places (Newport, say), so ask which; more: true means not all fitted.

MCP server

Tools: search_places, describe_location, resolve_places (up to 100 at once), map_link.


  

Docs for LLMs

Limits

Each key allows 600 requests a minute.