About XoomPark
The reservation infrastructure for autonomous vehicles.
Autonomous vehicles are operating at scale. What does not exist yet — at any scale — is a neutral, reliable system where any provider can list physical AV capacity and any operator can reserve it without collisions, without bespoke integrations, and without moving money through the core.
XoomPark is that system.
Architecture
Two layers. Built in sequence. Designed together.
Reservation API — The Sabre
The neutral system of record.
Holds, confirmations, check-ins, check-outs, and usage records all flow through one authoritative booking engine. Every provider's capacity is listed on the same ledger. Every operator's reservation is an atomic hold against it. No reservation path can double-book.
Operators integrate with it programmatically. It is operator-agnostic and provider-agnostic by design. The analogy is Sabre — the neutral GDS that airlines and travel agents both connected to.
Platform — The Expedia
The web application on top.
The platform is where providers onboard — creating sites, resources, and offerings through a guided UI without touching the API directly. It is where operators self-register, receive API credentials, and access developer documentation.
Provider dashboards show live reservations, occupancy, and revenue. Operator dashboards show API usage and session history. Everything in the platform is a read or write against the reservation API underneath. The analogy is Expedia — a product built on top of the GDS.
Why this matters
The infrastructure gap is real. It is open now.
AVs need more than roads.
Autonomous vehicles can navigate public roads. What they cannot do — today — is reliably reserve a staging stall between jobs, book a charger in advance, or claim a PUDO berth at a commercial property without a bespoke integration. XoomPark is that infrastructure.
The curb is not enough.
Public curb space is congested, regulated, and inconsistent. The real demand for AV staging, charging, and pick-up and drop-off is in private property — parking lots, garages, hotel driveways, office campuses, charging stations. That capacity is unlisted and unreserved today.
There is no standard. We are the standard.
Every property has different rules. Every operator has different integration requirements. Without a neutral system of record, every provider-operator relationship requires a bespoke negotiation. XoomPark is the single integration point — one API for every operator, one platform for every provider.
How we build
Engineering principles, not aspirations.
One source of truth. No exceptions.
The reservation API is the single availability ledger for every resource on the network. Every hold is atomic. No reservation path, channel, or cache can cause a double-booking — the constraint is enforced at the infrastructure layer, not by convention.
The platform serves both sides equally.
Providers manage inventory and see their usage through the platform UI. Operators self-register and get API credentials through the same platform. Neither side is treated as primary. The platform is neutral infrastructure.
Money never touches the core.
The reservation API records the form of payment and emits usage records. It does not store card data or move money. Payment execution is external to the core by design — a deliberate boundary, not a gap.
Correctness over convenience.
Idempotent writes. Anti-spoofing check-in. Hold expiry and no-show handling. Immutable usage records. Tenant isolation. These are not features — they are invariants. The system is built around them.
The infrastructure gap is open. Come help close it.
If you have physical capacity or a fleet that needs it, the platform is ready.