Area reverse geocode
GET /v1/areas/reverse-geocodeThe area of a given type containing a coordinate. `type_id` is an area
Same call over MCP
Area containing a coordinatearea_reverse_geocodeAuthenticate with an API key from the API & MCP Hub. The same call is available as an MCP tool at the same price.
Inputs
Before you call it
- type_id
- The area type id names one geography layer (district, ward, local authority). A point sits inside exactly one area per layer, so the id is required; the hierarchy area_resolve returns lists the layers and their ids.
- lat
- Coordinates are WGS84 latitude and longitude, the order a map gives them. A postcode is accepted wherever
locationis, and is usually the easier input.
Request
Calling GET /v1/areas/reverse-geocode
curl "https://api.marketcode.ai/v1/areas/reverse-geocode?lat=51.4613&lng=-0.0106&type_id=3977a3cf-ccdb-4be4-90ec-ad43cacb0b42" \
-H "Authorization: Bearer $MARKETCODE_API_KEY"Send your API key as a Bearer token. Every response carries credits_charged and credits_remaining.
Inputs
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| lat | Query | number | Yes | |
| lng | Query | number | Yes | |
| type_id | Query | string | Yes | Area type UUID — which geography layer to answer for (ward, LAD, LSOA, …). Required: a point sits inside one area per layer, so without it the answer is ambiguous. |
Response
What GET /v1/areas/reverse-geocode returns for a real request
curl "https://api.marketcode.ai/v1/areas/reverse-geocode?lat=51.4613&lng=-0.0106&type_id=3977a3cf-ccdb-4be4-90ec-ad43cacb0b42" \
-H "Authorization: Bearer $MARKETCODE_API_KEY"{
"country": "UK",
"query": {
"lat": 51.4613,
"lng": -0.0106,
"type_id": "3977a3cf-ccdb-4be4-90ec-ad43cacb0b42"
},
"data": {
"id": "e7eb27fb-677c-4b58-b9ba-414769855966",
"name": "Lewisham",
"area_type_id": "3977a3cf-ccdb-4be4-90ec-ad43cacb0b42",
"area_type_name": null,
"analytics_area_id": null
},
"credits_charged": 0
}A real response, captured from production and trimmed: arrays to three items, long strings shortened, volatile keys dropped.
Response
Response fields
| Field | Type | Example |
|---|---|---|
| country | string | UK |
| query | object | |
| query.lat | number | 51.4613 |
| query.lng | number | -0.0106 |
| query.type_id | string | 3977a3cf-ccdb-4be4-90ec-ad43cacb0b42 |
| data | object | |
| data.id | string | e7eb27fb-677c-4b58-b9ba-414769855966 |
| data.name | string | Lewisham |
| data.area_type_id | string | 3977a3cf-ccdb-4be4-90ec-ad43cacb0b42 |
| data.area_type_name | null | |
| data.analytics_area_id | null | |
| credits_charged | integer | 0 |
Fields observed in the example response above; a field the example did not exercise is not listed.
Price and licence
What it costs, and where the data comes from
Area reverse geocode is free over MCP and over REST, and the two surfaces share one credit balance. Free calls need a signed-in account or an API key and appear in your usage, but they never touch your balance.
Credits are granted on sign-up and bought in packs; the pricing page lists every call.
Related
Endpoints used with Area reverse geocode
- One composed document for an area5 credits
area_reportThe market for one area, as one document: sourcing readiness per strategy from the coverage register, the commercial capital and rent indices with rated stock, the planning decision record for the authority, and the live listing stock.Same category - Data coverage register for a local authorityFree
data_coverageThe data-coverage register for a local authority — read it before the data: per-field non-null and source shares over every unit in the authority (floor area, bedrooms, year built, EPC, last sale, tenure…), which designation flags were checked and how fully, how many units carry a registered lease or a hereditament, whether official planning data covers the authority and how deep it goes (applications, link shares, latest decision), and how much of the live listing stock the sweep has dated. `area` is a GSS code (E09000032), a local authority name (Wandsworth) or a warehouse area id. State the coverage before quoting a share from a thin field. UK only.Same category - Resolve an area nameFree
area_resolveResolve an area name or code ("Hackney", "E5") to its area_id, centroidSame category
FAQ
Questions about Area reverse geocode
How much does `area_reverse_geocode` cost?
+
Area reverse geocode is free over MCP and over REST, and the two surfaces share one credit balance. Free calls need a signed-in account or an API key and appear in your usage, but they never touch your balance.
How do I authenticate?
+
Send your API key as a Bearer token in the Authorization header. Keys are created in the API & MCP Hub, shown once and revocable. Every response carries the credits charged and your remaining balance.
Is there an MCP version?
+
Yes. The area_reverse_geocode tool on the MarketCode MCP server is the same call at the same price, signed in with OAuth rather than a key, so Claude, ChatGPT, Codex and Cursor can run it in a conversation.
Where does the data come from?
+
The answer is computed by MarketCode. Coverage is the UK.
Does `area_reverse_geocode` change anything?
+
No. The tool is annotated read-only on the server, so it never writes to your data or ours and an assistant can call it without a confirmation step.
Try Area reverse geocode on a real address.
30-minute call. We'll provision a key and walk through the endpoint on your use case.