Hosted API
Call our routing and compliance API. Metered card-free keys, pay as you go, every profile. No sales call.
Maps, built for agents.
Yours to own.
Tiles, styling, geocoding, routing and turn-by-turn guidance. Hosted, or fully offline on your own servers.
Three surfaces. One signed data layer.
Offline SDK
Turn-by-turn guidance fully offline in your app. On-device routing, ADR enforcement, spoken directions, over-the-air map updates.
Agent-native
Agents find us, price us, get a key and route without a human in the loop. MCP server, llms.txt, machine payments.
If you can’t self-host it, you don’t control it.
The whole stack boots from one Compose file inside your network: gateway, routing engine, geocoder and MCP server. An SBOM ships with every release. If we disappeared tomorrow, your maps would still work.
Self-host guidefirst boot, from the source checkout
$cd distro && docker compose up -d --build
→gateway · routing engine · geocoder · MCP server
Truck routing with ADR dangerous-goods restrictions, enforced in the costing, not post-filtered.
Read how it works© OpenStreetMap contributors © OpenMapTiles
An agent can discover, evaluate and use MapMap unaided.
llms.txt on every deployment, machine-readable pricing, one-call card-free key issuance and an MCP server. Nothing gated behind a sales call.
Read the agents guidean agent, evaluating mapmap.ai
$curl -s mapmap.ai/llms.txt # discover
→endpoints, auth, pricing, mcp
$curl -s mapmap.ai/pricing.json # evaluate
→{ free: "50k calls/mo", payg: "0.05p std · 1p truck" }
$POST /v1/keys # one call, card-free
→snk_… issued · provisional · 1,000 calls / 72 h
$GET /route/v1/truck/…?height=4.0&tunnel_code=D # act
→292 km · restrictions respected · ADR code D
