Lyft

Lyft is a transportation network company operating ride-hailing, bikeshare, scooter-share and related mobility services across the United States and Canada. Its API surface has two halves that behave very differently. The ride-hailing developer program — the Rides and Concierge APIs on api.lyft.com, used for patient transport, employee transit and customer-service ride booking — is gated: www.lyft.com/developers redirects to a sign-in, access is granted through a Lyft Business relationship, and the old documentation host developer.lyft.com no longer resolves. The micromobility side is wide open: Lyft serves live GBFS feeds for eight bikeshare and scooter systems (Citi Bike, Divvy, Bay Wheels, Bluebikes, Capital Bikeshare, Biketown, and its own DC and Denver fleets) anonymously from gbfs.lyft.com, alongside a public RFC 8414 OAuth metadata document that publishes the platform's full 47-scope vocabulary.

Lyft publishes 8 APIs on the APIs.io network, including Concierge Rides API, Cost Estimates API, Drivers API, and 5 more. Tagged areas include Transportation, Mobility, Ride Hailing, Micromobility, and Bike Share.

The Lyft catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.

Lyft’s developer surface includes authentication, engineering blog, documentation, getting-started guide, support, signup flow, and 32 more developer resources.

🌐 Visit website 📡 Source on GitHub

48.7/100 developing ▬ flat Agent 36/100 agent ready Front door AI 1/6 silent Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0

AccessFreemiumSelf serve⚡ Free to try

2 APIs

Transportation Mobility Ride Hailing Micromobility Bike ShareScootersGBFS Logistics Travel

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Mobility Services Operations Management

BC-3490

Concierge RidesCost EstimatesRide TypesRides

GET /concierge/rides POST /concierge/rides GET /concierge/rides/{id} POST /concierge/rides/{id}/cancel

Kin Score

Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0

Composite quality — 48.7/100 · developing

Contract Quality 11.6 / 19

Developer Ergonomics 8.8 / 15

Access Clarity 4.7 / 15

Operational Transparency 1.5 / 10

Contract Governance 2.5 / 9

Discoverability 5.5 / 8

Regulatory Posture 5.4 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 36/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/lyft: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 8

Individual APIs this provider publishes, each with its own machine-readable definition.

lyft Concierge Rides API

Endpoints for creating, scheduling, tracking, and managing rides on behalf of passengers who may not have a Lyft account.

lyft Cost Estimates API

Endpoints for estimating ride costs for concierge bookings.

lyft Drivers API

Endpoints for checking the availability and proximity of nearby Lyft drivers.

lyft ETA API

Endpoints for estimating the time for the nearest driver to reach a specified pickup location.

lyft Profile API

Endpoints for retrieving profile information for the authenticated Lyft user.

lyft Ride Types API

Endpoints for retrieving available ride types for concierge bookings.

lyft Rides API

Endpoints for requesting, tracking, canceling, and managing Lyft rides on behalf of an authenticated user.

Lyft Micromobility GBFS Feeds

Live General Bikeshare Feed Specification (GBFS) feeds for the eight bikeshare and scooter systems Lyft operates — Citi Bike, Divvy, Bay Wheels, Bluebikes, Capital Bikeshare, Bi...

Scroll for all 8

Open Collections 10

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Lyft Concierge Concierge Rides API

OPEN COLLECTION

Lyft Concierge API

OPEN COLLECTION

Lyft Concierge Concierge Rides Cost Estimates API

OPEN COLLECTION

Lyft Concierge Concierge Rides Drivers API

OPEN COLLECTION

Lyft Concierge Concierge Rides ETA API

OPEN COLLECTION

Lyft Concierge Concierge Rides Profile API

OPEN COLLECTION

Lyft Ride-Sharing API

OPEN COLLECTION

Lyft Concierge Concierge Rides Ride Types API

OPEN COLLECTION

Lyft Concierge Concierge Rides API

OPEN COLLECTION

Scroll for all 10

Pricing Plans 1

Published pricing tiers and plan structures.

Lyft Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Lyft Rate Limits

0 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Lyft Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Lyft Webhooks

ASYNCAPI

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Lyft Context

0 classes · 9 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Lyft API Rules

6 rules · 5 warnings 1 info

SPECTRAL

JSON Schema 3

Standalone JSON Schema definitions for this provider's data models.

Lyft Cost Estimate

9 properties

JSON SCHEMA

Lyft Ride

16 properties

JSON SCHEMA

Lyft Ride Type

