Agent-ready OpenAPI document · curated by JenticMaps GeolocationRide Hailingoauth216 EndpointsREST
Know of an official OpenAPI document?
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%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%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.
Estimate ride cost between points
Get pickup ETAs and list available drivers
List available ride types
Request and cancel a ride
Update a ride's destination and submit a rating
Read ride history and receipts
Use Cases
Patterns agents use Lyft API for, with concrete tasks.
★ Quote a trip before booking
Riders want to know cost and wait time before committing. The Lyft API returns cost estimates between two points and pickup ETAs for a location, so an application can present a quote up front. Ride types let the caller compare options such as standard and shared.
Return the cost estimate and pickup ETA for the requested trip.
Request and track a ride
Booking a trip means requesting a ride and following it to completion. The Lyft API requests a ride to a destination, reports the ride detail, and can cancel it, letting an application manage a trip end to end. Receipts and ride history record what happened after the trip.
Request a ride to the destination and return the ride detail.
Rehearse ride flows in sandbox
Testing a ride integration needs controllable ride states. The Lyft API exposes sandbox operations to preset ride types, prime-time pricing, and propagate a ride through its statuses, so a team can validate handling without real trips. This lets an integration cover cancellation and completion paths safely.
Advance a sandbox ride through its statuses to test the integration.
Key Endpoints
16 endpoints — jentic publishes the only available openapi specification for lyft, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/cost
Estimate the cost of a ride between points.
GET
/eta
Get pickup ETAs for a location.
POST
/rides
Request a ride.
GET
/rides/{id}
Get the detail of a given ride.
POST
/rides/{id}/cancel
Cancel an ongoing ride request.
GET
/ridetypes
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Lyft yourself means managing an OAuth2 client-credentials or authorization-code token, quoting trips, and tracking ride states. With Jentic you install once, import Lyft from the API Directory, and store the credential a single time.
Permission scoping
Jentic lets you grant your agent only the operations it needs, such as estimating costs and requesting rides without sandbox controls, and enforces that on every call.
Credential isolation
Your Lyft OAuth2 credential is stored once, encrypted, by your own Jentic One instance. It is injected when a call runs and never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents find Lyft through Jentic's intent search, matching a request like 'book a ride to the airport' to the right operation without hardcoded endpoints.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Lyft API through Jentic.
What can an AI agent do with the Lyft API through Jentic?
An agent can estimate ride cost and ETA, list ride types, request and cancel rides, and read ride history and receipts. Through Jentic the agent matches an intent to the right operation and runs it with your credential injected at execution time.
How do I authenticate with the Lyft API?
Lyft uses OAuth2. Public endpoints such as cost, ETA, and ride types use a client-credentials token via Client Authentication, while user-scoped endpoints such as profile and rides use an authorization-code token via User Authentication. You store the credential once in your Jentic One instance, and it is added to each call at run time.
Does the Lyft API include a sandbox for testing?
Yes. The API exposes sandbox operations to preset ride types, prime-time pricing, and ride statuses, so an integration can rehearse ride flows without real trips. This helps validate cancellation and completion handling before going live.
Where does the Lyft OpenAPI specification come from?
Jentic maintains this OpenAPI specification for Lyft and keeps it validated and agent-ready. It is the specification used to run the API through Jentic, and it is checked against the operations the API exposes.
Can I control which Lyft operations my agent can call?
Yes. Jentic lets you allow only the operations your agent needs, for example estimating costs and requesting rides while withholding sandbox controls. Your Jentic One instance enforces that boundary on every call and keeps the credential outside the agent's context.
GET STARTED