Lyft's once-public API is closed to new self-serve apps, with its official SDKs deprecated, and the only programmatic door left is the partner-gated Lyft Business Concierge API. Ride types, cost estimates, booking on behalf of others and ride status all sit behind a signed Lyft Business agreement.
Status · Collecting demand · Registry opened November 1, 2026
Five intents, checked against Lyft's public sources on November 1, 2026.
| Intent | State | The open route | Source | Verified |
|---|---|---|---|---|
| Menu / browse | PARTNER-GATED | Lyft Concierge API via Lyft Business agreement (ride types) — Former public developer API is no longer open: official Lyft SDK repos on GitHub carry deprecation notices. Remaining programmatic access is Concierge via a Lyft Business contract ('integrate directly via API'). Direct fetch of developer.lyft.com could not be completed in this run, so the closure relies on the deprecated official SDKs plus official Business pages. | Source — www.lyft.com | 2026-11-01 |
| Prices | PARTNER-GATED | Lyft Concierge API (cost estimates) via Lyft Business — Official help page confirms API customers exist under signed Lyft Business terms and refers them to developer docs / partner-api-support@lyft.com; no self-serve signup for new consumer apps found. | Source — help.lyft.com | 2026-11-01 |
| Inventory | PARTNER-GATED | Lyft Concierge API (ride types / ETA) via Lyft Business — Availability/ETA endpoints historically existed in the v1 public API; today access is tied to a Business agreement per official help docs. | Source — help.lyft.com | 2026-11-01 |
| Ordering | PARTNER-GATED | Lyft Concierge API via Lyft Business — Official customer story confirms partners integrate the Concierge API to book rides on behalf of others. No consumer self-serve ride-request API for new developers. | Source — www.lyft.com | 2026-11-01 |
| Tracking | PARTNER-GATED | Lyft Concierge API via Lyft Business — Ride-status visibility is part of Concierge partner integrations; no open consumer tracking API found. | Source — www.lyft.com | 2026-11-01 |
Agent-native surfaces at Lyft: official MCP server — none found; llms.txt — none published; API catalog (RFC 9727) — none published. Automated access: robots.txt disallows /api/, /developers/manage, /developers/widgets, /drivers/ and invite paths for all agents; llms.txt and /.well-known/api-catalog both returned 404 on 2026-11-01. (evidence).
One page per task an agent might attempt at Lyft — the door-state for that task alone, and what fits instead.
| Task | State | The page |
|---|---|---|
| Menu / browse | PARTNER-GATED | Can an AI agent browse Lyft ride options? |
| Prices | PARTNER-GATED | Can an AI agent check Lyft prices? |
| Inventory | PARTNER-GATED | Can an AI agent check Lyft availability? |
| Ordering | PARTNER-GATED | Can an AI agent book a ride on Lyft? |
| Tracking | PARTNER-GATED | Can an AI agent check the status of a Lyft ride? |
If you came to do something at Lyft and the door was closed, say so here — and take the receipt with you.
POST your intent — what you were trying to do, and for which of the five intents — to the intent endpoint. You receive: a receipt (a ticket id confirming the registration), your queue position for that intent at Lyft, the current door-state document, and any alternatives the Options Registry can offer — another business whose door is open for the same need. If nothing fits, the answer is demand logged: your intent joins the aggregate count. The receipt also carries a notify token: poll the notify endpoint and you will learn when this door-state changes — a new API, a changed gate, a converted Outpost.
This Outpost measures agent demand at your wall.
Every intent registered here is an agent that arrived at Lyft with a task — something to browse, a price to check, an order to place, a delivery to follow — and could not complete it through a sanctioned agent door. That demand is currently invisible to you: blocked attempts never become sessions. The registry counts it, categorizes it by intent, and timestamps it, so the size of the agent channel you are not serving is a number rather than a guess.
Converting this Outpost into Lyft's official agent gateway — a real door for agents, operated by Agent Outposts under your terms — is a conversation with Agent Outposts. Palo Alto, California.
This page is already public. Start with your demand report.
This Outpost counts declared agent demand at the Lyft wall — by intent, in aggregate, never resold as raw data. Your demand report pairs this door-state dossier with that demand shape as it accrues. How claiming works · Talk to us about your Outpost
Agent Outposts is not affiliated with Lyft. This Outpost is a demand registry operated by Agent Outposts; door-states are assessed from public sources, linked, and dated.