Skip to content
Geo Suite

Geocoding, reverse-geocoding & H3 — designed for India.

Reverse-geocodes anywhere in India down to ward + pincode + locality. Bharat-language script normalisation built-in. Same shape for humans and agents.

Indian addresses parsed
88M+
Median latency (ap-south-1)
24ms
Languages normalised
22
Per-coord cost
5 tokens

Endpoints

MethodPathCostTier
GET/v1/geo/reverse?lat=&lng=
Coord → ward + pincode + city + nearest road.
5free
GET/v1/geo/lat-lng-to-h3
Coord → H3 cell at any res 0-15.
1free
GET/v1/geo/h3-to-lat-lng
H3 cell → centre coord + boundary verts.
1free
GET/v1/geo/forward?q=
Free-text address → ranked candidates.
10pro

Try it from your terminal

No SDK install. Plain HTTP. Works the same from a Lambda, a Jupyter notebook, or an LLM tool call.

curl -H "X-API-Key: $GR_KEY" \
  "https://api.gridrock.ai/v1/geo/reverse?lat=19.0760&lng=72.8777" | jq
For agents

Drop into Claude / OpenAI / LangGraph as geo_reverse

Bind once. Call on demand. Get back a verbose, deterministic shape that any LLM can reason over without prompt engineering.

# Claude tool-use
{
  "name": "geo_reverse",
  "input": { "lat": 19.0760, "lng": 72.8777 }
}
# → { city: "Mumbai", ward: "G/N", pincode: "400028", h3: "8861aacd1bfffff", ... }
Why Bharat

Western geocoders treat India as one big admin layer. We model 7,500+ municipal wards (BMC, BBMP, GHMC, MCD, KMC, PMC, GCC) and 19,000 pincodes natively, so your app speaks the language of Indian governance.

Related

Start building with Geo — free

No card. No sales call. 60-second self-serve, agents included.

Get a free key