5 properties

JSON SCHEMA

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Lyft Authentication

apiKey/http · 2 schemes

SECURITY

Lyft Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Lyft Vulnerability Disclosure

Hackerone

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Lyft Scopes

47 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Lyft Agentic Access

19 operations · 6 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 4

Reference material describing how the API behaves

JSONSchema

JSONSchema

JSONSchema

Documentation

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

WellKnown

WellKnown

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

JSONLD

Conformance

ErrorCatalog

Lifecycle

Conventions

DataModel

Webhooks

Scroll for all 7

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 5

Authentication, authorization, and security posture

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

Authentication

OAuthScopes

Security

Operate 2

Status, limits, changes, and where to get help

RateLimits

RateLimits

Support

Support

Commercial 4

Pricing, plans, and the legal terms of use

Plans

FinOps

TermsOfService

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

LinkedIn

Blog

Blog

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

GBFS

GBFS

Source (apis.yml)

name: Lyft
aid: lyft
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: true
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  generated: '2026-08-28'
  method: derived
specificationVersion: '0.23'
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  label: Freemium · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/lyft.png
url: https://raw.githubusercontent.com/api-evangelist/lyft/refs/heads/main/apis.yml
apis:
- aid: lyft:lyft-concierge-rides-api
  name: lyft Concierge Rides API
  description: Endpoints for creating, scheduling, tracking, and managing rides on behalf of passengers who may not have a
    Lyft account.
  humanURL: https://www.lyft.com/developers
  baseURL: https://api.lyft.com
  tags:
  - Concierge Rides
  properties:
  - type: OpenAPI
    url: openapi/lyft-concierge-rides-api-openapi.yml
  - type: Documentation
    url: https://www.lyft.com/developers/products/concierge-api
  - type: Documentation
    url: https://help.lyft.com/business/hc/en-us/articles/360001599667-Concierge-API-overview
    name: Concierge API overview (public help centre)
  - type: Overlay
    url: overlays/lyft-concierge-rides-api-overlay.yaml
- aid: lyft:lyft-cost-estimates-api
  name: lyft Cost Estimates API
  description: Endpoints for estimating ride costs for concierge bookings.
  humanURL: https://www.lyft.com/developers
  baseURL: https://api.lyft.com
  tags:
  - Cost Estimates
  properties:
  - type: OpenAPI
    url: openapi/lyft-cost-estimates-api-openapi.yml
  - type: Documentation
    url: https://www.lyft.com/developers/products/concierge-api
  - type: Documentation
    url: https://help.lyft.com/business/hc/en-us/articles/360001599667-Concierge-API-overview
    name: Concierge API overview (public help centre)
  - type: Overlay
    url: overlays/lyft-cost-estimates-api-overlay.yaml
- aid: lyft:lyft-drivers-api
  name: lyft Drivers API
  description: Endpoints for checking the availability and proximity of nearby Lyft drivers.
  humanURL: https://www.lyft.com/developers
  baseURL: https://api.lyft.com
  tags:
  - Drivers
  properties:
  - type: OpenAPI
    url: openapi/lyft-drivers-api-openapi.yml
  - type: Documentation
    url: https://www.lyft.com/developers/products/concierge-api
  - type: Documentation
    url: https://help.lyft.com/business/hc/en-us/articles/360001599667-Concierge-API-overview
    name: Concierge API overview (public help centre)
  - type: Overlay
    url: overlays/lyft-drivers-api-overlay.yaml
- aid: lyft:lyft-eta-api
  name: lyft ETA API
  description: Endpoints for estimating the time for the nearest driver to reach a specified pickup location.
  humanURL: https://www.lyft.com/developers
  baseURL: https://api.lyft.com
  tags:
  - ETA
  properties:
  - type: OpenAPI
    url: openapi/lyft-eta-api-openapi.yml
  - type: Documentation
    url: https://www.lyft.com/developers/products/concierge-api
  - type: Documentation
    url: https://help.lyft.com/business/hc/en-us/articles/360001599667-Concierge-API-overview
    name: Concierge API overview (public help centre)
  - type: Overlay
    url: overlays/lyft-eta-api-overlay.yaml
