OpenCage
Berlin geocoding API that turns addresses into coordinates and back, built on open data
Quick Overview
| Company | OpenCage GmbH |
|---|---|
| Category | Maps & Navigation |
| Headquarters | Berlin, Germany |
| EU Presence | EU (Germany) |
| Open Source | No |
| Pricing | Free tier with 2,500 requests/day (testing only); X-Small €45/month (10,000/day) up to Large €900/month (300,000/day); custom Enterprise pricing from €1,800/month |
| Free Option | Free tier, 2,500 requests/day, no credit card required |
| Replaces | Google Geocoding API, Mapbox Geocoding API |
Detailed Review
OpenCage does one thing: geocoding. Forward geocoding turns an address into coordinates, reverse geocoding turns coordinates into an address, and the API aggregates OpenStreetMap alongside other open datasets rather than maintaining a single proprietary index. For a product that already has its own maps and routing and just needs addresses resolved reliably, that focus is the appeal — nothing to configure that isn't geocoding.
OpenCage GmbH is registered in Berlin. Pricing is published in full and is unusually transparent for this category: a free tier of 2,500 requests a day for testing, then X-Small at €45 a month for 10,000 requests a day up to Large at €900 a month for 300,000, with Enterprise from €1,800 a month, all inclusive of VAT and with no surge pricing.
The limits are the flip side of the focus: no map tiles, no routing, and free-tier accounts are deleted after three months of inactivity.
What OpenCage does well
- Forward and reverse geocoding, nothing else to learn
- Built on OpenStreetMap and other open data sources
- Full price list published, VAT-inclusive, no surge pricing
- Free tier for testing, no credit card required
- German company, EU jurisdiction
Where OpenCage falls short
- Geocoding only — no tiles or routing
- Free-tier accounts are deleted after three months idle
- No certification published
- Aimed at developers, not end users
Standout feature. A geocoding-only API with every tier's price and its VAT status on the page, and no surge pricing to plan around.
Pros and Cons
Pros
- Forward and reverse geocoding, nothing else to learn
- Built on OpenStreetMap and other open data sources
- Full price list published, VAT-inclusive, no surge pricing
- Free tier for testing, no credit card required
- German company, EU jurisdiction
Cons
- Geocoding only — no tiles or routing
- Free-tier accounts are deleted after three months idle
- No certification published
- Aimed at developers, not end users
Alternatives to OpenCage
Frequently Asked Questions
What is OpenCage?
OpenCage does one thing: geocoding. Forward geocoding turns an address into coordinates, reverse geocoding turns coordinates into an address, and the API aggregates OpenStreetMap alongside other open datasets rather than maintaining a single proprietary index. For a product that already has its own maps and routing and just needs addresses resolved reliably, that focus is the appeal — nothing to configure that isn't geocoding.
Where is OpenCage based?
OpenCage operates from Berlin, Germany, which places it under EU (Germany).
What does OpenCage cost?
Free tier with 2,500 requests/day (testing only); X-Small €45/month (10,000/day) up to Large €900/month (300,000/day); custom Enterprise pricing from €1,800/month. Free tier, 2,500 requests/day, no credit card required.
Who is OpenCage best for?
Developers who need addresses turned into coordinates and back. A geocoding-only API with every tier's price and its VAT status on the page, and no surge pricing to plan around.
What are the drawbacks of OpenCage?
Geocoding only — no tiles or routing. Free-tier accounts are deleted after three months idle. No certification published. Aimed at developers, not end users.