Predictika · Map and location API usage quotes

An AI sales agent's TomTom Maps API usage quote, checked before it goes out

An AI sales agent prepares a monthly usage quote for the TomTom map APIs on the pay-as-you-grow plan: Map Display vector and raster tiles, Routing, Geocoding, Reverse Geocoding, Places Search, Traffic Flow and Incidents tiles and Traffic Flow Segment Data, on TomTom Orbis Maps or the previous-generation TomTom Maps, with a free monthly allowance and volume levels for each API, a prepaid balance and a spending cap. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of TomTom's public pricing page and returns a verdict, every reason, a line-item quote and the figures it computed.

Scope: TomTom map API monthly usage quotes: Map Display vector and raster tiles, Routing, Geocoding, Reverse Geocoding, Places Search Suggest and Discover, Traffic Flow and Incidents vector tiles and Traffic Flow Segment Data, on Orbis or previous-generation maps, at any request volume. See everything this validator covers

This validator models monthly usage quotes for these TomTom APIs, not just the scenarios shown below. The API names, the map generation each API is offered on, the free monthly requests and the three volume levels of each API follow TomTom's public pricing page; the rates per 1,000 requests and several limits are modeled and labeled that way.

  • APIs — Map Display API Vector Tiles and Raster Tiles, Routing API, Geocoding API, Reverse Geocoding API, Places Search API Suggest and Discover, Traffic Flow & Incidents API Vector Tiles and Traffic Flow API Segment Data, each with its free monthly requests and volume levels.
  • Plans — pay as you grow or prepaid, with an optional monthly spending cap; APIs that TomTom sells only through Sales (Fuel Prices, Parking, Points of Interest, Traffic Stats and others) are not pay as you grow.
  • What the validator checks — Places Search against Orbis maps, Segment Data against the previous-generation maps, contract-only APIs, the request rate, the spending cap, the prepaid minimum and balance, and the stated charges and billable requests.
  • Approvals — volume above the highest level of an API, monthly charges above $50,000 and charges within 10 percent of the spending cap go to a person.

Any monthly usage quote that touches these APIs and rules is in scope — not only the scenarios pictured here. Not covered: Matrix Routing and the other APIs with small free allowances, SDKs, map data licences, enterprise contracts and taxes. The rates on this page are illustrative: they are modeled, not TomTom prices.

The AI sales agentBuilds the usage quote from the conversation with the customer and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

7 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI sales agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      

        
        
        
      

      
Waiting for the call.

      
    

  

  
  

    
Where rules-based CPQ gets it wrong
Click to expand
    
Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

    
What the validator caughtTypical rules-based CPQPredictika
Tiered usage charges across many APIsOnly with workarounds
Each API has its own free allowance and volume levels, so one month's charge is a sum of bands over nine APIs; a typical CPQ prices a unit price times a quantity, not a banded sum.		The bands of every API are computed and each band is a line on the quote.
APIs that exist on one map generation onlyOnly with care
Places Search is offered on Orbis Maps and Segment Data on the previous-generation maps; a product rule per API against a quote-level choice of map generation.		The map generation is checked against every API in the quote.
APIs that cannot be sold onlineOnly with care
Some APIs are available only through Sales; a self-service quote must keep them out, one product rule at a time.		Contract-only APIs in the quote are a finding.
A spending cap and a prepaid balanceOnly with workarounds
The cap and the balance are compared with a charge that is only known after the bands are summed; a rule over a computed total, in the right order.		Charges are computed first and compared with the cap and the balance on every call.
A request-rate limit of the planOnly with workarounds
The peak requests a second belongs to the application, not the order; it has to be asked for and compared with the plan limit.		The peak rate is an input checked against the plan limit.
Stated charges and billable requests that matchOnly with workarounds
The agent's own figures are text on a quote; nothing compares them with the banded sum unless someone builds that check.		Both stated figures are fields the validator compares with its own.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the quote is saved or a step is completed, so a rep often fixes one error and meets the next.		All findings come back together, whatever order the choices arrived in.

  

  

    
What this validator catches: findings from its test cases
Click to expand
    
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.

    
11 thousand requests a month are above the highest volume level of an API, where a person should confirm the rate with TomTom Sales.
2Places Search API Suggest and Discover run on TomTom Orbis Maps, and the quote uses the previous-generation TomTom Maps.
3Traffic Flow API Segment Data is available on the previous-generation TomTom Maps only, and the quote uses TomTom Orbis Maps.
4The quote includes 1 API that TomTom sells only through a custom contract with Sales (such as Fuel Prices, Parking or Traffic Stats); they cannot be quoted as pay as you grow.
5The application sends up to 51 requests a second; the pay-as-you-grow plan allows up to 50 and requests above it are refused.
6The estimated monthly charges of $384.00 are within 10 percent of the monthly spending cap of $384.00, so a person should confirm.
7The estimated monthly charges are $384.00, above the monthly spending cap of $383.99.
8The prepaid balance is $999.99; a prepaid plan needs at least $1,000.00.
9The prepaid balance of $5,000.00 does not cover the estimated monthly charges of $5,135.00.
10The estimated monthly charges are $61,684.00, above $50,000.00, so a person should confirm.
11The quote states monthly charges of $707.49, but the request volumes and rate bands give $707.50.
12The quote states 4.069 million billable requests a month after the free allowances, but the volumes give 4070 thousand.

  

  

    
Scenarios and results
Click to expand
    
