/
AI Dispatch

Your AI dispatcher talks to drivers. Make sure it knows the road.

Placematic is the location layer under AI dispatch products: truck-legal routes, toll and fuel cost, driver hours, incidents on the road ahead and plan-versus-actual checks. HERE data, called by your backend as APIs or by your agent as MCP tools.

HERE Gold Partner since 2016
One contract, one invoice
USD billing, Placematic USA LLC
You own the agent
LIVEAI dispatcher + Placematic
Dispatcher

Dispatch load 48213: Joliet, IL to Cleveland, OH. 53′ dry van, 80,000 lb, 13′6″, 5 axles. Driver has 7 h 40 m left.

Truck route
358.8 mi · 5 h 49 min · legal for this truck
Routing v8 · truck
Tolls
$163.10 · Tri-State Tollway, Indiana Toll Road, Ohio Turnpike
Routing v8 · tolls
Hours
Fits the 7 h 40 m the driver has left
Driver schedule
Fuel
Cheapest truck-accessible diesel at mile 214
Fuel Prices
Road ahead
Lane closure, Ohio Turnpike EB · +9 min · no truck restriction
Traffic
Agent → driver

You’re good to roll. Route is legal at 13′6″ and 80,000 lb, tolls come to $163.10. A lane closure on the Ohio Turnpike adds about 9 minutes. Cheapest diesel on your way is at mile 214.

Where the advantage isTolls on the same 358.8 miles
Priced as a car$43.35what a car-profile route returns
Priced as this truck$163.105 axles, 80,000 lb

A lane quote built on car logic misses $119.75 per trip.

Why now

AI dispatch agents moved from messaging to deciding.

Chasing a missing BOL is a text message. Rerouting a loaded 53-footer, quoting a lane or telling a driver where to fuel is a decision, and a decision needs facts the model doesn't have.

01
Car logic on a truck
A model plans like a car. The low underpass, the weight-limited bridge and the truck-banned parkway aren't in its head. They are in HERE's truck attributes.
Evanston → Museum Campus, Chicago car 15.3 mi, 49 min · truck 28.5 mi, 1 h 31 min
02
Costs it can't see
Tolls by axle count and the diesel spread along a corridor decide whether a load makes money. Neither lives inside a language model.
Joliet → Cleveland tolls car $43.35 · 5-axle truck $163.10
03
Answers nobody can audit
When the agent tells a driver to reroute, your ops team needs the vehicle profile, the time and the data source behind that call. A guess has none of them.
Computed for: truck (height 411 cm, gross weight 36287 kg, length 2195 cm, 5 axles), departure now
Ideas to build

Combine the checks. Ship features your customers notice.

Each idea is two or three HERE APIs your agent calls in sequence. Pick a moment in the load's life and see what your dispatcher could say.

Quote the lane in seconds

agent
Joliet to Cleveland: 358.8 mi, 5 h 49 min, $163.10 in tolls for 5 axles. That's $119.75 more than a car-priced quote.
Rate quotes built on what the truck will actually pay.
Routing v8 · truck
+
Toll costs
+
Fuel Prices

Pick the truck that should take it

agent
Truck 214 is 38 mi from pickup with 9 h of drive time left. Truck 107 is closer but runs out of hours before delivery.
Loads assigned by deadhead and hours left, not by who picked up the phone.
Matrix Routing
+
Driver schedule
+
Isoline

Turn an order email into clean stops

agent
3 of 41 delivery addresses match only to a street, not a building. Confirm them before dispatch?
Bad addresses caught at intake, not at the dock.
Geocoding & Search
+
Batch Geocoding

Put the stops in the right order

agent
Swapping stops 4 and 6 saves 23 miles and keeps every delivery inside its window.
Multi-stop loads sequenced around time windows and truck access.
Waypoints Sequence
+
Tour Planning

Fuel where the break falls

agent
Your 30-minute break lands near mile 214. The truck stop there is the cheapest diesel within 2 miles of the route.
One stop instead of two: rest and fuel planned together.
Driver schedule
+
Fuel Prices

Check the weather before wheels roll

agent
Winter storm warning on I-80 near Des Moines from 6 AM. Leaving at 3:30 AM clears it. Want me to tell the driver?
Departure times set around the storm, not discovered in it.
Destination Weather · route alerts
+
Routing v8 · truck

Plan charging for electric trucks

agent
This route needs one charge: a fast charger 0.4 mi off I-94 at mile 142, about 40 minutes.
Electric trucks dispatched with the charging stop already in the plan.
Routing v8 · EV
+
EV Charge Points

Log arrival and detention on their own

agent
Arrived at the shipper 7:58 AM, still on site at 10:31. Free time ended at 9:58, so 33 minutes are billable so far.
Detention claims backed by timestamps, not driver memory.
Geofencing
+
your ELD positions

Give the dock a heads-up

agent
Load 48213 is 15 minutes out. I've sent the ETA to the receiver so door 7 is ready.
Receivers ready when the truck pulls in, fewer hours lost at the gate.
Geofencing
+
Routing v8 · ETA

Answer “what's ahead?” in one line

agent
Lane closure at mile 212 adds about 9 minutes. Light snow after Toledo. Nothing that restricts your truck.
The driver gets what matters on this route, not a traffic map.
Traffic · incidents
+
Destination Weather · route alerts

Show what the trip really cost

agent
The driver left the plan near Gary, IN: 14 extra miles and $22.40 more in tolls than quoted.
Plan versus actual in dollars, ready for the settlement.
Route Matching
+
Toll costs · driven route

Find the lanes that always run late

agent
Joliet to Cleveland loads leaving between 3 and 5 PM arrive 41 minutes late on average. Leaving before 1 PM avoids it.
ETAs set by how each lane really drives, hour by hour.
Traffic Analytics
+
Route Matching
The toolbox

