How it works
A marketplace with no human renter in the loop
Every booking on ParkFSD is executed and monitored through an AV provider's API. Phase 1 (this build) runs on a simulated/mock provider adapter so the full booking, vacate, and tandem-cascade logic works end-to-end before a real provider is connected.
1. A host registers a space
A property owner registers a location, draws the exact boundary of a rentable space on a map, sets physical constraints and amenities, and defines an availability schedule and rate.
2. An operator registers a vehicle
A vehicle owner registers their self-driving vehicle, linking it to its AV provider (Tesla FSD, Waymo, etc.) — every booking is executed through that provider's API, never by a person behind the wheel.
3. The vehicle books and arrives
The operator books an available window. The provider commands the vehicle to arrive, and the reservation goes active once it occupies the space.
4. Vacate is commanded, not requested
When it's time to leave, the system issues a vacate command to the provider and tracks acknowledgement, movement, and confirmed departure — sequencing multiple vehicles automatically in tandem spaces.
5. Faults are the system's problem, not the renter's
If a provider fails to acknowledge or execute a command, it's logged as a system fault and routed to helpdesk — never framed as renter non-compliance, since there is no human renter.