For cities
Connect every robot on your streets.
Agentic middleware directing autonomous robots and vehicles across sidewalks, crosswalks and curbs.
Crosswalks that answer
A robot with your permit can push the crosswalk button, just as a person would. Every company asks the same way, so there’s nothing to set up for each one.
Curbs held for pickupsCDS 1.1
A robotaxi gets a loading zone held for its pickup, with the curb’s rules sent ahead: where to stop, how close, how long.
Closures that reach every robotWZDx 4.2
Police and fire close a block, and every company’s robots and robotaxis get it at once, with the way around. Each one’s way out is on the record.
Rules by place and hourMDS Policy 2.1
School hours, a market day, a walk too narrow to pass: set a rule for a place and a time once, and every robot that asks to go there is sent the way around.
The month, for councilMDS 2.1
One page in plain numbers, by company: trips, crossings, closures cleared and 311 reports answered, with the permits renewed and the blocks opened. Residents see the same numbers on a public dashboard.
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.
Nothing new to publish: it reads the feeds your department already keeps, and reports back in the formats you use, MDS, CDS, WZDx and Open311.
For robot companies: one API asks for the crosswalk, the curb and the closures, the same way in every city. Start building →
The city’s screen
Your streets, and the robots on them, live.

For cities
Your conditions, measured from your own record.
See a robot ask to cross, a robotaxi take the curb, a closure reach every company at once, and the month’s report for council.