For cities
Govern your robot pilot from evidence.
Sidewalk robots and robotaxis ask Plynth before they cross, stop at a curb or go through a door, so the city sets the conditions and sees every request, whichever company the robot belongs to.
01
Permit conditions, measured
Set the permit’s numbers: fleet caps, speed, crossing on WALK, curb ramps clear. Each company is measured against them from its robots’ own requests, not from what it reports.
02
Keep-outs on a two-minute clock
Police and fire send a keep-out order and every company gets it at once, with two minutes to confirm and be out. The order shows who confirmed, who’s out and who’s late.
03
Curb ramps kept clear
Every minute a robot stands on a curb ramp is counted, by company. Robots are kept off any sidewalk too narrow for a wheelchair to pass them.
04
311 complaints, traced
Residents report a robot to 311 without needing to know whose it was. The complaint is traced to the robot most likely there, and the company’s answer goes in the month’s report.
05
The month, for council
One page in plain numbers: each company’s rates per 1,000 trips, curb ramp minutes, complaints and the city’s steps. Residents see the same numbers on a public dashboard.
06
Requests, not routes
No robot routes, camera images or callers’ names are kept: only each request and what the city’s rules decided. Every read of the data is counted, and the count is public.
For cities
Your conditions, measured from your own record.
Fifteen minutes on a simulated street: each company against its permit, a keep-out order on its two-minute clock, and the month as council would see it.