Head to head · Geocoding · October 2026 research run

LocationIQ vs OpenCage Geocoding API

OpenCage Geocoding API scores 69.8 (B) on agent readiness against LocationIQ's 62.2 (B), and leads in 5 of 7 scored categories. LocationIQ leads on security & auth. Both do geocoding.

Best maps, geocoding and places APIs for AI agents · All 153 maps comparisons

Which one, for what

LocationIQ B

Best for A prototype or a cost-sensitive geocoding and routing job, with EU and US endpoints.

Ahead on

  • Security & auth, 55 against 44

Also in its favour

  • Rated higher by the reviewer agents, 4.5 against 3.5 out of 5
  • No incidents deducted, where OpenCage Geocoding API loses 3 points for them

Watch for

No changelog, release notes or blog

OpenCage Geocoding API B

Best for Bulk or repeated geocoding where results go into a database, and for EU data residency.

Ahead on

  • Agent ergonomics, 86 against 74
  • Payments & pricing, 53 against 45
  • Maintenance & community, 86 against 3
  • Transparency & trust, 85 against 61

Also in its favour

  • Runs on your own machine

Watch for

Geocoding only, no place search or routing

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community OpenCage Geocoding API +83

LocationIQ 3

We found no changelog, release notes or blog on 4 November (docs.locationiq.com/changelog, locationiq.com/changelog and locationiq.com/blog all return 404, and llms.txt lists none), so there's no dated API change to count. The terms were updated 31 March 2026, which isn't an API change (0). No dated entries in the last 90 days (0). No public changelog. Support is by email, which we didn't test (3). The official Python client hasn't changed since 30 March 2020 (0). Nothing current to judge package health by (0). The status page shows the service is run and watched, which this checklist doesn't capture. 0+0+3+0+0 = 3.

OpenCage Geocoding API 86

The newest API changelog entry is 15 October 2026 (SMDG port terminal codes), and the Python SDK released 3.5.0 on 28 October 2026, both within 30 days (30). Dated changes in the last 90 days include improved IATA airport code geocoding (blog, 7 October), the 15 October changelog entry and Python SDK 3.5.0, with spreadsheet upload improvements on 14 August (20). Dependabot pull requests on the MCP repo are merged within days, the latest on 1 November. We couldn't see issue reply times from git (15). In the official MCP registry as io.github.OpenCageData/opencage-geocoding-mcp, and the Python SDK is current at 3.5.0 (15). The MCP's CI lints, type-checks and builds on Node 20, 22 and 24 but runs no tests, and npm still serves 1.0.3 from 11 September 2025 while the repo is at 1.0.5 (6).

Transparency & trust OpenCage Geocoding API +24

LocationIQ 61

Closed service with readable terms, updated 31 March 2026, under the laws of Telangana, India (15). The terms are specific on storage, 48 hours on Free and for as long as you're a customer on paid plans, with no server-side tile caching. The privacy policy at locationiq.com/privacy was last updated 22 May 2020, says IP addresses are stored to check for abuse with no retention period, and links a DPA (15). No deprecation policy or notices found (0). Stripe, Zoho and Google Analytics named without locations. Data centre regions are visible on the status page, not in the policy (10).

OpenCage Geocoding API 85

Closed service with clear terms, an MIT MCP server and open-source SDKs (20). Results may be stored permanently, even after cancelling. Query logs are deleted after six months and never used to train AI, no_record turns query logging off, and the DPA is public on GitHub. The GDPR page was updated 22 July 2026 with its change history (30). A dated API changelog that announces deprecations, such as the jsonp parameter on 11 May 2026, which keeps working for existing customers. No written deprecation policy (14). Seven subprocessors with locations, and hosting at Hetzner in Germany and Finland with backups in Switzerland (20).

Agent ergonomics OpenCage Geocoding API +12

LocationIQ 74

No MCP server. Responses can be sized with limit, format, addressdetails and dedupe, and a /balance endpoint reports what's left (20). countrycodes, viewbox and bounded on search, and tag filters on nearby (17). Error messages tell a burst (Rate Limited Second) from a spent day (Rate Limited Day) and a missing scope from a bad key (18). Every call reads and is safe to retry, but there are no tool annotations to give (12). Few required parameters, but the official Python client's last commit is 30 March 2020 and the Leaflet plugin's 15 June 2020 (7).

OpenCage Geocoding API 86

Three compact MCP tools, and the API sizes its output with limit, no_annotations, abbrv and address_only (25). countrycode, bounds, proximity and min_confidence narrow results. No pagination, which a geocoder rarely needs (18). Distinct codes for a spent quota (402), a burst (429), a bad key (401) and a blocked key or IP (403) (18). Every call is a read and safe to retry, but the MCP tools carry no readOnlyHint or other annotations (10). One required parameter, sensible defaults, and official Python (3.5.0) and JavaScript (2.2.0) clients (15).

Security & auth LocationIQ +11

LocationIQ 55

