Register an Uber for Business developer application and obtain OAuth 2.0 client credentials with the guests.trips scope; note the organization UUID from the U4B portal
Call the zones endpoint to retrieve specialized pickup locations such as airports or arenas before constructing a trip request
POST to /v1/guests/trips with rider name, phone, pickup and dropoff coordinates, and include the x-uber-organization-uuid header containing your organization UUID
Poll the trip status or subscribe to webhooks to track ride state transitions from accepted through completed
To test without live drivers, POST to /v1/guests/sandbox/run which provisions test riders and drivers that persist for 8 hours
Record the trip ID returned at creation and reconcile it against your expense or billing records once the ride completes
Known gotchas
The x-uber-organization-uuid header is mandatory for third-party app requests; omitting it causes authorization failures even with a valid bearer token
Guest trip estimates expire; re-fetch an estimate immediately before creating the trip to avoid price mismatch errors at booking time
Guest riders do not need an Uber account, so passenger identity verification relies entirely on the phone number you supply — validate format and reachability before submitting
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp