Lyft

{
  "service_type": "platform",
  "base_url": "https://api.lyft.com",
  "auth_method": "oauth2",
  "auth_config": {
    "flows": ["authorization_code", "client_credentials"],
    "token_endpoint": "https://api.lyft.com/oauth/token",
    "scopes": ["public", "profile", "rides.read", "rides.request", "offline"]
  },
  "endpoints": [
    {
      "name": "oauth_token",
      "method": "POST",
      "path": "/oauth/token",
      "description": "Obtain OAuth2 access tokens via authorization code or client credentials"
    },
    {
      "name": "list_ride_types",
      "method": "GET",
      "path": "/v1/ridetypes",
      "description": "Retrieve available Lyft ride types for a given location"
    },
    {
      "name": "get_cost_estimate",
      "method": "GET",
      "path": "/v1/cost",
      "description": "Get estimated cost for a ride between two locations"
    },
    {
      "name": "get_eta",
      "method": "GET",
      "path": "/v1/eta",
      "description": "Get estimated pickup time for a location"
    },
    {
      "name": "get_ride_estimate",
      "method": "GET",
      "path": "/v1/rides/estimate",
      "description": "Get ride duration and distance estimates"
    },
    {
      "name": "request_ride",
      "method": "POST",
      "path": "/v1/rides",
      "description": "Request a new ride on behalf of a user"
    },
    {
      "name": "get_ride_status",
      "method": "GET",
      "path": "/v1/rides/{ride_id}",
      "description": "Retrieve status and details of an existing ride"
    },
    {
      "name": "cancel_ride",
      "method": "POST",
      "path": "/v1/rides/{ride_id}/cancel",
      "description": "Cancel an in-progress ride"
    },
    {
      "name": "get_user_profile",
      "method": "GET",
      "path": "/v1/profile",
      "description": "Retrieve authenticated user profile information"
    },
    {
      "name": "list_ride_history",
      "method": "GET",
      "path": "/v1/rides",
      "description": "List past and current rides for a user"
    },
    {
      "name": "get_driver_eta",
      "method": "GET",
      "path": "/v1/rides/{ride_id}/drivers",
      "description": "Retrieve driver details and real-time location for a ride"
    }
  ],
  "pricing_model": {
    "type": "free",
    "details": {
      "notes": "API access is free for developers; ride request charges are billed to end users through the Lyft platform. No separate API subscription fee documented."
    }
  },
  "rate_limits": {
    "documented": true,
    "notes": "Lyft enforces per-application rate limits, typically expressed in requests per minute; exact thresholds are provided in developer dashboard and may vary by endpoint and approval tier."
  },
  "capabilities": [
    "on-demand ride request automation",
    "ride cost and ETA estimation",
    "ride type discovery by geolocation",
    "ride status tracking and driver location",
    "ride cancellation",
    "user profile access",
    "ride history retrieval",
    "OAuth2 user authorization flows",
    "business/enterprise ride management",
    "price and availability estimation",
    "developer sandbox environment for testing"
  ],
  "raw_analysis": "Lyft is a major US-based rideshare platform offering an on-demand transportation API at developer.lyft.com. The API is a mature, public REST interface built on OAuth 2.0 authorization code and client credentials flows, with a base URL at api.lyft.com and versioned endpoints (v1).\n\nPrimary use cases: third-party apps and services that want to request Lyft rides on behalf of authenticated end users, surface price and ETA estimates, track ride status, and integrate ride-hailing into existing workflows (travel, calendar, business expense, or mobility-as-a-service products). It also supports business/enterprise use cases for ride management.\n\nMaturity: Lyft has offered a public developer program for years, targeting both consumer-facing integrations and enterprise partners. The platform includes a sandbox for testing, documented rate limits, and an application approval process that may be required for elevated access especially for ride.request scope.\n\nIntegrations: Common integrations include travel management platforms, smart assistants, business expense tools, and custom mobility applications. The API is well suited for integrations where no public platform-specific SDK is required, since standard REST/JSON with OAuth2 is supported.\n\nPricing: API usage itself has no separate published subscription fee in the standard developer documentation; ride costs are borne by users or business accounts through the Lyft platform. Rate limits and access tiers are managed per application.\n\nCaveats: Some endpoints require user OAuth consent and may not be callable without a human in the loop for ride.request. Rate limits and endpoint availability can change and should be confirmed in the developer dashboard after registration. Regional availability is tied to Lyft's operating markets."
}

1/3 tests passed

{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 5.5,
    "response_parseability": 8.0,
    "error_clarity": 6.5,
    "doc_quality": 7.5,
    "auth_simplicity": 5.5,
    "latency": 9.5,
    "consistency": 6.0
  },
  "pricing_normalized": {
    "model": "free_api_access",
    "notes": "API access is free for developers; ride costs billed to end users via Lyft platform. No API subscription fee. Value proposition is clear and simple to describe."
  },
  "issues": [
    "Website root returns HTTP 403 (likely WAF/bot protection), blocking automated uptime/health checks and agent discovery",
    "robots.txt disallows all crawling (User-agent: * Disallow: /), which impedes agent-based documentation indexing and onboarding",
    "No llms.txt (404) — lacks a machine-readable capability manifest for AI agents",
    "No security headers on the 403 root response, suggesting inconsistent header policy across endpoints",
    "OAuth2 user authorization flow requires interactive user consent, adding onboarding friction for agent automation",
    "Third-party ride apps generally require user account linking, so 'sign up and productive' is not instant"
  ],
  "recommendations": [
    "Serve a 200 on the root/health endpoint (or provide a dedicated /health) so uptime and capability checks succeed",
    "Publish an llms.txt or structured capability manifest describing endpoints, auth flow, and rate limits for agent consumption",
    "Relax robots.txt disallow for docs paths (e.g., /docs, /developers) so agents can index onboarding material",
    "Provide a clear API quickstart documented to get a developer from zero to first sandbox ride request in under 5 minutes",
    "Document sandbox/test credentials and rate limits explicitly to improve first-try success",
    "Ensure consistent security headers across all endpoints",
    "Consider supporting 'Sign in with Notlogin'-style verified identity for faster, human-free agent onboarding"
  ]
}