Contact Lyft Business to provision a Concierge API client; access to the full technical documentation requires a business agreement, so do not assume public sandbox access
Create a client application in the Lyft Developer Portal to obtain a Client ID, then connect it to a Lyft Business program in the portal
Authenticate with OAuth 2.0 using the client credentials flow; the token scope governs which ride types and billing programs are accessible
Submit a ride request specifying pickup and dropoff coordinates, passenger contact details, and the linked billing program identifier
Poll the ride endpoint or handle webhook callbacks to surface status updates to the dispatcher or embedding application
Retrieve completed-ride receipts and map them to internal cost centers or booking references for expense reconciliation
Known gotchas
Lyft Concierge API documentation is gated behind a Lyft Business relationship; attempting to use public developer portal credentials alone will not grant access to business dispatching endpoints
Ride type availability is market-dependent; always call the ride types availability endpoint for the specific origin coordinates before presenting options to a dispatcher
Cancellation fees apply after a driver has been matched; build a confirmation step before submission to prevent accidental charges
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