DockDuty Data: the datasets behind the depot business, free to cite
The machine-readable files DockDuty publishes and maintains about the robotaxi depot business: what each covers, when it was last updated, and the CSV or JSON behind it. Each one has a methodology, a source per row or a named source, a change log and a correction address on its own page.
Here: the datasets DockDuty builds from public sources or from its own order book, each one dated, with a definition for every field and a download a crawler or a script can fetch directly. Not here: anything about an individual owner, reservation or vehicle; DockDuty’s internal metrics; and any figure a page cannot source. Where a number is not published by anyone, the row says unknown rather than estimating.
DockDuty sells depot stalls for privately owned Cybercabs, so it is not a neutral party in this market. Its own demand, its own planned depot and its own rate card sit in these files on the same terms as everyone else’s, and nothing in them is a recommendation or a forecast.
Cybercab stall reservations across the 21 US markets DockDuty sells: network-wide totals, founding and Priority Owner books, a status and depot status per market. Reservations, not vehicles.
112 stall reservations · 8 of 21 markets with at least one
Every publicly documented US robotaxi depot, charging hub, service center and production plant: operator, status, size, capacity, charging, dates, one source per row and the date it was last verified.
Companies that build, run, charge, staff or orchestrate robotaxi depots in the United States, in six categories, with what each does, its markets and observable status signals. No ratings, no ranking.
Every US metro with driverless robotaxi service, by operator, with launch dates and zone notes, plus the announced markets. A metro counts as live when one operator gives public riders driverless rides there.
The vocabulary of the robotaxi depot industry, each term with a neutral definition that can be quoted on its own, its synonyms and the page that owns the concept.
The published stall rates, service fees, deposit and onboarding fee, generated from the same pricing source the checkout uses, so the page and the file cannot disagree.
The method lives with the data, not here, so it cannot drift from the table it describes. Each page states its inclusion rule, what it excludes, how a status is assigned and what was actually verified:
The reservation counts in the owner-demand dataset are a dated snapshot of DockDuty’s own order book. The live view is on the order book, every market’s status and the demand by market are on the DockDuty Network page, and the snapshot file itself is traction.json, which every count on this site is written from.
License and corrections
The datasets are published under Creative Commons Attribution 4.0: use them, quote them, build on them, and credit DockDuty with a link to the page or the row. The rate card is a published price schedule rather than a licensed dataset; quote it with a link and a date, because prices change.
Why a depot company publishes data. The ground layer under every robotaxi fleet, the depots, the companies that run them and the owners who want a stall, is mostly undocumented. These files are DockDuty’s working record of it, published so a journalist, an analyst or an owner can check the same numbers the founders use.