Geocoding API for Europe

The European geocoding API, GDPR by design

Geocode, reverse geocode, autocomplete and repair addresses on official address registers. Processed in the EU only, no address written to our logs, and you may keep every result.

Join the early access Read the docs

30,000 free requests a month
Permanent storage of results
Google-compatible endpoint

Request

curl https://api.addrova.eu/v1/geocode \
  -H "X-API-Key: $ADDROVA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"q": "4 place d'\''Armes, Belfort"}'

Response (shortened)

{
  "results": [{
    "label": "4 Place d'Armes 90000 Belfort",
    "location": { "lat": 47.64, "lon": 6.86 },
    "precision": "rooftop",
    "confidence": 0.97,
    "confidence_level": "high",
    "sources": ["ban"]
  }],
  "attribution": [{ "source": "ban" }]
}

Example from the quickstart. Addrova is in pre-launch: the base URL is not live yet.

Where the big geocoding APIs stop you

What the published terms and prices say, read on 2026-10-18. Sources are in the comparison below.

With Google, Esri or Mapbox

Storing results is restricted or paidGoogle lets you cache coordinates for a limited time only (30 days in the terms we read). Mapbox charges for permanent storage and Esri bills storage in credits.
Your data may leave the EUThese providers are US companies. Check where your requests are processed and which transfer rules apply before you send customer addresses.
The price climbs with volumeAbout $450 for 100,000 Google requests a month on the published grid; Mapbox permanent mode is about $500.

With Addrova

Keep every resultStore coordinates in your own database for as long as you need, with attribution of the sources.
EU-only processingRequests are processed in the European Union only. The list of sub-processors is published for review.
No address in our logsBy default no address is written to our logs, and your requests are never reused. Each commitment is tied to an automated test.
A flat, predictable priceFree up to 30,000 requests a month, then €49 for 100,000 and €199 for 1 million, excluding VAT.

Prices and terms change: verify them at the source. Addrova is in pre-launch. Prices shown are the planned launch prices. Nothing can be bought yet.

One API for everything you geocode in Europe

The same request and response model for every country, with the source and licence stated in each answer.

Forward geocoding

Turn a free-text or structured address into coordinates, with a precision level and a confidence you can threshold.

Quickstart

Reverse geocoding

Find the nearest address to a point, with the distance in metres.

API reference

Autocomplete

Suggest addresses as people type, focused on the area they are in.

API reference

Address repair

Fix typos, abbreviations and missing parts and get a corrected address with a confidence. Billed only when an address is repaired.

API reference

Batch files

Geocode CSV or JSON Lines files asynchronously, with idempotent retries and webhooks. Try it online on up to 1,000 rows.

CSV geocoder

Google and Nominatim compatible

Change the base URL and keep your client: compatible endpoints for both.

Migrate in one line

SDKs and MCP server

Python and TypeScript clients with typed errors and retries, and an MCP server for AI assistants.

SDK documentation

Confidence you can use

A calibrated confidence and a precision level on every result, so you decide what to trust.

Read the guide

Measured, and published as it is

France, a second frozen test set, a single pass, 2026-10-20. Verdict GO, outside any comparison with Google.

56 %fewer errors than the BAN aloneOn 610 noisy addresses: 24 errors against 55. Interval 33 to 73 %.
0.22 %confident false positives2 out of 905 accepted answers.
23 msp95 latencyMeasured locally, one request at a time.
0.005calibration error (ECE)The limit set beforehand was 0.05.

The truth is the BAN’s own point, which favours engines built on the BAN. One country only. No comparison with a commercial provider has been run, so we do not claim Addrova is better than any other service.

Read the method and the limits

How the published terms compare

Terms and prices read on public pages on 2026-10-18. Verify them at the source before you decide.

Provider	Free tier	100,000 requests a month	Storing results	Data
Google Geocoding	10,000 a month	About $450	Not beyond a limited cache (30 days for coordinates in the terms we read)	Google proprietary data; US company
Esri ArcGIS	20,000 a month, not stored (developer plan)	Stored: about 40 credits per 1,000; credit price not verified	Paid, in credits	Not verified
Mapbox	100,000 temporary requests a month	Permanent mode about $500	Temporary mode forbids caching; permanent mode is paid	Proprietary data and OSM; US infrastructure
OpenCage	Trial: 2,500 a day, for testing	€45 (X-Small plan)	Permanent on every plan, even after cancelling	Open data such as OSM; Berlin-based company
Addrova	30,000 a month	€49 a month (Starter)	Permanent, with attribution of the sources	Official open address registers; EU-only processing

Source: our competitor study and the providers’ public pricing pages, read on 2026-10-18. Accuracy is not compared here: see the benchmark. Prices as published, excluding taxes. Prices shown are the planned launch prices. Nothing can be bought yet.

Compare in detail

Simple pricing, results you can keep

Prices in euros, excluding VAT. Prices shown are the planned launch prices. Nothing can be bought yet.

Free

€0 per month

30,000 requests a month
Permanent storage of results allowed
Attribution required
Community support

Starter

€49 per month

100,000 requests a month
Higher rate limit
Email support
Adjustable spending cap

Pro

€199 per month

1 million requests a month
Highest rate limit
Availability target in the contract
Priority support

Enterprise

Custom per year

Dedicated EU instance or private deployment
Contractual SLA and DPA
Volume discounts
Contact us to discuss

Address repair is billed in addition to the plan, on success only: you pay for an address only when it is repaired and returned with a confidence score.

See the full pricing

GDPR by design, with proof

Each privacy claim is numbered and tied to an automated test in our code.

Zero addresses in our logs

By default no address, requested coordinate or API key appears in our logs (ZL-10), and third-party library logs are neutralised (ZL-11).

Processed in the EU

Requests are processed in the European Union only. This site loads no third-party script, font or analytics.

No reuse of your requests

Your requests are not reused for training or any other purpose.

DPA and sub-processors

A data processing agreement (a draft under legal review) and the list of EU sub-processors are published for review.

Questions

Can I store geocoding results permanently?

Yes. Results can be stored and reused for as long as you need, including after you stop using Addrova. Source attribution still applies.

Where are my requests processed?

Only in the European Union, on EU-based infrastructure. The list of sub-processors will be published on the compliance page before launch.

Do you keep the addresses I send?

By default, no address is written to our logs and your requests are not reused for any other purpose. See the compliance page for the exact commitments.

Is it available today?

Addrova is in pre-launch. The documentation and pricing here describe the planned service.

Guides

Geocode Europe on data you can keep

Join the early access and be among the first to send a request when the service opens. No payment is asked.

Join the early access Read the docs