FR
All alternatives

unmap as an alternative to TomTom

When unmap fits a Canadian map, search or route better than TomTom, when TomTom is the better choice, and how the two bills count what you use.

The unmap API for each need

What you needunmapTomTom
MapsMaps APIMap Display API
GeocodingGeocoding APIGeocoding API and Reverse Geocoding API
Place searchPlacesPlaces Search API
RoutingRouting API · RouteRouting API
Travel-time areasRouting API · IsochroneReachable Range API
Distance matrixRouting API · MatrixMatrix Routing v2 API
Map matchingRouting API · MatchSnap to Roads API
Route optimizationOptimize APIWaypoint Optimization API

Published prices

The first paid tier from the provider's public pricing page, as read on the date shown. Prices change: check the source before you decide.

What you needPrice after the free allowanceFree allowanceCheckedSource
Maps$0.10 per 1,000 vector tile requests (200,001 to 10,000,000)200,000 tile requests2026-11-06TomTom
Geocoding$1.00 per 1,000 geocoding requests (20,001 to 1,000,000)20,000 requests2026-11-06TomTom
Place search$1.00 per 1,000 Places Search Suggest requests (10,001 to 1,000,000)10,000 requests2026-11-06TomTom
Routing$1.00 per 1,000 Routing API requests (20,001 to 1,000,000)20,000 requests2026-11-06TomTom
Travel-time areas$1.50 per 1,000 Reachable Range requests (2,501 to 100,000)2,500 requests2026-11-06TomTom
Distance matrix$3.00 per 1,000 Matrix Routing transactions (2,501 to 100,000)2,500 transactions2026-11-06TomTom
Route optimization$4.00 per 1,000 Waypoint Optimization requests (deprecated; shuts down 2027-05-31)2,500 requests2026-11-06TomTom

When unmap is the better fit

  • You want to keep what you fetch. Our terms let you cache maps and geocoding results permissively, and what you have cached stays yours to keep and serve after you cancel.
  • Your users search in Canada, in either official language. One record carries its English and French names, plus Indigenous-language names where the source data has them, and a query typed in Inuktitut syllabics finds the place. See Languages.
  • You plan deliveries, not just a stop order. TomTom's Waypoint Optimization API reorders up to 12 waypoints with no fleet planning, is deprecated, and shuts down on 2027-05-31 with no recommended migration path. Optimize plans shipments across vehicles with time windows, loads and driver breaks, and /optimized-route reorders up to 10 stops (Routing API). Road travel times cover Canada only.
  • You route transit riders in Canada. mode=transit routes and draws travel-time areas on scheduled Canadian transit (Transit routing). TomTom's product list has no transit routing.
  • You search by legal land description. With the Legal Land add-on, a Dominion Land Survey or NTS description such as NW-25-24-1-W5 is an ordinary search query (Legal land).

When TomTom is the better fit

  • Your drive times need live traffic. The Traffic API serves real-time flow and incidents as tiles and as segment detail, with coverage in 73 markets, and TomTom's pricing page describes its Routing API as traffic-aware. unmap drive times have no live or predicted traffic, and its road events are provincial closures and incidents, not traffic speeds.
  • You search or route outside Canada. unmap's basemap is worldwide, but search and routing cover Canada only, and a route that leaves the country is a 422 (Coverage).
  • You ship turn-by-turn navigation in a native app. The Maps and Navigation SDK for Android and iOS gives voice and visual guidance and falls back to onboard maps offline. Commercial use goes through TomTom sales. unmap ships a web SDK and no native mobile SDK.
  • You route electric vehicles. The Long Distance EV Routing API plans charging stops along a route. unmap has no EV routing.

How the bill compares

The table above is TomTom's first paid tier for each API, each with its own free allowance, as read on the date shown. Later tiers cost less per 1,000.

unmap has one meter instead. Every request is one call, tiles included, and every API draws from the same pool. Three bulk paths count work, not requests: batch geocoding is one call per non-blank query, a hosted batch job is one call per eligible row, and Optimize is one call per shipment a successful solve performs. The dev plan is free and for building, not production. Browser calls from localhost are not counted, except Optimize, which counts from every origin. Server-side calls and Optimize draw on 10,000 included calls a month. Indie is US$19 a month for 250,000 calls, then US$1.00 per 1,000. Growth is US$99 a month for 2,000,000 calls, then US$0.75 per 1,000. Plans and limits has the detail.

TomTom bills each API on its own meter, with its own free allowance. The allowances have no time limit and need no credit card, and TomTom's pricing page states no commercial-use restriction on them. Once one is used, requests are blocked unless you have added prepaid credit. unmap's dev plan cannot serve a live domain at all.

For maps the units line up, because both sides count tiles. On unmap a map's first paint is about 40 calls, almost all of them tiles. TomTom's vector tiles cost less per 1,000 than unmap's overage: a million tile requests a month is $80 at TomTom's first tier, and on unmap that million fits inside Growth with a million calls left for search and routing. Which is cheaper depends on what else you call.

Search and routing are one request on both sides, but each TomTom API draws on a separate allowance and rate, while on unmap a geocode, a reverse geocode, a route and a travel-time area all come from the same pool. A matrix is where they part: TomTom bills a 10 by 10 Matrix Routing request as 50 transactions, and a 10 by 10 /matrix request on unmap is one call. If you use Waypoint Optimization, budget for a move before it shuts down on 2027-05-31.

To estimate your own bill, start from about 40 calls for a first paint on an empty browser cache. Panning and zooming add tiles, and return visits fetch fewer. Then add your searches and routes and set the total against a plan's included calls.

Read the quickstartGet a key