The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

    
1. Fleet routing app, Orbis maps: A quote for a fleet routing app with tiles, routing, search and traffic segment data

    
The agent's request. Please quote a monthly TomTom API usage of 60 million vector tile requests, 30 million traffic vector tile requests, 4.2 million Routing API requests, 900,000 Geocoding API requests, 600,000 Reverse Geocoding API requests, 3 million Traffic Flow Segment Data requests, 2.5 million Places Search Suggest requests and 300,000 Places Search Discover requests on TomTom Orbis Maps, on the pay-as-you-grow plan, with a monthly spending cap of $13,000.00. The application sends up to 120 requests a second. The quote states 101.005 million billable requests a month and monthly charges of $11,251.75. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Segment Data needs previous-generation Maps. Traffic Flow API Segment Data is available on the previous-generation TomTom Maps only, and the quote uses TomTom Orbis Maps.
    • 
      
  • Request rate above the pay-as-you-grow limit. The application sends up to 120 requests a second; the pay-as-you-grow plan allows up to 50 and requests above it are refused.
    • 
      
  • Monthly charges above the spending cap. The estimated monthly charges are $13,186.75, above the monthly spending cap of $13,000.00.
    • 
      
  • Stated total differs from the computed total. The quote states monthly charges of $11,251.75, but the request volumes and rate bands give $13,186.75.
    • 
    

    
2. Fleet routing app, Orbis maps: The agent resubmits after fixing the errors

    
The agent's request. Please quote a monthly TomTom API usage of 60 million vector tile requests, 30 million traffic vector tile requests, 4.2 million Routing API requests, 900,000 Geocoding API requests, 600,000 Reverse Geocoding API requests, 2.5 million Places Search Suggest requests and 300,000 Places Search Discover requests on TomTom Orbis Maps, on the pay-as-you-grow plan, with a monthly spending cap of $13,000.00. The application sends up to 45 requests a second. The quote states 98.025 million billable requests a month and monthly charges of $11,251.75. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Quote summary. 98.025 million billable requests a month, estimated monthly charges $11,251.75 (illustrative prices, not TomTom prices).
    • 
    

    
3. Store locator, previous-generation maps: A quote for a store locator that uses Places Search on previous-generation maps

    
The agent's request. Please quote a monthly TomTom API usage of 400,000 vector tile requests, 60,000 Routing API requests, 15,000 Geocoding API requests, 400,000 Places Search Suggest requests and 120,000 Places Search Discover requests on the previous-generation TomTom Maps, on the pay-as-you-grow plan. The application sends up to 12 requests a second. The quote states 780 thousand billable requests a month and monthly charges of $421.75. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Places Search needs Orbis Maps. Places Search API Suggest and Discover run on TomTom Orbis Maps, and the quote uses the previous-generation TomTom Maps.
    • 
      
  • Stated billable requests differ. The quote states 780 thousand billable requests a month after the free allowances, but the volumes give 745 thousand.
    • 
    

    
