Obtain Uber Direct sandbox credentials from the Uber Developer Dashboard.
Create a delivery in the sandbox environment; include the test_specifications attribute in the CreateDelivery request body to trigger Robocourier instead of a real courier.
Robocourier will automatically progress the delivery through status stages (courier_assigned, en_route_to_pickup, pickup_complete, en_route_to_dropoff, delivered) and fire corresponding webhook events.
Configure your webhook endpoint to receive and process these sandbox events, validating your status-handling logic against each state transition.
Do not create multiple Robocourier deliveries from the same pickup address in rapid succession; wait at least 90 seconds between deployments to avoid batching conflicts.
Validate your webhook signature verification logic using the sandbox secret before moving to production.
Known gotchas
Robocourier does not support batching — if you create multiple deliveries quickly from the same address, they may be unexpectedly batched, producing inconsistent webhook sequences that do not reflect real production behavior.
Robocourier is exclusively a sandbox/testing tool; it has no effect in the production environment, so test flows must be re-validated with real couriers before launch.
Uber Direct quotes expire after 15 minutes; if your test flow involves quoting then creating, ensure your test harness creates the delivery before quote expiry or you will receive a stale-quote error.
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