Geocoding · two endpoints

Geocoding, both directions.

Forward (address → coordinates) for placing pins on a map. Reverse (coordinates → address) for telling users what they tapped on. One coverage footprint of 240+ countries, one explicit accuracy_type field on every response.

Pick a direction

One coverage footprint. Two endpoints.

POST · /v1/geocode

Forward geocoding

Address text in. Coordinates + accuracy type out. Best for placing pins on a map, routing, distance calculations, last-mile delivery, and CRM enrichment.

Try forward $0.0012 · req
POST · /v1/reverse

Reverse geocoding

Lat/lng in. Structured address + accuracy type out. Best for "what's here" lookups — mobile apps, geofencing, IoT pings, and on-map address-on-tap experiences.

Try reverse $0.0012 · req
Same response contract for both

Every result states its accuracy.

Every response — forward or reverse — includes an explicit accuracy_type so your application decides what to trust. Coverage and quality vary by country.