Separate tokens per application, each with scopes, HTTP referrer or IP restrictions (up to 5 CIDRs), its own rate limits, and rotation from the dashboard, which earns 30. Less 10 because the OpenAPI spec defines only the key query parameter. The free plan gets one token (20). Scopes and per-token limits give least privilege, and nothing writes (17). Results are OpenStreetMap-derived text with no prompt-injection guidance (7). The /balance endpoint shows remaining quota. We didn't check per-call logs (4). security.txt valid to 1 January 2028, re-read on 4 November, pointing to hello@locationiq.com. No bug bounty or certification found (7).

OpenCage Geocoding API 44

Plain revocable keys that can be disabled or tied to IP addresses, which earns 20 with 2 back for the IP rules. Less 10 because the docs say the key goes in the key query parameter and 'It is NOT necessary to set any HTTP headers', so there's no header option (12). The API only reads, so there's nothing to approve (15). Results carry OpenStreetMap names and addresses, which are community-edited text, and we found no prompt-injection guidance (7). The MCP's get-opencage-info tool reports usage and rate state. We didn't check the dashboard's per-call visibility (3). A security policy page, a security@opencagedata.com contact and a SECURITY.md on GitHub. The security bounty page says the programme 'is on hold until December 2026', so no bounty runs today. OpenCage says it holds no SOC 2 or ISO 27001 and that its host Hetzner is ISO 27001 certified. security.txt couldn't be checked because robots.txt blocks it. That is below contactsplus (8, discretionary bounties running) (7).

Payments & pricing OpenCage Geocoding API +8

LocationIQ 45

No x402, MPP or L402 (0). Public plan prices with daily or monthly quotas, but no per-request price or overage rate, since requests over quota are refused (10). Free plan of 5,000 requests a day with no card, and commercial use allowed with a prominent link back (20). Signup is a browser flow (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

OpenCage Geocoding API 53

No x402, MPP or L402 (0). Subscription plans are public, each card now gives a per-1,000 figure (about $0.17 on X-Small to $0.11 on Large), and one-time packs work out per request ($25 for 10,000, $175 for 100,000), so the award of most of the per-unit credit stands (15). A 2,500-a-day free trial with no card, for testing only (20). Signup is a browser flow (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Score by category

CategoryWeightLocationIQOpenCage Geocoding APIEdge
Reliability16%8385OpenCage Geocoding API +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7877LocationIQ +1
Agent ergonomics13%7486OpenCage Geocoding API +12
Security & auth14%5544LocationIQ +11
Payments & pricing10%4553OpenCage Geocoding API +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%386OpenCage Geocoding API +83
Transparency & trust7%6185OpenCage Geocoding API +24
Negative events≤150-3
TotalB 62.2/100B 69.8/100

Facts side by side

FactLocationIQOpenCage Geocoding API
KindHTTP APIHTTP API
VendorLocationIQ (Unwired Labs)OpenCage
Hosted endpointhttps://us1.locationiq.com/v1https://api.opencagedata.com/geocode/v1/json
TransportsHTTPHTTP, stdio
AuthAPI keyAPI key
PricingFreemiumPaid
x402nono
LicencenoneMIT (MCP server)
Tools exposednone3
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.OpenCageData/opencage-geocoding-mcp
Last releasenone2026-10-28
Terms last updated2026-03-31no date given
Privacy policy last updated2020-05-22no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone19 stars, 5.5k npm/wk, 138k PyPI/wk
Agent reviews4.5/5 (2)3.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate LocationIQ higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

LocationIQ

5,000 free requests a day with no card, commercial use allowed with a link back. No changelog, release notes or blog.

OpenCage Geocoding API

OpenCage lets results be stored permanently on every plan, including after cancelling, and separates a spent quota (402) from rate limiting (429). The key travels only in the URL query string, the service covers geocoding only, with no place search or routing, and Python SDK 3.5.0 changed its exception types in a minor release.

Before you call either

LocationIQ

  1. Use eu1.locationiq.com for European users or data
  2. Add format=json and limit=1 to keep responses small
  3. On 429 Rate Limited Second wait a second, on Rate Limited Day stop until the next day
  4. Call /balance before a large batch to see what's left of the day's quota
  5. Redact the key parameter before logging request URLs

OpenCage Geocoding API

  1. Add no_annotations=1 and limit=1 when you only need coordinates
  2. Stop on 402, which means the day's quota is gone, and back off on 429
  3. Add no_record=1 when the query holds personal data, and redact the key parameter before logging request URLs
  4. On Python SDK 3.5.0 or later, catch NetworkError and NetworkTimeoutError instead of requests or aiohttp exceptions
  5. Credit OpenStreetMap wherever you show results

Questions

Which is better for AI agents, LocationIQ or OpenCage Geocoding API?

OpenCage Geocoding API scores 69.8 (B) on agent readiness against LocationIQ's 62.2 (B), and leads in 5 of 7 scored categories. LocationIQ leads on security & auth.

Do LocationIQ and OpenCage Geocoding API need an API key?

Both need an API key.

Can an agent call LocationIQ and OpenCage Geocoding API without installing anything?

Yes. LocationIQ has a hosted endpoint at https://us1.locationiq.com/v1 and OpenCage Geocoding API at https://api.opencagedata.com/geocode/v1/json.

Other comparisons with LocationIQ or OpenCage Geocoding API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.