One set of plans. Every rate published.
Start free, subscribe once your volume settles, self-host when data control demands it. Machine-readable at /pricing.json.
Email-verified, no card, commercial use allowed. Overage on prepaid credit at the pay-as-you-go rates.
Get an API keyFor a first integration in production: five times the free tier, cancel any time.
For fleets and products with steady routing volume across the month.
For heavy integrations: ten million included calls at the sharpest per-call rate.
Every plan includes the full API surface. Beyond included calls, usage falls back to pay-as-you-go pricing, never a surprise invoice. See how billing works. Subscriptions bill via Stripe, apply to every verified key on your email within a minute of payment, and cancel any time (quota returns to free at the period end).
Not sure which plan? Estimate your monthly cost with the calculator below.
What happens when you run out
- On-device. Offline guidance and territories you already hold keep working. Nothing is revoked.
- Hosted API calls. When included volume and prepaid credit are both spent, calls stop: the gateway answers HTTP 429 with the quota, the reset time and an upgrade link in the body, and an offline territory download over its allowance answers HTTP 402. No balance accrues, so you can never owe us money. Top up or subscribe and the next call succeeds.
- Fleet SDK monthly active users. MAU billing never blocks a request. An uncovered MAU debit marks the account overdrawn for the month and we keep serving; you settle it afterwards rather than your end users losing the app.
Everything else
Routing trucks or hazmat? Switch to Truck and ADR.
A call is one route, geocode or lookup. Matrix, isochrone and optimisation requests bill by size, see below.
| Class | Free / month | Up to 1M | 1M–10M | 10M+ |
|---|---|---|---|---|
| Standard routing and data | 50,000 | 0.05p | 0.03p | 0.02p |
| Premium truck and ADR | 2,500 | 1p | 0.7p | 0.4p |
Two-speed, marginal pricing: the free allowance comes first, then each band applies only to the calls that fall within it. Standard covers car, van, bike and pedestrian routing, geocoding, matrix, isochrone, map matching and route optimisation; Premium covers truck routing, ADR compliance and truck-constrained optimisation, detected automatically per request. A matrix bills one call per started block of 25 elements (10,000 max), an isochrone one call per contour (10 max), and an optimisation 10 calls per 2,500-pair block of its internal matrix: 10 calls up to 50 locations, 40 at 100, and 160 at the 200-location cap. Plans bundle larger allowances at a lower effective rate; above 25 million calls a month, talk to sales.
Built for agents: issue a key in one call, top up prepaid credit and go. A provisional key gives 1,000 calls over 72 hours with no card needed, before your email is verified.
Track usage and balance at /account. Every metered 402 also accepts x402 machine payment on mainnet. The mechanics are spelled out in the FAQs.
| Feature, or fleet size | Core | Plus |
|---|---|---|
| Offline navigation | ✓ | ✓ |
| ADR restrictions enforced offline | ✓ | ✓ |
| Territory updates | 1 region | Additional regions |
| Priority support | – | ✓ |
| CarPlay and Android Auto, beta (source, not yet a published artefact) | ✓ | ✓ |
| Price, per vehicle per month, billed annually. Your whole fleet pays the rate of the band it falls in, counted on contracted fleet size and trued up at each anniversary | ||
| Up to 500 devices | £3 | £5 |
| 501–2,500 devices | £2.40 | £4 |
| 2,501–10,000 devices | £1.80 | £3 |
| 10,001+ devices | £1.20 | £2.20 |
CarPlay and Android Auto are included in both bands: templates, trip state and car-screen map rendering. They are beta and source-distribution today, not yet a published artefact, and public artefacts land with the sdk-v0.7.0 release after hardware validation; your app also needs its own platform entitlement and store review (see the car integration guide). Per-vehicle licensing is invoiced, not self-serve: we agree the band and regions with you, then bill annually. The free tier’s 8 GiB/month download allowance covers a one-region proof of concept.
Building an app, not running a fleet?
Meter the SDK per monthly active user instead of per vehicle: 1,000 MAU free every month, then 30p per additional active user from prepaid credit. Monthly plans include 5,000 to 100,000 MAU. MAU billing never cuts an end user off: if credit runs out we keep serving and flag the account instead. Hosted API calls are the other meter and they do stop; see the two meters above.
You license the platform, subscribe to fresh territory data, and choose the support that fits. Unlike the comparable vendors in the table below, the prices are published: “from” anchors, scoped precisely in a proposal.
The ladder starts at Team Lite: tiles, styles, static maps and geocoding on your own infrastructure for one internal application. It runs no routing engine, so a deployment that needs routes is a Team deployment. Moving up is an upgrade rather than a re-purchase, credited pro rata against the remainder of the term.
Platform licence
An annual commercial licence to run the full stack on your own hardware, tiered by fleet size.
Territory data subscription
Signed, QA'd, restriction-audited territory packages with ongoing over-the-air updates. One region's signed channel, with quarterly updates, is included in every tier. Territories beyond your tier's coverage are scoped on the call.
Support and SLA
Security-patch SLAs, priority support and source escrow, matched to how critical routing is to your operation. Published in full, with the 99.5% monthly availability commitment that covers the hosted API on Scale and above and on a self-host licence whose order form includes a hosted API entitlement, at /sla.
Professional services
Custom territory builds, bespoke restriction overlays, fixed-price point cloud bakes and hands-on integration support from the engineering team. Scoped and quoted per engagement, not sold as a subscription.
Team Lite
from £2,500/year
Tiles, styles, static maps and geocoding on your own box. No routing engine.
- 1 region of territory data, quarterly updates
- 500 MAU included, one internal application
- Community support, no response target
- Upgrade to Team at the pro-rata difference
Team
from £12,000/year
One production deployment for internal apps.
- 1 region of territory data, quarterly updates
- 500 MAU or 100 vehicles included
- Email support (support@mapmap.ai), 2-day response
Business
Popularfrom £36,000/year
Customer-facing apps, truck & ADR costing.
- Continental territory data, quarterly updates
- 5,000 MAU or 1,000 vehicles included
- Priority support, 1-day response
Enterprise
from £96,000/year
HA, multi-deployment, world data, full workspace access.
- World territory data (monthly available)
- 50,000 MAU or 10,000 vehicles included
- Named engineer, 4-hour critical response
Sovereign / OEM
from £180,000/year
Air-gapped, accredited, embedded: your factory runs, your keys.
- Custom & private territories
- Per-unit royalty schedule for embedded fleets
- Dedicated engineer, source escrow option
Annual licences, invoiced, plus a territory data subscription. A paid 60-90-day pilot runs at 10% of year one, fully credited on conversion.
MapMap Roadside is bought as a fixed-price engagement, not a subscription: an inventory pilot at £22,000 (up to 40 km, two asset classes), a town inventory at £62,000 and a large town at £96,000, each with a stated allowance and published overage rates. Every engagement starts with a free demo and a free desk proof; a £2,500 drive proof on your own network is credited in full against any package.
The full rate card, including kerbside restriction surveys and re-survey passes, is at Roadside pricing.
Drawing point clouds is never a metered event: you host the payloads and the package renders them with the same key as the rest of the platform, or with no key at all on a self-hosted deployment. What meters is the basemap underneath, on the standard call pricing above.
Clouds not yet in the wire format are baked as a fixed-price package: a site or corridor bake at £3,600, or £6,000 where the classification is mixed or undocumented or the CRS has to be reconciled first, with nothing recurring after handover. If you would rather we hosted the payloads, every viewer delivery includes 250 GB and storage above that is £3.50 per GB a year. Serving those payloads is not charged separately: we charge for storing the bytes or for serving them, never for both.
If you want the thing working rather than the files, that is a fixed price too: a survey viewer at £18,000 is your own survey stood up as a hosted viewer on your branding and your domain, a city-scale viewer at £48,000 is the same at whole-city scale with everything navigable, and a regional viewer at £95,000 takes two to four authorities as one continuous scene. Programmes covering a wider network, repeat capture or integration into your own systems start at £180,000 and are scoped per network, with an annual platform fee of £60,000 to £120,000 by network size. Drawing the points is still never metered and there is no per-seat viewer licence. The detail is on the point clouds page.
Overhead clearance read from survey geometry, in the viewer and on the API. Three fixed prices. A clearance audit at £6,500 compares the survey you already hold against the OSM height tags for the same network: what carries no tag at all, what disagrees with your survey, and by how much. A clearance corridor at £14,000 publishes measured clearance live in the viewer and on the API for one corridor or a small network. A clearance network at £24,000 does the same across a network, covering 150 centreline km, then £90 per centreline km beyond it.
Prices are published and fixed up to £24,000, because a published number is what lets you check a price against your own authority and buy without opening a conversation. Larger networks are scoped per network and quoted as a fixed price after scoping, rather than asked to contact us for a rate.
A measured clearance is a within-survey figure reported with its uncertainty bound and the coverage it rests on. It is not a signed, legal or certified height, it is not a structural assessment, and it does not replace a bridge owner’s own records. Ground the survey did not cover is reported as not surveyed, never as clear. On the API, a clearance query is five standard calls. The audit is delivered as a report and a per-structure table; an API endpoint for it is planned, not yet available.
How we compare to Google, Mapbox, HERE
Car routing per 1,000 calls at each vendor’s entry paid rate, and what truck/ADR routing actually takes to buy. We are not the cheapest generic router: we sell truck and ADR compliance as a self-serve product with a published price, which the vendors below do not.
| Provider | Car routing / 1k | Truck + ADR | Free tier | Self-host | Price transparency |
|---|---|---|---|---|---|
| MapMap | £0.50 | £10, published, self-serve; ADR compliance check included | 50,000 calls/mo, commercial use | Yes, self-serve, every tier | Published to 25M calls/mo |
| Google Routes | ~$5-10 | No truck routing | 10,000 calls/mo | Prohibited by ToS (no offline, no caching) | Published |
| Mapbox | $2.00 | Dimension params only, no ADR; in-vehicle use needs a sales-negotiated licence | 100,000 calls/mo | Enterprise Atlas, sales only | Published to 5M |
| HERE | ~$0.88 | ~$2.92, tunnel-category params; quote-only above 1M/mo | 30,000 std / 5,000 truck per mo | Enterprise sales only | “Indicative” only; quote above 1M |
| Azure Maps (Gen2) | $4.50 | Truck params in routing | ~1,000-5,000 calls/mo | No | Published |
| Indie cohort (Stadia, GraphHopper, Geoapify) | ~$0.20-0.60 | Dimension/hazmat params on paid plans; no ADR compliance product | Non-commercial only (Stadia, GraphHopper) or ~90k (Geoapify) | OSS DIY or enterprise | Published |
Competitor figures are list prices from public pricing pages as of July 2026 (Google Routes Essentials/Pro; Mapbox Directions first paid band; HERE Base Plan calculator; Azure Maps Gen2; Stadia/GraphHopper/Geoapify entry paid plans), converted where needed and rounded; check each vendor for current numbers, and check ours at /pricing.json, which is the billed truth. HERE’s page states its prices are “indicative estimates only”; ours are the rates the ledger charges.
Every metered request also speaks x402 machine payment: the gateway’s 402 response quotes the exact price and accepts inline settlement: on-chain in USDC on Base and Solana on the hosted gateway since 20 July 2026, prepaid credit everywhere, and on-chain via configuration for self-host.
Frequently asked questions
What counts as a call?
One route, geocode or lookup is one call. Matrix, isochrone and optimisation requests bill by size, not as one call each: a matrix bills one call per started block of 25 elements (10,000 max), an isochrone one call per contour (10 max), and an optimisation 10 calls per 2,500-pair block of its internal matrix, which is 10 calls up to 50 locations, 40 at 100 and 160 at the 200-location fair-use cap.
What does a search box cost?
The typed part is free at ordinary volumes. The first 5,000 GET /geocode/suggest requests a day are not billed, counted across every key on your account rather than per key, and every suggest beyond that bills one standard call. The pick is always billed: GET /geocode/retrieve and the single-shot GET /geocode are one standard call each. The allowance is for suggest alone and resets at midnight UTC, so unused suggest calls never become routing calls.
What happens when I go past my included calls?
Usage meters against prepaid credit at the two-speed pay-as-you-go rate: 0.05p per standard call, 1p per Premium truck and ADR call. Fractional pence are billed exactly (the ledger meters in millipence). A busy month degrades to metered pricing, never a surprise invoice.
Do Premium calls use my free tier faster?
Yes. Included volume is denominated in standard calls and a Premium call draws 20 of them, matching the price ratio, so an all-Premium free tier is 2,500 calls rather than 50,000.
Do unused calls roll over?
No. Included calls reset at the start of each UTC calendar month and unused calls do not carry over, so the counter resets on the 1st regardless of your billing date.
How do keys and verification work?
Keys start provisional: 1,000 calls over 72 hours, no card. Verifying your email upgrades the key to 50,000 included calls a month. A monthly plan raises the included volume on every verified key of your email, applied idempotently each billing period.
Can I cancel a plan?
Yes, any time. Subscriptions bill via Stripe, apply to every verified key on your email within a minute of payment, and your quota returns to the free tier at the period end.
Can an agent pay without a human?
Yes. Every metered 402 response follows the x402 open payment standard, quoting the exact price of the request. On-chain x402 payment has been live on the hosted gateway since 20 July 2026, in USDC on Base and Solana. Prepaid credit works on every deployment, and self-host operators turn on-chain settlement on in their own configuration.
Who processes payment?
Stripe handles cards and subscriptions. Quota and credit land on the key via the gateway's admin API.
Start with 50,000 free calls.
Card-free, commercial use allowed, every rate on this page published. We are also taking on a small number of founding fleets, for direct engineering access and preferential pricing in exchange for real routes and audits that sharpen the roadmap.