HERE’s Geocoding & Search API v7 is enterprise mapping infrastructure — global coverage, routing, geocoding, and places in one platform. Loop is built specifically for AI agents: MCP protocol, freshness signals per record, and a report() tool that lets agents improve the data they consume. The use cases overlap on “find a place” but diverge on everything else.
Note: The original HERE Places (Search) API is in legacy/maintenance status. This comparison covers the current recommended HERE Geocoding & Search API v7 (GS7).
| Dimension | Loop | HERE GS7 |
|---|---|---|
| Primary protocol | ✓MCP (streamable HTTP) + REST | REST only |
| Agent integration | ✓Paste one URL — zero code | Write a REST client or custom MCP wrapper |
| Free tier | ✓30 reads/min + 10 reports/min — no account or key required | Requires account + API key on every tier; free allowance varies — see here.com/get-started/pricing |
| Coverage | Restaurants, Kreuzberg Berlin | ✓Global — cities, transit, POIs, routing |
| Availability labeling | ✓availability.inferred: true on every record until verified | isOpen derived from stored openingHours schedule; no inferred label or confidence score |
| Freshness signals | ✓observed_at timestamp + confidence score (0–1) per record | No documented freshness or confidence fields in the response schema |
| Agent feedback loop | ✓report() mutates record confidence in real time | No feedback mechanism |
| Out-of-coverage handling | ✓Explicit error with suggested_action enum | No declared coverage boundary |
| Response format | Vertical-typed JSON with restaurant sub-object | Generic place schema with categories and openingHours |
| Data licensing | ✓ODbL (OSM) + Apache 2.0 (FSQ OS Places) | Proprietary commercial license (HERE content) |
| Routing & geocoding | Not included | ✓Full routing, geocoding, and isoline APIs |
The HERE Geocoding & Search API v7 is a REST-only service providing global place and geocoding data — built for enterprise mapping products. Loop is built specifically for AI agents: it exposes local business data via MCP (Model Context Protocol) so agents connect with one URL, adds per-record freshness signals (observed_at, confidence), and includes a report() tool that lets agents improve the data they consume. There is also no HERE MCP server, so connecting HERE to an MCP client requires custom code.
No. The HERE Geocoding & Search API is REST-only. Connecting it to an MCP client requires writing a custom wrapper server. Loop exposes native MCP at https://stayinloop.dev/mcp — paste one URL into Claude, Cursor, or Windsurf and all four Loop tools are immediately available.
If your agent needs MCP protocol, freshness transparency, or a feedback loop that improves data with every call — use Loop. If you need global coverage beyond Kreuzberg Berlin, routing and geocoding alongside place data, or enterprise-grade mapping infrastructure — use HERE.
Loop offers a free tier with 30 read calls/min (search, get_details, verify) and 10 report calls/min — no account or API key required during the open wave. HERE requires an account and API key on every tier; the free request allowance varies by plan. See here.com/get-started/pricing for current HERE pricing details.
The original HERE Places (Search) API is in legacy/maintenance status and uses the deprecated OAuth 1.0 authentication scheme. HERE's current recommended replacement is the Geocoding & Search API v7 (GS7), which consolidates places, geocoding, and search. For new integrations, HERE recommends GS7.
Paste https://stayinloop.dev/mcp into Claude, Cursor, or Windsurf. No key, no approval, 30 reads/min free.