Every number on this site is HERE Technologies' published rate divided by two. Same free allowances, same response shapes, no sales call to find out what a million requests would cost you.
curl -sG "https://api.apinavi.com/v1/geocode" \
-H "Authorization: Bearer $APINAVI_KEY" \
-d "q=Torstraße 66, Berlin" \
-d "in=countryCode:DEU"Free allowances are identical to HERE's — the discount is on price, not on limits. Volume steps are theirs too, halved step for step.
HERE list prices quoted from public sources and dated on the pricing page. HERE raised its Base Plan and pay-per-transaction prices by about 6% on 1 April 2026; this card already reflects that.
Run a call in the sandbox on this page, take the snippet, add a key. Billing starts after the free tier, and the rate you pay is on the pricing page before you sign anything.
Committed volume, invoiced billing, a signed DPA and an SLA with credits. The same published rate card applies — the commitment buys terms and support, not a different price list.
HERE splits the same capability across Base Plan, Location Services, the platform and half a dozen product brands. Here it is one catalogue with one bill.
Addresses to coordinates, coordinates to addresses, at 0.44 per thousand.
Learn more$0.75per 1 000Car, truck, bike and foot — with live traffic and truck restrictions.
Learn more$0.25per 1 000Vector and raster basemaps you can restyle, plus static images.
Learn more$1.25per 1 000Live flow and incidents, refreshed every 60 seconds.
Learn more$1.00per 1 000Typeahead that completes an address in three keystrokes.
Learn more$17.49per optimisationTolls, map-matching, geofences and tour planning for vehicles that move all day.
Learn moreFour things HERE makes you ask for. None of them are a secret worth keeping.
HERE's pricing page is a sign-up wall: to learn a per-request rate you register or you contact sales. Every rate here is on the pricing page, per service, per volume step.
The discount is a published rule — half of HERE's list, tracked as it changes. When they raise prices, ours move with them and stay at half. When they cut, so do we.
Latency per region, uptime, every API change dated in a changelog, and a deprecation policy with a 12-month floor. Operational facts belong on the marketing site.
Field-compatible responses and a parameter map for HERE, Google and Mapbox. Migration guides work in both directions — including away from us.
Free allowances are applied first, then the volume ladder, marginally. The HERE column uses their published list price for the same call volume.
Open the full calculatorResponses carry the same field names and nesting as HERE's, so most integrations move by swapping a base URL and a key. Where a parameter differs, the mapping table says so.
// the whole migration, for most integrations
- https://geocode.search.hereapi.com/v1/geocode?apiKey=…
+ https://api.apinavi.com/v1/geocode
+ Authorization: Bearer $APINAVI_KEY
// response fields keep their names and nesting
items[0].address.label
items[0].position.lat
items[0].scoring.queryScoreLatency is measured at the edge of each region against the geocoding endpoint. Modelled targets are labelled as such until a region reaches general availability.
| Region | p50 | p95 | Uptime |
|---|---|---|---|
| Frankfurteu-central | 24 ms | 61 ms | 99.98% |
| Amsterdameu-west | 21 ms | 55 ms | 99.99% |
| Ashburnus-east | 28 ms | 70 ms | 99.97% |
| San Joseus-west | 31 ms | 74 ms | 99.98% |
| Mumbaiap-south | 38 ms | 92 ms | 99.95% |
| Tokyoap-northeast | 34 ms | 81 ms | 99.97% |
Every endpoint ships a JSON Schema tool definition, the docs are served as plain text at /llms.txt, and there is a hosted MCP server. An agent can plan a route without a human writing glue code first.
mcp.apinavi.com — endpoints exposed as typed tools with the same auth.
The whole reference as clean text, no navigation chrome, no JavaScript.
JSON Schema per endpoint, generated from the same spec as the SDKs.
Formats you already use
Two structural reasons. The map data comes from open sources plus commercial feeds we license per region rather than owning end to end, and there is no field sales organisation — the rate card does the selling. The trade-off is honest: we do not sell embedded automotive-grade HD maps, and the deepest coverage tiers stay HERE's.
No. Free allowances match theirs service by service: 30 000 geocoding, 30 000 map tiles, 5 000 routing, 2 500 matrix, 500 tour optimisations. The 50% applies to the paid rates.
The rate card is derived from theirs by a single constant, and the page states the date it was last reconciled. Their April 2026 increase of about 6% is already reflected. If they cut a rate, ours drops to half of the new one.
Response field names, nesting and error shapes follow HERE's documented payloads for geocoding, routing, matrix, isolines, traffic and places. Where behaviour differs — mostly around scoring and truck attributes — the migration guide lists the difference instead of glossing over it.
Three things. Coverage of indoor venues and lane-level HD data is narrower. There is no embedded automotive stack for offline head units. And the company is young: the SLA carries credits, but not a decade of references.
That is what the panel above is. It returns documented response shapes from a fixture set, labelled as sandbox data, with no key and no account.
It is the same page a customer on a committed contract sees. If the numbers do not work, nothing else about the product matters.
apinavi.com