The Blue Alliance API v3

```json
{
  "service_type": "platform",
  "base_url": "https://www.thebluealliance.com",
  "auth_method": "api_key",
  "auth_config": {
    "header": "X-TBA-Auth-Key",
    "key_location": "admin panel at https://www.thebluealliance.com/account",
    "notes": "All endpoints require an Auth Key passed in the X-TBA-Auth-Key header"
  },
  "endpoints": [
    {
      "path": "/api/v3/teams/{page_num}",
      "method": "GET",
      "description": "List of FIRST Robotics Competition teams (paginated)"
    },
    {
      "path": "/api/v3/team/{team_key}",
      "method": "GET",
      "description": "Info about a single FRC team"
    },
    {
      "path": "/api/v3/events/{year}",
      "method": "GET",
      "description": "List of events in a given year"
    },
    {
      "path": "/api/v3/event/{event_key}",
      "method": "GET",
      "description": "Info about a single event"
    },
    {
      "path": "/api/v3/team/{team_key}/events/{year}",
      "method": "GET",
      "description": "Events a team attended in a year"
    },
    {
      "path": "/api/v3/event/{event_key}/matches",
      "method": "GET",
      "description": "Match results for an event"
    },
    {
      "path": "/api/v3/event/{event_key}/rankings",
      "method": "GET",
      "description": "Rankings at an event"
    },
    {
      "path": "/api/v3/event/{event_key}/alliances",
      "method": "GET",
      "description": "Alliances for a playoff event"
    },
    {
      "path": "/api/v3/event/{event_key}/oprs",
      "method": "GET",
      "description": "Offensive power ratings (OPRs) for an event"
    },
    {
      "path": "/api/v3/status",
      "method": "GET",
      "description": "API status/health check"
    }
  ],
  "pricing_model": {
    "type": "free",
    "details": {
      "notes": "The Blue Alliance is a free, community-run platform. API access is provided at no cost, though users are encouraged to register an Auth Key via their account page."
    }
  },
  "rate_limits": {
    "notes": "Docs recommend reading the API rules; a reasonable request rate is expected. TBA asks consumers not to make excessive/rapid requests and to cache responses where possible.",
    "documentation": "https://www.thebluealliance.com/apidocs"
  },
  "capabilities": [
    "Query FRC team information and metadata",
    "Retrieve event schedules and results",
    "Access match data and scores",
    "Fetch event rankings and alliance selections",
    "Obtain computed statistics (OPRs, etc.)",
    "List awards and team event participation",
    "Search media (photos, videos) linked to teams/events",
    "RESTful JSON API with versioned base path (/api/v3)"
  ],
  "raw_analysis": "The Blue Alliance (TBA) is a community-developed platform that aggregates information and statistics about FIRST Robotics Competition (FRC) teams and events. It is widely used by FRC teams, students, mentors, scouts, and app developers who want programmatic access to match results, rankings, event schedules, team profiles, and derived metrics like OPRs. The service is mature — it has been operating for over a decade (since the early 2010s) and is considered a de facto data source for the FRC community.\n\nAPI details: TBA exposes a well-documented REST API under https://www.thebluealliance.com/api/v3. Authentication is via an API key (Auth Key) passed in the X-TBA-Auth-Key request header. Keys are issued through the user's TBA account. All endpoints require the key. The API is public, free to use, and returns JSON. The documentation is available at https://www.thebluealliance.com/apidocs, and developers are asked to follow reasonable usage guidelines (avoid hammering the API, cache results).\n\nIntegration surface: Beyond the raw REST API, TBA has a broad ecosystem — community libraries/SDKs exist for Python, JavaScript, Java, and others; the underlying data also feeds many FRC scouting apps (e.g., apps powered by TBA data), Statbotics, and event livestream tools. Because it is community-run and non-commercial, there is no official SLA, but reliability is generally high.\n\nRelevance for Prowl: This is not a 'no public API' platform — it has a clear, documented REST API with header-based auth. It fits the 'platform' service_type because TBA itself is a data platform/dashboard (web app) whose primary value is the aggregated FRC data. Key considerations for integration are the required API key header and the expectation of respectful rate limiting."
}
```

2/3 tests passed

{
  "overall": 71,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 7.5,
    "response_parseability": 8.5,
    "error_clarity": 7.0,
    "doc_quality": 7.5,
    "auth_simplicity": 7.0,
    "latency": 9.0,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "model": "free",
    "notes": "Free, community-run. Auth key registration encouraged but not strictly required for basic API access."
  },
  "issues": [
    "robots.txt disallows /api/ — crawlers (and some agent frameworks that respect robots.txt) are blocked from the API surface, which can hinder automated discovery.",
    "No llms.txt (404) — agents lack a machine-readable entry point describing capabilities, base URLs, and usage.",
    "Competition-focused (FRC) niche limits broad agent utility; not a general-purpose platform.",
    "API auth via Auth Key requires account creation; onboarding path is not clearly surfaced in provided data.",
    "No security headers observed on responses."
  ],
  "recommendations": [
    "Publish an llms.txt or /.well-known/ agent manifest describing the v3 API, auth, rate limits, and common endpoints.",
    "Reconsider robots.txt Disallow: /api/ for read-only public endpoints, or document an explicit agent allowlist.",
    "Provide OpenAPI/Swagger spec for /api/v3 to improve machine-parseability and first-try success.",
    "Surface a 'Getting Started with the API' page above the fold with auth key instructions and example cURL requests.",
    "Document rate limits, pagination, and quota behavior clearly to improve error clarity for agents."
  ]
}