A new roundabout can permanently change how visitors approach a museum. A broken-down vehicle can block the same approach for an afternoon. On the map both may explain a detour, but they are very different pieces of information. TomTom builds the underlying road network and sells services that calculate journeys and describe current conditions. Its use of AI begins upstream, with the work of deciding which observations should change the map.
- 01The foundation TomTom describes combining sensor observations, partner data and open map sources, using machine learning, computer vision and validation in map production.
- 02The services Orbis map display, routing, traffic, places and geocoding have distinct APIs. A product can use several while keeping track of what each one supplied.
- 03A purchasing detail The developer pricing page assigns separate monthly allowances to route calculations, traffic tiles and incident details. A map view is rarely just one request.
01 / ProductWhen a machine observation is strong enough to change a map
TomTom's account of its mapmaking process describes collecting observations from vehicle sensors, imagery, partners and open-data sources including OpenStreetMap and Overture. The company compares sensor-derived observations against historical material and its own mobile-mapping data. Machine learning and computer vision help process the evidence, with checks before changes enter the map. A motorist following a route benefits from that work without necessarily interacting with a generative assistant.
A routing application then has to decide which questions to ask of that map. What roads connect the station with the museum? How long might the trip take on a Tuesday morning? Is an incident currently affecting that corridor? In July 2026 TomTom announced general availability for six Orbis APIs, covering display, routing, traffic, place search and both directions of geocoding. They share a map foundation while answering different requests. Orbis API release and scope
A map's ability to draw a line between two places also says little about whether it has chosen the destination the visitor intended. A large venue may have several entrances. Its street address can point to the nearest public road while the appropriate drop-off is around the corner. For a venue operator the split of responsibilities is concrete. The mapmaker provides a navigable network and routing services. The venue still owns its instructions about which door visitors should use.
02 / AudienceWho should evaluate the Orbis APIs
A travel company operating several attractions may already know its destinations but need reliable ways to get guests there from a station, airport or hotel. It can take ownership of the last few metres while using a mapping platform for the larger route. A developer building a regional visitor app has another interest. It may need a visual explanation of why a normal trip is taking longer and a way to distinguish a current delay from a general forecast.
A company planning deliveries by heavy vehicle has a different shortlist of requirements. Weight, height, road restrictions and service-specific coverage are consequential. The original Orbis general-availability announcement scoped the first release to car routing and distinguished other vehicle modes and batch capabilities. Check the current documentation for the exact mode and geography needed before migrating an existing integration. A supported car journey is a useful prototype for a visitor app and a poor substitute for a commercial vehicle acceptance test.
03 / WorkflowA proposed visitor-trip planner for a museum
Start with the station and the venue's verified visitor entrance. Ask a local employee to record which entrance a taxi should use and where a passenger can actually get out. Keep that information alongside the application’s venue record. Calculate a car route between those locations and examine the last turns as well as the total travel time. This catches a common category of mistake that a plausible arrival time cannot expose.
Use the Orbis Routing API v3 guide to separate journeys starting now from those planned for a future departure. TomTom describes using its routing engine, historical traffic patterns and traffic information to estimate journeys. A forecast for next Tuesday uses a different kind of evidence from an estimate for a visitor leaving the station now. The interface should distinguish those estimates and show when a route was calculated.
Then add a traffic view around the venue. The Orbis Traffic API v2 guide describes vector and raster tiles, as well as an incident details endpoint that returns events within or intersecting a bounding box. A raster tile can display a visual overlay. A vector tile gives the client data to style. Incident details supply a separate way to explain a specific event. An incident inside the displayed rectangle may be on a neighboring street and have no bearing on the calculated route.
For a proposed trial, choose one quiet day, a busy event day and a day with a known road change. Have a local reviewer judge the intended drop-off and whether the displayed explanation belongs to the chosen route. Keep the route calculation, traffic view and staff observation separately labeled. Differences are leads for investigation. The front-desk employee may know a gate is closed for an hour even when the public road itself remains open.
04 / PricingThree counters behind one journey screen
The developer pricing page lists monthly free request allowances individually for relevant endpoints. It distinguishes products available for TomTom Maps, the earlier platform, from those also available for Orbis. Its pricing tables separate traffic tiles from incident details and route requests. Select the products and generation used by the app before entering volume. A number attached to an older segment-data endpoint cannot automatically be used to price a newer traffic overlay.
| Service | Monthly free requests | What causes usage |
|---|---|---|
| Routing API | 20,000 | Calculating journeys or comparing route requests |
| Traffic flow and incidents vector tiles | 200,000 | Loading tiles for the visible map and zoom |
| Traffic Incidents API Details | 2,500 | Looking up event details in an area |
Monthly free allowances displayed on TomTom developer pricing, consulted 19 November 2026. Selected endpoints available for Orbis.
Imagine the museum app calculates one route when the user selects the correct entrance and recalculates it if the user changes their departure time. Those are different events from panning the map or expanding an incident explanation. Count the events separately during the trial. A screen used primarily to explore city traffic can generate many map requests with relatively few route calculations. A text-only trip estimate could produce the opposite pattern.
The developer page also directs buyers of data, SDK licensing and tailored packages to sales. A team embedding standard request-based services should compare its measured volumes with the published tiers. A buyer looking to license map data for a separate product needs an agreement covering that use. A request allowance provides an entry point for evaluating an API. It cannot settle rights, offline distribution or a wider dataset purchase.
05 / DistinctionsThe difference between a map service and a completed trip
The Mapbox Blueprint provides another view of the location stack, particularly for a team evaluating automotive conversation and branded navigation. Test both providers on addresses the customer has found difficult, with the same entrances and departure times. Compare useful route alternatives, the clarity of place selection and the actual request units required by the interface. Country-wide coverage on a product page cannot resolve a disputed local entrance.
Uber represents a different responsibility in a visitor's journey. A venue app can tell a visitor how long a car trip might take without arranging a driver, offering an available ride or estimating a fare. If the visitor needs a bookable journey, decide where the mapping experience hands over to the transport provider. The route calculation should never imply that a vehicle is waiting or that the quoted arrival time is guaranteed.
06 / QuestionsWhich changes belong to the venue and which belong to the road network
Suppose the museum temporarily sends visitors to its side entrance during a restoration. Its public address has not changed and there may be no reason for the mapmaker to edit the road network. The venue can update its destination record and show a dated note. If the city permanently changes a road's permitted direction, the route network itself may need attention. Keeping those cases separate gives the support team a specific place to report the problem.
It also pays to consider the age of every observation in the interface. A staff report entered before opening, a route estimated at lunchtime and an incident detail retrieved a few minutes later can all be accurate when collected. Combined carelessly, they can suggest a certainty the data does not support. For this proposed service, record retrieval times and define when the app should refresh the route, retire a local alert or ask the visitor to confirm the entrance.
07 / DecisionStart with the journey the operator can actually verify
A venue or destination operator
Own the approved entrance coordinates and visitor instructions. Test the last few turns and compare estimates for immediate and future departures.
A developer building a traffic map
Decide whether the interface needs rendered overlays, styled vector data or incident detail. Measure tile loads separately from event lookups during actual browsing.
An existing TomTom integrator
List the vehicle modes, features and regions the current product depends on. Compare the relevant Orbis endpoint and migration guidance for each dependency.
A business worth understanding.
Suggest your business or one you find interesting. Tell us what you want to understand about its product, positioning, design or workflows.
Suggestions are free. Selection and publication stay with the desk.
- How TomTom uses AI in mapmakingConsulted
- TomTom Orbis APIs in general availabilityConsulted
- Orbis Routing API v3 introductionConsulted
- Orbis Traffic API v2 introductionConsulted
- TomTom developer pricingConsulted