4. Store locator, previous-generation maps: The agent resubmits after fixing the errors

    
The agent's request. Please quote a monthly TomTom API usage of 400,000 vector tile requests, 60,000 Routing API requests, 15,000 Geocoding API requests, 400,000 Places Search Suggest requests and 120,000 Places Search Discover requests on TomTom Orbis Maps, on the pay-as-you-grow plan. The application sends up to 12 requests a second. The quote states 745 thousand billable requests a month and monthly charges of $421.75. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Quote summary. 745 thousand billable requests a month, estimated monthly charges $421.75 (illustrative prices, not TomTom prices).
    • 
    

    
5. Delivery marketplace: A quote for a delivery marketplace with contract-only APIs and a high request rate

    
The agent's request. Please quote a monthly TomTom API usage of 8 million vector tile requests, 900,000 Routing API requests, 700,000 Geocoding API requests and 300,000 Reverse Geocoding API requests on TomTom Orbis Maps, on the pay-as-you-grow plan. The application sends up to 80 requests a second, and the quote includes 2 further APIs that TomTom sells through Sales. The quote states 9.64 million billable requests a month and monthly charges of $2,004.00. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • API sold only by custom contract. The quote includes 2 APIs that TomTom sells only through a custom contract with Sales (such as Fuel Prices, Parking or Traffic Stats); they cannot be quoted as pay as you grow.
    • 
      
  • Request rate above the pay-as-you-grow limit. The application sends up to 80 requests a second; the pay-as-you-grow plan allows up to 50 and requests above it are refused.
    • 
    

    
6. Delivery marketplace: The agent resubmits after fixing the errors

    
The agent's request. Please quote a monthly TomTom API usage of 8 million vector tile requests, 900,000 Routing API requests, 700,000 Geocoding API requests and 300,000 Reverse Geocoding API requests on TomTom Orbis Maps, on the pay-as-you-grow plan. The application sends up to 50 requests a second. The quote states 9.64 million billable requests a month and monthly charges of $2,004.00. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Quote summary. 9.64 million billable requests a month, estimated monthly charges $2,004.00 (illustrative prices, not TomTom prices).
    • 
    

    
7. Heavy tile and routing app: A quote for a heavy tile and routing app at 400 requests a second

    
The agent's request. Please quote a monthly TomTom API usage of 150 million vector tile requests and 12 million Routing API requests on TomTom Orbis Maps, on the pay-as-you-grow plan. The application sends up to 400 requests a second. The quote states 161.78 million billable requests a month and monthly charges of $14,119.00. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Request rate above the pay-as-you-grow limit. The application sends up to 400 requests a second; the pay-as-you-grow plan allows up to 50 and requests above it are refused.
    • 
      
  • Volume above the highest level. 52 million requests a month are above the highest volume level of an API, where a person should confirm the rate with TomTom Sales.
    • 
    

  

  

    
Narration transcript
Click to expand
    
The text of the narrated walkthrough, step by step.

    
    
      
  1. Welcome to a demo of Predictika's Validator. An AI sales agent prepares a monthly usage quote for the TomTom map APIs on the pay-as-you-grow plan: Map Display vector and raster tiles, Routing, Geocoding, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of TomTom's public pricing page and returns a verdict, every reason, a line-item quote and the figures it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote a monthly TomTom API usage of 60 million vector tile requests, 30 million traffic vector tile requests, 4.2 million Routing API requests. The application sends up to 120 requests a second. The rest of the request is on screen. The quote states 101.005 million billable requests a month and monthly charges of $11,251.75.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with four findings, all in one answer. Traffic Flow API Segment Data is available on the previous-generation TomTom Maps only, and the quote uses TomTom Orbis Maps. The application sends up to 120 requests a second; the pay-as-you-grow plan allows up to 50 and requests above it are refused. The estimated monthly charges are $13,186.75, above the monthly spending cap of $13,000.00. The other one is on screen.
    6. 
      
  6. The validator returned four blocking findings in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the quote are checked against each other and against the stated total.
    7. 
      
  7. What this shows: for a request-rate limit of the plan, a rules-based CPQ can do this only with workarounds.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the peak requests a second to 45 and the stated billable requests a month to 98,025,000. It removes the Traffic Flow Segment Data requests a month.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. The validator also returns the line-item quote. It starts with Map Display API Vector Tiles and Map Display API Vector Tiles; the other eleven lines are on screen.
    13. 
      
  13. All four earlier findings are cleared, and the validator's total, $11,251.75, matches the quote.
    14. 
      
  14. Four problems caught in one call, fixed in one pass, and a clean quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.
    15.