- aid: lyft:lyft-profile-api
  name: lyft Profile API
  description: Endpoints for retrieving profile information for the authenticated Lyft user.
  humanURL: https://www.lyft.com/developers
  baseURL: https://api.lyft.com
  tags:
  - Profiles
  tags_raw:
  - Profile
  properties:
  - type: OpenAPI
    url: openapi/lyft-profile-api-openapi.yml
  - type: Documentation
    url: https://www.lyft.com/developers/products/concierge-api
  - type: Documentation
    url: https://help.lyft.com/business/hc/en-us/articles/360001599667-Concierge-API-overview
    name: Concierge API overview (public help centre)
  - type: Overlay
    url: overlays/lyft-profile-api-overlay.yaml
- aid: lyft:lyft-ride-types-api
  name: lyft Ride Types API
  description: Endpoints for retrieving available ride types for concierge bookings.
  humanURL: https://www.lyft.com/developers
  baseURL: https://api.lyft.com
  tags:
  - Ride Types
  properties:
  - type: OpenAPI
    url: openapi/lyft-ride-types-api-openapi.yml
  - type: Documentation
    url: https://www.lyft.com/developers/products/concierge-api
  - type: Documentation
    url: https://help.lyft.com/business/hc/en-us/articles/360001599667-Concierge-API-overview
    name: Concierge API overview (public help centre)
  - type: Overlay
    url: overlays/lyft-ride-types-api-overlay.yaml
- aid: lyft:lyft-rides-api
  name: lyft Rides API
  description: Endpoints for requesting, tracking, canceling, and managing Lyft rides on behalf of an authenticated user.
  humanURL: https://www.lyft.com/developers
  baseURL: https://api.lyft.com
  tags:
  - Rides
  properties:
  - type: OpenAPI
    url: openapi/lyft-rides-api-openapi.yml
  - type: Documentation
    url: https://www.lyft.com/developers/products/concierge-api
  - type: Documentation
    url: https://help.lyft.com/business/hc/en-us/articles/360001599667-Concierge-API-overview
    name: Concierge API overview (public help centre)
  - type: Overlay
    url: overlays/lyft-rides-api-overlay.yaml
- aid: lyft:lyft-gbfs-feeds
  name: Lyft Micromobility GBFS Feeds
  description: Live General Bikeshare Feed Specification (GBFS) feeds for the eight bikeshare and scooter systems Lyft operates
    — Citi Bike, Divvy, Bay Wheels, Bluebikes, Capital Bikeshare, Biketown, Lyft Scooters DC and Lyft Denver. Station inventory
    and status, free-floating vehicles, vehicle types, service alerts, system hours and regions, and machine-readable consumer
    ride pricing, all served anonymously from Lyft's own host with no key and no account. 96 feed endpoints across 8 systems,
    GBFS 1.1 and 2.3.
  humanURL: https://www.lyft.com/bikes
  baseURL: https://gbfs.lyft.com
  tags:
  - GBFS
  - Micromobility
  - Bike Share
  - Scooters
  - Stations
  - Open Data
  tags_raw:
  - GBFS
  - Micromobility
  - Bikeshare
  - Scooters
  - Stations
  - Open Data
  properties:
  - type: GBFS
    url: gbfs/lyft-gbfs.yml
    name: Lyft GBFS feed index (8 systems, probed 2026-09-17)
  - type: GBFS
    url: https://gbfs.lyft.com/gbfs/2.3/dca/gbfs.json
    name: GBFS auto-discovery — Lyft Scooters, Washington DC
  - type: GBFS
    url: https://gbfs.citibikenyc.com/gbfs/2.3/gbfs.json
    name: GBFS auto-discovery — Citi Bike (feeds served from gbfs.lyft.com)
  - type: Documentation
    url: https://github.com/MobilityData/gbfs/blob/master/gbfs.md
    name: GBFS specification
  - type: AgentSkill
    url: skills/lyft-read-micromobility-feeds.md
common:
- type: VulnerabilityDisclosure
  url: security/lyft-vulnerability-disclosure.yml
- type: Website
  url: https://lyft.com
- type: CapabilityMap
  url: capabilities/lyft-capability-edges.yml
  name: lyft Business Capability Map
- type: AgenticAccess
  url: agentic-access/lyft-agentic-access.yml
- type: DomainSecurity
  url: security/lyft-domain-security.yml
- type: Authentication
  url: authentication/lyft-authentication.yml
- type: GitHubOrganization
  url: https://github.com/lyft
- type: LinkedIn
  url: https://www.linkedin.com/company/lyft
- type: JSONLD
  url: json-ld/lyft-context.jsonld
- type: JSONSchema
  url: json-schema/lyft-ride-schema.json
