What the filing covers
An AI assistant can place a short hold on a parking space for a driver. The price is fixed when the hold is placed. The space count is checked in one atomic step, so two assistants cannot sell the last space twice. The driver gets a signed link. One tap confirms and pays exactly the held price; no account is needed. When a lot passes an occupancy threshold, the system sends assistants to the nearest lot that still has room. I filed this to connect an assistant's booking work with a driver's payment decision. A chatbot, voice assistant or booking agent can find a space and place the hold. The driver still decides whether to confirm and pay. That division matters: asking an assistant for parking is different from handing it control of the payment.
The hold fixes the price. The signed link carries the driver through confirmation and payment at that held price. The driver does not need an account to complete the transaction. I want the person receiving the link to have a clear choice: confirm the held space and pay the price already set.
The space count is checked in one atomic step. Checking capacity and securing a hold belong together. If assistants compete for the last space, the system cannot sell that space twice. This is a parking inventory problem as much as a booking problem.
Why it matters now
AI agents are starting to book travel and parking for people. I want lot owners to accept those requests without double-booking or changing the price after a hold. Drivers need to keep control of payment. A short hold and a signed confirmation link connect those needs.
A real-world example
A driver asks a voice assistant for parking. The assistant places a hold, and the driver receives a signed link. The price stays fixed while the driver moves from the assistant's conversation to payment. One tap confirms and pays that price.
Now consider another assistant requesting the same last space. The atomic space check prevents both requests from selling it. When a lot passes its occupancy threshold, assistants are sent to the nearest lot with room. The booking request can move to available inventory instead of continuing to send drivers toward a crowded lot.
Where it applies
This filing covers technology in Park Graph, Wins Parking's parking payment platform. I see the same practical question whether a request comes through a chatbot, a voice assistant or a booking agent: can the owner hold a real space at a fixed price while the driver makes the final payment decision?
Used in: Park Graph
Status
U.S. provisional patent application, filed October 25, 2026, application 64/183,842; Status: Patent pending; Sole inventor: Ross D. Blankenship; Assignee: Wins Parking, LLC.
Provisional applications establish a priority date; they are not examined.