Dispatch map (in development)
Fleet vehicles overlaid on city availability. The dispatch map will route drivers to the nearest open spot or loading zone and steer them around high-enforcement blocks.
For fleets & operators
Know where each van can legally stop, before it arrives.
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 are available on request. A dispatch workspace and a companion app for drivers are in development.
Looking for our mobile app? DriversMobile app·Cities
Three ways your dispatcher will use it
Dispatch. Optimize. Report.
Send every vehicle to the right spot before it arrives.
Your dispatcher sees availability at block-face resolution where detection is switched on (pilot study areas). 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.
- Block-face occupancy where detection is switched on (pilot study areas)
- Loading zone priority for commercial fleets
- Reroute around high-enforcement blocks
What Parkspot Fleet is built to do
Six modules covering dispatch through reporting.
Loading zone intelligence
Predicted LZ availability, turnover rate, and misuse detection. Dispatch a van to an LZ that'll be clear when it arrives.
Ticket risk & avoidance
Historical ticket hotspots by block, hour, and day. Per-route exposure scoring. Automatic avoidance in dispatch recommendations.
Fleet analytics
Per-vehicle, per-driver, per-route efficiency. Hours saved, fuel burned in search, dollar impact.
Driver app
Fleet-mode of the Parkspot app: spot assignments, auto-log park events, tap-to-report, LZ priority.
Integrations & API
Planned connectors: Samsara, Geotab, Motive, Verizon Connect, Fleetio, built with the first pilot fleet. API specified; access by arrangement.
Modules in depth
A closer look at each capability.
Module 01
Dispatch map (in development)
Fleet vehicles on a live curb availability map. Driver-level routing. Loading zone priority. Ticket-risk avoidance baked into recommendations.
- Block-face occupancy + turnover where detection is on
- Loading zone assignment and turnover prediction (planned)
- Ticket hotspot avoidance
Module 02
Loading zone intelligence
The differentiator for delivery. We will predict LZ availability 5/15/30 minutes out and flag misuse in real time.
- Forward-looking availability forecasts
- Dwell-time + turnover per zone
- LZ misuse detection (private vehicles in commercial zones)
Module 03
Ticket risk & avoidance
Ticket hotspot history + per-route exposure scoring. Drivers see the risk before they park; routes avoid it by design.
- Historical violations by block/hour/day
- Per-route ticket exposure scoring
- Post-trip ticket analysis
Module 04
Fleet analytics
Per-vehicle, per-driver, per-route efficiency. Search time reduction tracking. Fuel savings via telematics integration.
- Search time reduction vs baseline
- Hours recovered per month
- Fuel savings + dollar-cost impact
Module 05
Driver mobile app
Fleet mode inside the Parkspot app. Spot assignments. Auto-log park events. Tap-to-report. Loading zone priority.
- Push: 'spot assigned'
- Auto-log park events for reporting
- Tap-to-report (LZ blocked, unsafe, ticket)
Module 06
Integrations & API
Planned connectors for the major telematics providers, built with the first pilot fleet. API specified; access by arrangement.
- Planned connectors: Samsara · Geotab · Motive · Verizon Connect · Fleetio
- TMS (planned): Descartes, Project44, Trimble
- Dispatch software (planned): Route4Me, OptimoRoute, Onfleet
Data & API
The curb, as data, for your routing stack.
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.
New York City
All five boroughs
- Live
Every posted curb sign decoded to a block-face rule, with the sign text kept verbatim.
- Live
Curb coverage: which faces are signed, which have no curb to park at, and where the record is blank.
- Live
Live stills from the city and state camera networks we ingest.
- Pilot
Free and occupied curb from computer vision, with a confidence figure per block-face.
London
Camden, Westminster, 12 more boroughs
- Live
Parking and loading bays with their hours, maximum stay and length, so a 7.5 t van knows whether it fits.
- Live
Controlled parking zone boundaries and the hours they apply.
- Live
Live stills from the city-wide traffic camera network.
- Pilot
Free and occupied curb from computer vision, with a confidence figure per block-face.
Also live: Edinburgh bays, off-street parking in both cities, 59,000+ cameras from 54 sources across 30 US states and 10 countries, and 97 traffic and road data feeds. Every layer exports as GeoJSON for the area you work in.
Who it is for
- Delivery and routing platforms
- Fleet and telematics products
- Navigation and mapping
- Proptech and location intelligence
- Parking operators
- City teams and researchers
The Curb & Parking API
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?
Data heldGET /v1/kerb/nearest-legal
The closest curb where this vehicle may legally stop for the time it needs, with the walk from the door.
Data heldGET /v1/routes/kerb-plan
Give us a day's stops; get back where each one can legally park and which stops need re-timing.
Data heldPOST /v1/kerb/rules
Every regulated block-face in a bounding box, with its posted signs verbatim and its measured geometry.
Data heldGET /v1/kerb/schedule
One block-face's week, hour by hour: when it is metered, swept, cleared for rush hour, or free.
Data held
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 October 2026.
Request pilot accessVertical-specific
Built for the specifics of your operation.
For last-mile and multi-stop delivery fleets.
LZ availability is the differentiator. The goal: less search time, a cleared loading zone at drop-off, and fewer stops on the blocks where your drivers keep getting tickets.
- Predicted LZ availability at drop-off
- Block-face ticket risk
- Per-route dwell and turnover analytics
~1.5 hrs / vehicle / week of search time cut (modeled)
Planned integrations
Telematics we plan to connect.
Samsara
Geotab
Motive
Verizon Connect
Fleetio
Modeled annual savings
See what Parkspot could save your fleet.
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.
vehicles
$/ hour
tickets
Estimated annual savings
$82K
- Hours recovered1,875 / yr
- Labor savings$71K
- Ticket avoidance$11K
Book a demo
Estimate anchored in Dalla Chiara & Goodchild 2020, SFpark 2014, and NYC DOF. Actual savings validated in 60-day pilot.
Curb-rule layers
37
NYC, London, Seattle, LA and 7 more cities, per block-face
Mapped bays
50,000+
Camden + Westminster, with length and hours
Cameras
59,000+
live stills and video, 30 US states, 10 countries (October 2026)
NYC signs decoded
440,000+
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
See how much your fleet could save.
30-minute demo tailored to your vehicle count and delivery patterns.