- type: JSONSchema
  url: json-schema/lyft-ride-type-schema.json
- type: JSONSchema
  url: json-schema/lyft-cost-estimate-schema.json
- url: https://www.lyft.com/blog
  type: Blog
- type: WellKnown
  url: well-known/lyft-well-known.yml
- type: OAuthScopes
  url: scopes/lyft-scopes.yml
- type: Packages
  url: packages/lyft-packages.yml
- type: SDKs
  url: packages/lyft-packages.yml
  name: Four first-party SDKs (Node, Android, iOS, Go) — all dormant
- type: Conformance
  url: conformance/lyft-conformance.yml
- type: ErrorCatalog
  url: errors/lyft-problem-types.yml
- type: Lifecycle
  url: lifecycle/lyft-lifecycle.yml
- type: Conventions
  url: conventions/lyft-conventions.yml
- type: DataModel
  url: data-model/lyft-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/lyft-mcp.yml
  name: Derived candidate — Lyft ships no reachable MCP server
- type: Webhooks
  url: asyncapi/lyft-webhooks.yml
  name: Subscription scopes published; no event catalogue
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/lyft-llms.txt
- type: Plans
  url: plans/lyft-plans-pricing.yml
- type: RateLimits
  url: rate-limits/lyft-rate-limits.yml
- type: FinOps
  url: finops/lyft-finops.yml
- type: GBFS
  url: gbfs/lyft-gbfs.yml
  name: 8 systems, 96 anonymous feed endpoints
- type: Security
  url: https://www.lyft.com/security
- type: DeveloperPortal
  url: https://www.lyft.com/developers
  name: Requires sign-in
- type: Documentation
  url: https://help.lyft.com/business/hc/en-us/articles/360001599667-Concierge-API-overview
  name: Concierge API overview (public help centre)
- type: GettingStarted
  url: https://help.lyft.com/business/hc/en-us/articles/8587470351891-Managing-your-API-client-and-program-connections
  name: Managing your API client and program connections
- type: Support
  url: https://help.lyft.com/hc/en-us
- type: TermsOfService
  url: https://www.lyft.com/terms
- type: PrivacyPolicy
  url: https://www.lyft.com/privacy
- type: SignUp
  url: https://www.lyft.com/signup
modified: '2026-09-17'
description: 'Lyft is a transportation network company operating ride-hailing, bikeshare, scooter-share and related mobility
  services across the United States and Canada. Its API surface has two halves that behave very differently. The ride-hailing
  developer program — the Rides and Concierge APIs on api.lyft.com, used for patient transport, employee transit and customer-service
  ride booking — is gated: www.lyft.com/developers redirects to a sign-in, access is granted through a Lyft Business relationship,
  and the old documentation host developer.lyft.com no longer resolves. The micromobility side is wide open: Lyft serves live
  GBFS feeds for eight bikeshare and scooter systems (Citi Bike, Divvy, Bay Wheels, Bluebikes, Capital Bikeshare, Biketown,
  and its own DC and Denver fleets) anonymously from gbfs.lyft.com, alongside a public RFC 8414 OAuth metadata document that
  publishes the platform''s full 47-scope vocabulary.'
tags:
- Transportation
- Mobility
- Ride Hailing
- Micromobility
- Bike Share
- Scooters
- GBFS
- Logistics
- Travel
tags_raw:
- Transportation
- Mobility
- Ride Hailing
- Micromobility
- Bikeshare
- Scooters
- GBFS
- Logistics
- Travel
created: '2026-05-03'
maintainers:
- FN: API Evangelist
  email: info@apievangelist.com
  url: https://apievangelist.com
x-enrichment:
  date: '2026-09-17'
  status: enriched
  artifacts_added: 41
  pass: local-v3
x-coverage:
  state: covered
  reason: covered
  detail: 'The ride-hailing developer portal is sign-in gated and its old docs host is gone, but contract discovery still
    landed two real first-party surfaces: the RFC 8414 OAuth metadata on api.lyft.com and eight live GBFS feed systems on
    gbfs.lyft.com.'
  evidence:
  - url: https://api.lyft.com/.well-known/oauth-authorization-server
    status: 200
  - url: https://gbfs.lyft.com/gbfs/2.3/dca/gbfs.json
    status: 200
  - url: https://www.lyft.com/developers
    status: 302
  - url: https://developer.lyft.com/docs
    status: 0
  checked: '2026-09-17'

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/lyft"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/lyft/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/lyft/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.