Build with the APIs
Tiles, styles, geocoding, routing and truck compliance behind one key, issued card-free. Your agents can find it, price it and use it without a human in the loop.
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 ways in. One signed data layer.
Run it on your infrastructure
The same stack on your own servers, and fully offline on your own devices. Signed territory packages, no call home, and a licence rather than a meter.
Commission a survey or a viewer
We drive the streets you name and hand back a positioned inventory with the photograph behind every value, or stand your own survey up as a viewer on your domain.
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.
ADR tunnel enforcement requires the MapMap Valhalla image, which the self-host distro does not yet ship by default.
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
Evidence
What we have built, and what was measured on it.
One roadside pass, measured
2,008 frames and 4,146 positioned features from a single day in Brighton, with legible-value precision of 98.0% on a seeded sample of 250.
An EV charging app, in under a day
909 UK charging sites on a branded basemap, with live routing and a reachable-range ring, built by our agents against the hosted gateway.
A low-bridge app, in under a day
Four thousand seeded bridge records, in-app capture with evidence hashing, and a truck profile refusing a bridge the car profile passes under.
All three are internal reference builds: we built them ourselves to prove a capability, and none of them is a customer deployment. Each card on /evidence carries what its figure does not establish.
