Get an audit

Head to head · Geocoding · October 2026 research run

HERE Location Services vs Radar

HERE Location Services scores 58 (C) on agent readiness against Radar's 53.3 (D), and leads in 4 of 7 scored categories. Radar leads on reliability and maintenance & community. Both do geocoding.

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

HERE Location ServicesHERE Technologies · HTTP API C58/100#591 of 950 RadarRadar Labs · HTTP API D53.3/100#713 of 950

Which one, for what

HERE Location Services C

Good for Fleet and logistics work that needs truck routing, large matrices, isolines, traffic and transit from one vendor with an SLA.

Ahead on

  • Schema & documentation, 87 against 50
  • Agent ergonomics, 74 against 65
  • Security & auth, 65 against 56
  • Transparency & trust, 63 against 55

Watch for

Platform Terms section f forbids using HERE Materials in connection with a machine learning or AI system, generative AI included. This matters before any probe is run

Radar D

Good for A company that already has a Radar contract, or wants geofencing and trip tracking with geocoding and routing on one key.

Ahead on

  • Reliability, 70 against 57
  • Maintenance & community, 77 against 60

Watch for

The pricing page says Radar has no free tier and every plan is an annual commitment set by quote

Score by category

CategoryWeight this runHERE Location ServicesRadarEdge
Reliability16%205770Radar +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28750HERE Location Services +37
Agent ergonomics13%16.27465HERE Location Services +9
Security & auth14%17.56556HERE Location Services +9
Payments & pricing10%12.51010even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86077Radar +17
Transparency & trust7%8.86355HERE Location Services +8
Negative events≤15-3-2
Total58 · C53.3 · D

Facts side by side

FactHERE Location ServicesRadar
KindHTTP APIHTTP API
VendorHERE TechnologiesRadar Labs
Hosted endpointhttps://geocode.search.hereapi.com/v1https://api.radar.io/v1
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumPaid
x402nono
LicenceProprietary service under the HERE Platform TermsProprietary service under Radar's Terms of Use. The web SDK in radarlabs/radar-sdk-js is Apache-2.0
Tools exposed13none
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-092026-09-14
Terms last updated2023-09-182023-05-24
Privacy policy last updated2024-08-292025-05-13
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes

Verdicts

HERE Location Services

Each endpoint page carries an OpenAPI 3.0 definition as Markdown, and HERE publishes 99.9 per cent monthly availability targets and a six-month deprecation policy. The Platform Terms of September 2023 forbid using HERE Materials in connection with a machine learning or AI system, and the price table could not be read.

Radar

Radar documents 36 REST operations in Markdown with a rate limit on each, and its status feed shows two short API incidents in 90 days. Access is sales-led. The pricing page says there is no free tier, every plan is an annual commitment, and no OpenAPI description or API changelog was found.

Before you call either

HERE Location Services

  1. Send Authorization: Bearer with an OAuth token where logs are kept. The apiKey query parameter puts the secret in every URL
  2. Do not store results for more than 30 days, and follow the HTTP caching headers on each response
  3. Treat 429 and 503 as throttling. HERE says a traffic surge can be throttled for about 10 minutes below the account's quota
  4. Read code, cause and action in the error body, and quote correlationId to support
  5. For Location Reasoning, send initialize, keep the Mcp-Session-Id header on later calls, and send a bearer token on tools/call

Radar

  1. Send the key in the Authorization header with no Bearer prefix, and call https://api.radar.io/v1, not radar.com
  2. Use a publishable key for geocoding, search and routing. Keep the secret key for users, trips, geofences and beacons
  3. Call /v1/search/autocomplete for partial addresses and place names. /v1/geocode/forward is documented as best for complete addresses
  4. Set units=metric on routing calls. The default is imperial, with distances in feet
  5. Treat 429 as one of three things (rate limit, no state change or selective throttling) and 402 as usage exceeded. No Retry-After header is documented
  6. Do not keep geocoding, autocomplete or place results for more than 30 days

Questions

Which is better for AI agents, HERE Location Services or Radar?

HERE Location Services scores 58 (C) on agent readiness against Radar's 53.3 (D), and leads in 4 of 7 scored categories. Radar leads on reliability and maintenance & community.

Do HERE Location Services and Radar need an API key?

HERE Location Services takes an API key or an OAuth sign-in. Radar needs an API key.

Can an agent call HERE Location Services and Radar without installing anything?

Yes. HERE Location Services has a hosted endpoint at https://geocode.search.hereapi.com/v1 and Radar at https://api.radar.io/v1.

Other comparisons with HERE Location Services or Radar

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.

Get an auditSee a sample report