One contract. The whole HERE toolbox.

Everything in the ideas above, plus what you'll think of next, under a single Placematic agreement.

Find the place

Geocoding & Search
addresses, access points, places
Batch Geocoding
whole order files at once
Positioning
cell and Wi-Fi location when GPS drops

Route and assign

Routing v8

truck profiles, driver schedule, EV

Matrix Routing

every truck to every load

Isoline

who can reach pickup in time

Waypoints Sequence · Tour Planning

stop order and fleet-wide plans

Price the trip

Toll costs

per vehicle, transponder or cash

Fuel Prices

station prices along the route

EV Charge Points

chargers and availability

Know the conditions

Traffic

incidents, closures and flow

Destination Weather

forecasts and alerts along the route

Map Attributes

truck restrictions as data layers

Prove what happened

Route Matching

the road actually driven

Geofencing

in or out of a facility, zone or state

Traffic Analytics

historical speeds by hour

In the cab

HERE SDK

truck turn-by-turn in your driver app, offline maps
Two ways to plug in

Call it from your backend, or let your agent call it.

Same data, same answers. The MCP Server is a thin layer over the same APIs your backend calls.

REST APIs

Your backend decides
Best when your product already owns the workflow and the agent reads results from your own services. Every HERE Location Service under one Placematic contract.
GET /routes
  ?transportMode=truck
  &origin=41.5250,-88.0817
  &destination=41.4993,-81.6944
  &vehicle[height]=411
  &vehicle[grossWeight]=36287
  &vehicle[axleCount]=5
  &return=summary,tolls
  &apiKey=YOUR_KEY

MCP Server

Generic location MCP servers stop at car-grade geocoding and routing. Placematic's tools answer as a truck: routes legal for the vehicle profile, tolls priced for it, and territory assignment. Every answer states the profile it was computed for.
// tool call
placematic_route {
  transport_mode: "truck",
  truck_height_cm: 411, truck_gross_weight_kg: 36287,
  truck_length_cm: 2195, truck_axle_count: 5, …
}
// result
Distance: 358.8 miles · 5 h 49 min
Computed for: truck (411 cm, 36287 kg, 2195 cm, 5 axles)
Tolls: USD 163.10 across 6 toll points
Your agent decides
In production

Dispatch software already runs on this stack.

Teams that put HERE routing in front of dispatchers and drivers through Placematic.

Fleet & ELD
ELD platform
Truck routing with road restrictions and the HERE Maps SDK in the driver app.
100+ vehicles
2 weeks to integration
Truck routing
HERE Maps SDK
Logistics & distribution
Dispatcher intelligence platform
A distribution company's dispatcher tool that re-optimizes routes on its own when new orders arrive.
Routing
Route Optimization
Geocoding
Fleet telematics
Embedded truck navigation
Truck navigation inside a telematics provider's driver tablet app, with corridor compliance and offline maps.
HERE Maps SDK
Truck routing
Guardrails

Answers your ops team can sign off on.

Truck profile on every answer

Each result states the vehicle profile, departure time and conditions it was computed for, so a reroute can be traced back.

Read-only, scoped, logged

Per-agent keys, scoped access and rate limits. Every tool call is logged with agent identity, query and data version.

Licensed map data

HERE data, licensed rather than scraped, with regular refreshes of roads and truck attributes. Your territory data is never used for model training.

Cost you can see

Pilot keys are capped. Every check maps to HERE transactions you can count per load before you scale.
Pricing

Priced the way your product is sold.

One contract and one USD invoice from Placematic USA LLC, whichever model fits.

Per transaction
Pay for what your agent calls.
For products that call location per action: quotes, address checks, one-off route lookups. Geocoding starts at $0.88 per 1,000 requests after the monthly free tier.
Per tracked truck
One monthly price per asset.
For fleets your product routes every day: routing with optimization, tolls and traffic for each truck, with fuel prices as an add-on. If your agent routes trucks and warns drivers about restrictions, this is the plan. Geofencing is available only here.
How it goes

From first call to production in weeks.

1

Map your dispatch loop

Fill in the short request form: which checks your agent makes, at which step of the load, for how many trucks.
2

Pilot one check on real loads

Wire one check end to end on a capped key. We suggest starting with truck-legal routing: it's the one drivers notice first.
3

Go live on the right plan

Per transaction or per truck. Integration typically takes one to three weeks.

Questions dispatch teams ask

No. You own the agent, the driver relationship and the product. We supply the location layer underneath it and stay out of your customers’ workflow.

REST when your backend owns the workflow, MCP when the agent should choose which check to run. You can mix them: the MCP Server sits on the same APIs, so the answers match.

HERE truck routing takes a driver schedule (driving and rest periods) and splits the route accordingly. You pass the hours left from your ELD; the HOS rules engine stays yours.

Any. Positions come from your ELD or telematics feed. Route Matching accepts GPS traces as GPX, NMEA, KML, CSV or GeoJSON.

No. Placematic answers the questions your agent asks about a live load. Years of GPS history and fleet-wide analysis belong in your own analytics stack, whether that’s a lakehouse, Databricks or Snowflake. Route Matching results come back as JSON you can store there.

If your product routes trucks and warns drivers about restrictions, it’s a fleet use case, licensed per tracked asset. Backend-only lookups such as quotes and address checks can run per transaction. We’ll tell you which in our reply to your request.

Your agent talks to drivers. Let it know the road.

Tell us which checks your dispatcher makes. Two minutes, no call needed.

What you get back
Which HERE APIs cover each check
An estimate of what those checks cost per load
A capped pilot key to test on real loads

Request a pilot

    What should your agent check?


    No commitment. By sending, you agree to our Privacy Policy.