Live dispatch map
Fleet vehicles overlaid on city availability. Route drivers to the nearest open spot or loading zone. Reroute around high-enforcement blocks in real time.
For fleets & operators
Better trip management, stop by stop. Parkspot gives your drivers and dispatchers the curb as data: where a van can legally stop right now, for how long, and what the block looks like on camera before it arrives. Data layers and an API for your routing stack, on request, plus a dispatch workspace and a companion app for drivers.
Looking for our mobile app? DriversMobile app·Cities



Three ways your dispatcher will use it
Your dispatcher sees availability at block-face resolution. Parkspot assigns vehicles to the nearest open curb or loading zone, routes them around known-hot enforcement blocks, and flips assignments live when conditions change.
What ships with Parkspot Fleet
Fleet vehicles overlaid on city availability. Route drivers to the nearest open spot or loading zone. Reroute around high-enforcement blocks in real time.
Predicted LZ availability, turnover rate, and misuse detection. Dispatch a van to an LZ that'll be clear when it arrives.
Historical ticket hotspots by block, hour, and day. Per-route exposure scoring. Automatic avoidance in dispatch recommendations.
Per-vehicle, per-driver, per-route efficiency. Hours saved, fuel burned in search, dollar impact.
Fleet-mode of the Parkspot app: spot assignments, auto-log park events, tap-to-report, LZ priority.
Native telematics with Samsara, Geotab, Motive, Verizon Connect, Fleetio. REST and streaming APIs for custom integrations.
Modules in depth
Module 01
Fleet vehicles on a live curb availability map. Driver-level routing. Loading zone priority. Ticket-risk avoidance baked into recommendations.
Module 02
The differentiator for delivery. We predict LZ availability 5/15/30 minutes out and flag misuse in real time.
Module 03
Ticket hotspot history + per-route exposure scoring. Drivers see the risk before they park; routes avoid it by design.
Module 04
Per-vehicle, per-driver, per-route efficiency. Search time reduction tracking. Fuel savings via telematics integration.
Module 05
Fleet mode inside the Parkspot app. Spot assignments. Auto-log park events. Tap-to-report. Loading zone priority.
Module 06
Native telematics with the major TSPs. REST and streaming APIs. Webhook events into your dispatch system.
Data & API
New York and London are where we go deep: posted rules per block-face, loading bays with length and hours, live camera stills. Delivered as layers your planner can read, or through the Curb & Parking API.
All five boroughs
Every posted curb sign decoded to a block-face rule, with the sign text kept verbatim.
Curb coverage: which faces are signed, which have no curb to park at, and where the record is blank.
Live stills from the city and state camera networks we run.
Free and occupied curb from computer vision, with a confidence figure per block-face.
Camden, Westminster, 12 more boroughs
Parking and loading bays with their hours, maximum stay and length, so a 7.5 t van knows whether it fits.
Controlled parking zone boundaries and the hours they apply.
Live stills from the city-wide traffic camera network.
Free and occupied curb from computer vision, with a confidence figure per block-face.
Also live: Edinburgh bays, off-street parking in both cities, and 25,000+ cameras with 52 traffic and road feeds across 10 countries. Every layer exports as GeoJSON for the area you work in.
Who it is for
Written as a specification with illustrative responses, so your team can see the shapes before a line of code. Pilot access is by arrangement.
GET /v1/kerb/legality
Can this vehicle stop here, right now, for twenty minutes, and if not, until when is it barred?
GET /v1/kerb/nearest-legal
The closest curb where this vehicle may legally stop for the time it needs, with the walk from the door.
GET /v1/routes/kerb-plan
Give us a day's stops; get back where each one can legally park and which stops need re-timing.
POST /v1/kerb/rules
Every regulated block-face in a bounding box, with its posted signs verbatim and its measured geometry.
GET /v1/kerb/schedule
One block-face's week, hour by hour: when it is metered, swept, cleared for rush hour, or free.
Data held: the layer is on the platform today and the route is plumbing. Pilot: switched on per study area. 8 further endpoints, coverage beyond the two focus markets, and the figures behind each layer go out on a pilot call. Counts as of September 2026.
Request pilot accessVertical-specific
LZ availability is the differentiator. Cut search time, predictably land at a cleared loading zone, and avoid the blocks where your drivers keep getting tickets.
~1.5 hrs / vehicle / week of search time cut (modeled)
Integrations
Modeled annual savings
Three inputs. No email required. Modeled on ~1.5 hrs/week search-time recovered per vehicle, ~20% reduction in parking violations, and $115 average NYC commercial-fleet fine.
Estimated annual savings
$82K
Estimate anchored in Dalla Chiara & Goodchild 2020, SFpark 2014, and NYC DOF. Actual savings validated in 60-day pilot.
Curb-rule layers
17
NYC + London + Edinburgh, per block-face
Mapped bays
50,000+
Camden + Westminster, with length and hours
Cameras
25,000+
live stills, 10 countries (September 2026)
NYC signs decoded
~440K
every posted rule, kept verbatim
Hours recovered
~1.5
hrs / vehicle / week (modeled)
Tickets avoided
~20%
modeled reduction
Time to ROI
60d
target pilot payback
API uptime
99.9%
SLA target
30-minute demo tailored to your vehicle count and delivery patterns.