78
/100
prowl
Benchmarked Aug 21, 2026

Bay Area Rapid Transit

Stations and predicted arrivals for BART

saas platform_profile
Benchmark Your API

Score Breakdown

Latency 9/10
Parseability 9/10
Consistency 8/10
Auth Simplicity 8/10
Token Efficiency 8/10
First-Try Success 8/10
Documentation 7/10
Error Clarity 6/10

Benchmark Analysis Log

Full LLM thinking from the 4-phase benchmark pipeline.

Analyze
{
  "service_type": "platform",
  "base_url": "http://api.bart.gov",
  "auth_method": "api_key",
  "auth_config": {
    "key_parameter": "key",
    "header_prefix": "none",
    "notes": "API key required; obtained via registration at https://www.bart.gov/schedules/developers/api"
  },
  "endpoints": [
    {
      "path": "/api/etd.aspx",
      "method": "GET",
      "description": "Get estimated departure times for a station or all stations",
      "params": ["cmd", "orig", "key", "plat", "dir", "time", "date"]
    },
    {
      "path": "/api/stn.aspx",
      "method": "GET",
      "description": "Get station information including name, abbreviations, and GPS coordinates",
      "params": ["cmd", "key"]
    },
    {
      "path": "/api/route.aspx",
      "method": "GET",
      "description": "Get route information including route ID, name, and number",
      "params": ["cmd", "key", "route"]
    },
    {
      "path": "/api/bsa.aspx",
      "method": "GET",
      "description": "Get BART service advisories (alerts) affecting service",
      "params": ["cmd", "key"]
    },
    {
      "path": "/api/sched.aspx",
      "method": "GET",
      "description": "Get trip schedule information (origin, destination, date, time)",
      "params": ["cmd", "key", "orig", "dest", "date", "time", "trip", "a", "b"]
    },
    {
      "path": "/api/version.aspx",
      "method": "GET",
      "description": "Get current API version number and date",
      "params": ["cmd", "key"]
    },
    {
      "path": "/api/help.aspx",
      "method": "GET",
      "description": "Get API documentation and help for commands",
      "params": ["cmd", "key"]
    }
  ],
  "pricing_model": {
    "type": "free",
    "details": {
      "api_key": "free for developers",
      "rate_limit": "no explicit fee, but usage limited per BART's terms",
      "notes": "Data is public, no subscription required"
    }
  },
  "rate_limits": {
    "unknown": "No official documented rate limit, but BART may enforce limits to prevent abuse"
  },
  "capabilities": [
    "Real-time estimated departure times (ETDs) for BART stations",
    "Station information (name, abbreviation, coordinates, zone)",
    "Route information (route list, route details)",
    "Service advisories (BSA) for current disruptions",
    "Trip schedule planning (origin, destination, date, time)",
    "API version and help endpoints",
    "Support for multiple response formats (XML, JSON, JSONP via 'json' param)",
    "Data for all BART stations and lines",
    "Batch queries for all stations in a single ETD request"
  ],
  "raw_analysis": "This service is the official API for Bay Area Rapid Transit (BART), a public transportation agency in the San Francisco Bay Area. It provides real-time and scheduled data for stations, routes, and service alerts. The service is classified as a 'platform' because it exposes programmatic access to public transit data via an HTTP API, though it is not a typical 'collaboration tool' or 'dashboard'. It is free to use with a simple API key registration. The API is mature, having been available for many years (since around 2007), and is well-documented. It offers multiple response formats including XML, JSON, and JSONP. The primary audience is developers building transit apps, data analysts, and researchers. The service does not have a user interface as a primary offering but is purely data-oriented. The API is REST-like with a fixed set of commands (cmd parameter) and returns data in structured formats. It is actively maintained by BART's IT department. The api.bart.gov domain is the base for all API endpoints, and the service is free, with no subscription tiers or pricing. There is no official rate limit documented, but it is implied that usage should be reasonable and consistent with public transit data policies. Integration possibilities include mapping services (Google Maps, Transit apps), data visualization dashboards, and real-time notification systems. The service supports ETD (Estimated Departure Times) which are updated every few seconds, making it suitable for real-time applications. The API also provides station-to-station trip planning, which can be used for route optimization. Overall, it is a reliable, free public data service with a simple authentication model."
}
Execute

2/3 tests passed

TestEndpointStatusLatency
website_uptimeGET /200189ms
robots_txtGET /robots.txt200107ms
llms_txtGET /llms.txt40478ms
Interpret
```json
{
  "overall": 58,
  "dimensions": {
    "token_efficiency": 7.5,
    "first_try_success": 8.5,
    "response_parseability": 9.0,
    "error_clarity": 6.5,
    "doc_quality": 7.0,
    "auth_simplicity": 8.0,
    "latency": 9.0,
    "consistency": 7.5
  },
  "pricing_normalized": {
    "cost": "free",
    "rate_limit": "no explicit fee, used per BART terms",
    "details": "Public data API with free API key"
  },
  "issues": [
    {
      "severity": "medium",
      "description": "Missing llms.txt file (404) — agents cannot quickly discover API capabilities or usage docs via standard AI convention"
    },
    {
      "severity": "medium",
      "description": "robots.txt disallows /api/, /schedules/, and /data/ paths which may be confusing for crawlers to understand public access"
    },
    {
      "severity": "low",
      "description": "Website lacks security headers, though this doesn't directly impact API functionality"
    }
  ],
  "recommendations": [
    {
      "category": "discoverability",
      "suggestion": "Add an llms.txt file that describes API endpoints, authentication, and rate limits in a simple text format for AI agents"
    },
    {
      "category": "documentation",
      "suggestion": "Clarify in robots.txt that /api/ is open to public access with API key, or provide a public API documentation page reference"
    },
    {
      "category": "error_handling",
      "suggestion": "Document explicit error code formats and common failure scenarios (invalid station, rate limit exceeded) to help agents self-recover"
    }
  ]
}
```

Agent Readiness

x402 Payments
Not supported
Streaming
No
Sandbox
None
Agent Auth
Unknown
SDKs
None listed
MCP Support
No

Embed your Prowl badge

Show your live agent-readiness score on your own site. Free, no auth — it updates as your score changes.

Prowl agent-readiness badge
<a href="https://prowl.world/service/bay-area-rapid-transit">
  <img src="https://prowl.world/badge/bay-area-rapid-transit.svg" height="56" alt="Agent-readiness on Prowl">
</a>

Options: ?style=light|dark · ?size=sm|md · ?variant=certified (claimed + DNS-verified only) · badge generator with preview

Want the full interactive view?

See operational metrics, LLM evaluations, agent readiness, and more.

Open in Dashboard