Community OpenAPI document · agent-readyMaps GeolocationRouting Directionsoauth216 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Quote Lyft ride costs and ETAs, request and cancel rides, update destinations, list ride types, and retrieve receipts via the Lyft platform.
Use for: I need to quote the cost of a Lyft from JFK to midtown Manhattan, Get the pickup ETA for a Lyft at my current coordinates, Find available drivers near a latitude and longitude, Request a Lyft for a user from their saved pickup location
Not supported: Does not handle food delivery, scooter rentals, or driver-side dispatch - use for Lyft passenger ride quoting, requesting, updating, and receipt retrieval only.
The Lyft API exposes Lyft's ridesharing primitives - cost estimates, ETAs, available drivers nearby, ride request and lifecycle, ride types, profile, and a sandbox for simulating ride status transitions and primetime. The 16 endpoints cover the journey from quoting a ride through requesting, updating destination, rating, and pulling a receipt. Authentication uses OAuth 2.0 with two flows: client credentials for public endpoints (cost, ETA) and authorization code for user-scoped operations (rides, profile).
Install Jentic One Beta
Connect the Lyft to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Lyft, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Flyft.com%2Flyft" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Flyft.com%2Flyft" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Lyft API.
Generate cost estimates between two coordinates with /cost
Return available drivers nearby and pickup ETAs for a coordinate
Request a ride with POST /rides and cancel an active request with POST /rides/{id}/cancel
Update the destination of an in-progress ride with PUT /rides/{id}/destination
Rate the driver and add a tip after the ride with PUT /rides/{id}/rating
Fetch the receipt for a completed ride and list past rides on the user profile
Use the sandbox endpoints to simulate ride status transitions, ride types, and primetime
Use Cases
Patterns agents use Lyft API for, with concrete tasks.
★ In-app ride booking inside another product
Travel apps and concierge services embed Lyft ride booking by chaining /cost and /eta to quote the trip, POST /rides to request it, and PUT /rides/{id}/destination if the user changes their mind mid-trip. The user authentication OAuth flow grants the rides.request scope, and POST /rides/{id}/cancel covers cancellation. This avoids deep linking out to the Lyft consumer app for partner experiences.
Call GET /cost and GET /eta for the pickup and dropoff coordinates, then POST /rides to request the ride if the quote is accepted.
Sandbox-based simulation for QA
Engineering teams use the /sandbox endpoints to drive a fake Lyft trip through state transitions before integrating against the live API. PUT /sandbox/rides/{id} propagates a ride through statuses, /sandbox/primetime sets a preset surge percentage, and /sandbox/ridetypes preset the available types. This lets QA cover the full lifecycle without spending money on real rides.
PUT /sandbox/rides/{id} to advance a sandbox ride from 'pending' to 'arrived' so the integration UI can be tested end to end.
Receipt and history retrieval for expense tools
Expense tools and travel managers pull a user's past Lyft rides via GET /rides and the receipt for a specific ride via GET /rides/{id}/receipt to attach to expense reports. With the rides.read scope, this avoids manual screenshotting from the Lyft app and enables automated reconciliation.
List the last 10 rides via GET /rides and pull the receipt for each via GET /rides/{id}/receipt for the expense report.
Agent-driven ride orchestration via Jentic
An AI travel concierge needs to book and adjust Lyft rides without juggling two OAuth flows or memorising the sandbox vs production split. Jentic stores both the client-credentials and authorization-code tokens in your Jentic One instance, exposes each Lyft operation by intent, and lets the agent chain cost, ETA, request, and cancel calls.
Search Jentic for 'lyft cost estimate', execute it for the trip, then chain POST /rides to request the ride.
Key Endpoints
16 endpoints — the lyft api exposes lyft's ridesharing primitives - cost estimates, etas, available drivers nearby, ride request and lifecycle, ride types, profile, and a sandbox for simulating ride status transitions and primetime.
METHOD
PATH
DESCRIPTION
GET
/cost
Cost estimates for a trip
GET
/eta
Pickup ETAs
GET
/drivers
Available drivers nearby
POST
/rides
Request a Lyft
POST
/rides/{id}/cancel
Cancel an ongoing ride request
PUT
/rides/{id}/destination
Update the destination of a ride
GET
/rides/{id}/receipt
Get the receipt for a completed ride
GET
/cost
Cost estimates for a trip
GET
/eta
Pickup ETAs
GET
/drivers
Available drivers nearby
POST
/rides
Request a Lyft
POST
/rides/{id}/cancel
Cancel an ongoing ride request
PUT
/rides/{id}/destination
Update the destination of a ride
GET
/rides/{id}/receipt
Get the receipt for a completed ride
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
L
Lyft
- AI-Aware (A-)71/100
99
Foundational Compliance57
Developer Experience & Jentic Compatibility56
AI-Readiness & Agent Experience94
Agent Usability88
Security66
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
57
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
10%
Example Density
How richly the API is illustrated with examples.
70%
Example Validity
Percentage of examples that conform to their schemas.
48%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
56
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
74%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
52%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
88
Security
Trust, risk posture, and security compliance.
Grade: ASignals: 1
88%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
66
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
66%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Lyft API by hand means running its OAuth flow, keeping a bearer token fresh for public estimate calls versus user-scoped ride calls, and handling the two credential types across cost, ETA, and ride paths. Through Jentic you install once, import Lyft from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
You choose which Lyft operations the agent may call, so you can limit it to the ones it needs, such as cost estimates and pickup ETAs, and leave out actions like requesting or cancelling a ride unless you add them. The agent only reaches the operations in the set you allow.
Credential isolation
Your Lyft credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'Lyft cost estimate', 'request a Lyft', or 'cancel a ride', and Jentic returns the matching Lyft operation with its parameter schema so the agent calls the right endpoint directly.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Lyft API through Jentic.
What authentication does the Lyft API use?
The Lyft API uses OAuth 2.0 with two flows: client credentials at https://api.lyft.com/oauth/token for public endpoints (cost, ETA) under the 'public' scope, and authorization code for user operations under 'profile', 'rides.read', and 'rides.request'. Through Jentic, the Lyft client secret is stored in your Jentic One instance and tokens are exchanged automatically per call.
Can I request a ride and update its destination mid-trip?
Yes. POST /rides creates the ride request and returns a ride ID. While the ride is active you can PUT /rides/{id}/destination to change the destination, POST /rides/{id}/cancel to cancel it, or wait for completion and call GET /rides/{id}/receipt for the final receipt.
What are the rate limits for the Lyft API?
Specific rate limits are not declared in this OpenAPI spec. Plan for per-application limits set in the Lyft developer portal - design clients to back off on 429 responses and avoid polling /eta or /drivers more aggressively than once per few seconds per coordinate.
How do I get a cost estimate through Jentic?
Search Jentic for 'lyft cost estimate', load GET /cost, and execute it with the start and end latitude/longitude. Jentic exchanges the client-credentials token automatically and returns the estimated price range.
Is the Lyft sandbox useful before going live?
Yes. The /sandbox endpoints (PUT /sandbox/rides/{id}, /sandbox/primetime, /sandbox/ridetypes) let you advance a fake ride through statuses, set a preset primetime percentage, and preset ride types, so you can test the full integration without spending money.
Can I limit what my agent is allowed to do with the Lyft API?
Yes. Jentic One is self-hosted by you, so your own rules decide which Lyft operations and credentials the agent may use. You can allow read-only calls like GET /cost and GET /eta while withholding actions such as POST /rides, POST /rides/{id}/cancel, and PUT /rides/{id}/destination unless you explicitly add them. The agent only ever reaches the operations in the set you permit.
GET STARTED