Reserve a Quo ride
reserve_rideRequest a Quo captain reservation. No account or payment needed to request, a concierge confirms every ride by phone, text, or email before it's finalized, exactly like the public booking form. Nothing is charged by this call. If the guest has already linked a card with a spending cap (see get_payment_method), reserve_and_pay can also complete payment in the same call instead of just requesting.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>",
"phone": "<phone>",
"pickup": "<pickup>",
"when": "<when>"
},
"name": "reserve_ride"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Guest's full name | |
| when | Yes | Pickup date and time, ISO 8601 (e.g. 2026-12-04T14:30:00-05:00) | |
| No | |||
| hours | No | ||
| notes | No | ||
| phone | Yes | Guest's mobile number, required, the concierge confirms by phone/text. Any common format is fine (e.g. "305-555-0100", "(305) 555-0100"); non-digit characters other than a leading + are stripped server-side. | |
| stops | No | Ordered intermediate stops between pickup and dropoff within this one reservation (e.g. a hotel stop to grab a bag before continuing to the airport). Up to 3. Pricing here isn't distance-based, so each stop adds a flat surcharge to the fare, reflected in the confirmation. | |
| pickup | Yes | Pickup address, airport, or hotel | |
| dropoff | No | Destination, omit for an hourly/as-directed booking | |
| service | No | transfer | |
| vehicle | No | sedan | |
| flightNumber | No | For an airport pickup, Quo tracks the flight and the captain waits if it's delayed | |
| idempotency_key | No | Optional. A unique string for this reservation request (e.g. a UUID). If the call is retried with the same key, the original reservation is returned instead of creating a second ride. | |
| specialRequests | No | ||
| additionalRiders | No | Other named riders on this same booking, for a group/split-fare trip, the caller above stays the sole booking owner (auth, cancel rights, and payment all stay with them). Purely for the driver's manifest and, if a phone is given, that rider's own SMS ride updates. Not a separate payment, the organizer's card is still charged the full fare. |