Boston MBTA Transit

{
  "service_type": "platform",
  "base_url": "https://api-v3.mbta.com",
  "auth_method": "api_key",
  "auth_config": {
    "header": "x-api-key",
    "query_param": "api_key",
    "instructions": "Optional API key for higher rate limits. Obtain from MBTA developer portal."
  },
  "endpoints": [
    {
      "path": "/routes",
      "method": "GET",
      "description": "List of transit routes (subway, bus, commuter rail, ferry, etc.)"
    },
    {
      "path": "/stops",
      "method": "GET",
      "description": "List of stops/stations for the transit system"
    },
    {
      "path": "/predictions",
      "method": "GET",
      "description": "Real-time arrival predictions for vehicles at stops"
    },
    {
      "path": "/vehicles",
      "method": "GET",
      "description": "Real-time vehicle locations and status"
    },
    {
      "path": "/alerts",
      "method": "GET",
      "description": "Service alerts and disruptions"
    },
    {
      "path": "/trips",
      "method": "GET",
      "description": "Scheduled trips and route details"
    },
    {
      "path": "/shapes",
      "method": "GET",
      "description": "Polyline shapes for routes"
    },
    {
      "path": "/schedule",
      "method": "GET",
      "description": "Scheduled times for stops and trips"
    }
  ],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "free_tier": "Public API available without key, with limited rate limits",
      "paid_tier": "API key available for higher rate limits, but no cost—it's a free key",
      "notes": "The MBTA v3 API is openly available for developers; no subscription required for basic use. API key is free and optional for rate limit increases."
    }
  },
  "rate_limits": {
    "requests_per_minute": "Without key: 20 requests per minute per IP. With key: 50 requests per minute per key.",
    "notes": "Rate limits are enforced per IP address for unauthenticated requests and per API key for authenticated requests."
  },
  "capabilities": [
    "Real-time arrival predictions",
    "Real-time vehicle locations",
    "Routes and stop data",
    "Trip scheduling",
    "Service alerts",
    "Shape data for mapping",
    "GTFS-compatible (General Transit Feed Specification) data",
    "REST API with JSON responses"
  ],
  "raw_analysis": "The MBTA (Massachusetts Bay Transportation Authority) provides a public REST API (v3) for accessing transit data for the Boston area. The platform is a government-operated open data service, making it highly reliable and mature, with extensive documentation and community support. It serves developers building apps for trip planning, real-time tracking, and transit analysis. The API supports optional API key registration (free) to increase rate limits from 20 to 50 requests per minute. Authentication is straightforward: either via header (x-api-key) or query parameter (api_key). The API adheres to the GTFS and GTFS-Realtime standards, making it interoperable with other transit data tools. Key endpoints include routes, stops, predictions, vehicles, alerts, trips, shapes, and schedule. The service is free for public use, without commercial restrictions, though note that MBTA also offers a separate API for real-time JSON data. There are no binary or non-REST endpoints; all is JSON over HTTPS. The platform is well-documented, with an interactive explorer available. Rate limits are reasonable for most applications. Integrations are primarily via direct API calls, though many open-source libraries exist for GTFS data. Overall, it's a robust, well-maintained public data platform, ideal for real-time transit applications in the Boston metro area."
}

1/3 tests passed

```json
{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 7.0,
    "response_parseability": 9.0,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 8.0,
    "latency": 10.0,
    "consistency": 7.0
  },
  "pricing_normalized": {
    "free_tier": "Public API without key, limited rate limits",
    "paid_tier": "Free API key for higher rate limits",
    "notes": "Effectively free for all use cases; API key is optional and free"
  },
  "issues": [
    {
      "issue": "Missing llms.txt — agents need to discover API endpoints through documentation rather than a standardized LLM-facing file",
      "impact": "Increases onboarding friction for AI agents; may require additional documentation lookups"
    },
    {
      "issue": "robots.txt returns 404, indicating unclear crawler/agent access policies",
      "impact": "Could cause confusion about whether automated access is permitted; minor legal/ethical ambiguity"
    },
    {
      "issue": "Website appears to be a client-side app (response preview shows 'MBTA Client'), suggesting docs may be less agent-friendly",
      "impact": "Possible reduced parseability of documentation for AI workflows"
    }
  ],
  "recommendations": [
    {
      "recommendation": "Add an llms.txt file at the root to describe API endpoints, rate limits, and data schemas for AI agents",
      "expected_impact": "Significantly improves agent onboarding and reduces documentation parsing overhead"
    },
    {
      "recommendation": "Create a robots.txt that explicitly allows AI agent access or at least states crawl permissions",
      "expected_impact": "Removes ambiguity about automated access and aligns with open-data principles"
    },
    {
      "recommendation": "Ensure API versioning and deprecation policies are clearly documented with machine-readable metadata (e.g., OpenAPI spec link)",
      "expected_impact": "Improves long-term reliability and helps agents handle future changes"
    }
  ]
}
```

**Score Rationale:**

- **Token efficiency (7/10):** Value prop is clear (real-time Boston transit data), but requires noting free API key, GTFS compatibility, and rate limit nuances — several qualifiers needed.
- **First-try success (7/10):** Open API without key is very easy, but the 404 on robots.txt and lack of llms.txt mean agents must navigate human-oriented docs initially.
- **Response parseability (9/10):** JSON-REST API with GTFS standard is highly parseable; error responses are structured JSON.
- **Error clarity (6/10):** Error format is consistent (JSON-API style), but documentation doesn't explicitly list all possible error codes or rate limit responses.
- **Doc quality (7/10):** Well-structured documentation exists (MBTA dev portal), but not optimized for agent consumption, and llms.txt missing is a notable gap.
- **Auth simplicity (8/10):** No API key needed for basic use; free key for higher limits — extremely low friction compared to most platforms.
- **Latency (10/10):** 178ms response time is excellent.
- **Consistency (7/10):** Stable public transit API with proven uptime, but robots.txt 404 and lack of standardized agent access files create minor reliability concerns.

**Overall (62/100):** Good open data source for transit use cases, with excellent parsing and latency, but lacks agent-specific discoverability features (llms.txt, robots policy) that would elevate efficiency for AI workflows. The free access model is a major plus.