DriveBC's Open511 API

{
  "service_type": "platform",
  "base_url": "https://www.drivebc.ca",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {"type": "free", "details": {"notes": "Government of British Columbia public service, no cost to use"}},
  "rate_limits": {},
  "capabilities": [
    "real-time road event data (accidents, construction, closures)",
    "Open511 specification compliant API",
    "highway webcams",
    "BC road conditions and weather",
    "ferry delay information",
    "travel advisories",
    "route planning",
    "geocoding",
    "vector tile basemap"
  ],
  "raw_analysis": "DriveBC is the Government of British Columbia's official traveller information platform, providing real-time road conditions, highway closures, webcams, weather, ferry delays, and travel advisories for highways across British Columbia, Canada. The service is free to the public and is maintained by the BC Ministry of Transportation and Infrastructure.\n\nThe platform exposes an Open511-compliant API (http://www.drivebc.ca/api) that reports known road events such as traffic accidents, construction, and closures. Open511 is an open specification for sharing road event data (closures, incidents, construction, etc.) in a standardized JSON/XML format. This makes DriveBC's data interoperable with other jurisdictions that also implement Open511 (e.g., some US states and Canadian provinces).\n\nFrom the page source, additional integrations are visible: ArcGIS vector tile basemaps, BC geocoder (geocoder.api.gov.bc.ca), Route Planner API (router.api.gov.bc.ca), and a routable locations OWS service hosted on Silver.devops.gov.bc.ca. These appear to be supporting services used by the web app rather than part of the Open511 API itself.\n\nMaturity: DriveBC is a long-established government service (legacy URL https://legacy.drivebc.ca exists; the current app reports release 1.5.1, deployment tag rc59). It's widely used by BC residents, travellers, and commercial drivers, and its data is consumed by third-party apps and agencies.\n\nPricing: Free. Government-funded public service. No authentication required to view the public web app; the Open511 API is publicly accessible without an API key based on its design.\n\nRate limits: Not documented in the provided information.\n\nTarget users: Drivers, travellers, logistics/commercial transport operators, emergency services, and developers building travel/traffic applications for British Columbia."
}

3/3 tests passed

{
  "overall": 78,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 9.0,
    "response_parseability": 9.5,
    "error_clarity": 7.0,
    "doc_quality": 8.0,
    "auth_simplicity": 10.0,
    "latency": 9.5,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "model": "free",
    "cost_per_call": 0,
    "notes": "Government of British Columbia public service; no API keys, no cost, no rate-limit friction documented"
  },
  "issues": [
    "No dedicated llms.txt or agent-facing documentation endpoint detected (llms.txt returns the web app HTML shell)",
    "Error clarity for the Open511 API is only as good as the spec — BC-specific quirks and rate limits aren't documented in a single agent-readable place",
    "Auth simplicity is achieved by having none, which is great for agents but means no per-user scoping or personalization",
    "The web endpoints return a JS app shell (window.__ENV__), so agents must hit the documented Open511/DriveBC API rather than scrape the site"
  ],
  "recommendations": [
    "Publish a machine-readable llms.txt or openapi.json describing the Open511 endpoints, parameters, and error codes",
    "Surface a concise 'getting started for agents' guide with example curl calls and typical response shapes",
    "Document rate limits and any BC-specific event taxonomy extensions to the Open511 spec",
    "Provide a lightweight health/status endpoint so agents can programmatically check availability"
  ]
}