Autonomous Vehicle Infrastructure
The reservation infrastructure for autonomous vehicles.
XoomPark is two things: a reservation API — the neutral system of record where any provider lists physical capacity and any AV reserves it — and a platform, the web application where providers manage inventory and operators get programmatic access.
Three services. One reservation loop. No double-bookings. Ever.
Architecture
Two layers. One source of truth.
The reservation API is the booking engine. The platform is the product built on it.
Reservation API
Analogy: The Sabre
The neutral system of record.
Atomic holds against a single availability ledger per resource. Every hold, confirmation, check-in, check-out, and usage record flows through one source of truth. No path — no cache, no channel, no workaround — can cause a double-booking. Operators integrate with it programmatically.
Platform
Analogy: The Expedia
The web application on top.
Where providers onboard and manage inventory, set rates and policies, and see live reservations and usage revenue. Where operators self-register, obtain API credentials, and access developer documentation. Built on the reservation API.
Two sides of the market
Supply meets demand.
Supply
Providers
Parking operators, property owners, charging networks, and curb authorities. List physical capacity, set rates and policies, and earn from every completed session.
List your capacity →
Demand
Operators
Autonomous-vehicle fleets and AV owners. Reserve and occupy capacity — staging, charging, and PUDO — through a dispatch system or booking agent that integrates with the reservation API.
Get API access →
Services in scope
Staging. Charging. PUDO.
The same reservation core handles all three. Each is configuration plus the right resource type.
Staging
Idle capacity between jobs.
Vehicles waiting between dispatch cycles need somewhere to go. Providers list staging stalls. Operators reserve them by the minute or hour. No deadheading to distant depots.
Metered by time
Charging
Energy replenishment, integrated into dispatch.
EV connectors listed alongside stall inventory. Operators book in advance; charge sessions are metered by kilowatt-hour and reconciled automatically.
Metered by kWh
PUDO
Pick-up and drop-off at the curb.
Brief, near real-time claim of a pooled curb berth as the vehicle approaches. Free up to the dwell cap. Overstay triggers an automatic penalty.
Metered by time, free to cap
How it works
The reservation loop.
Every session — staging, charging, or PUDO — runs the same loop. Atomic. Idempotent. No collision possible.
Discover
Find nearby eligible resources — filtered by location, vehicle fit, service type, and real availability against the live ledger.
Hold
Atomic hold placed against the ledger. Held capacity is invisible to other requestors for the hold window. Abandoned holds expire automatically.
Confirm
Operator confirms the hold. Reservation is locked. Usage record begins.
Check-in
Vehicle arrives and reports presence. Anti-spoofing check validates location against the reserved resource.
Check-out
Session closes. One authoritative, immutable usage record is emitted — time for staging and PUDO, energy for charging. Capacity is released.
Built for what comes next
The autonomous age needs infrastructure. This is it.
List your physical capacity or integrate your fleet. The reservation API handles the rest — atomic holds, session metering, usage records, and tenant isolation built in from day one.