BC Data Catalogue API

{
  "service_type": "platform",
  "base_url": "https://data.gov.bc.ca",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [
    {
      "name": "CKAN Action API",
      "path": "/api/3/action/{action}",
      "method": "GET|POST",
      "description": "Standard CKAN Action API endpoints for package_search, package_show, organization_list, group_list, datastore_search, etc. Version confirmable via /api/action/status_show."
    },
    {
      "name": "CKAN Status",
      "path": "/api/3/action/status_show",
      "method": "GET",
      "description": "Returns CKAN version and site info."
    },
    {
      "name": "Dataset Search",
      "path": "/api/3/action/package_search",
      "method": "GET",
      "description": "Search datasets by query, filters, facets."
    },
    {
      "name": "Dataset Detail",
      "path": "/api/3/action/package_show",
      "method": "GET",
      "description": "Retrieve metadata for a single dataset by id or name."
    },
    {
      "name": "Datastore Search",
      "path": "/api/3/action/datastore_search",
      "method": "GET|POST",
      "description": "Query tabular data resources hosted in the CKAN DataStore."
    },
    {
      "name": "Datastore SQL",
      "path": "/api/3/action/datastore_search_sql",
      "method": "GET|POST",
      "description": "Run read-only SQL queries against DataStore resources."
    }
  ],
  "pricing_model": {
    "type": "free",
    "details": {
      "notes": "Open government data portal, publicly accessible at no cost."
    }
  },
  "rate_limits": {
    "notes": "No publicly documented rate limits for the BC Data Catalogue. Standard CKAN deployments typically throttle abusive traffic; consumers should cache and paginate responsibly."
  },
  "capabilities": [
    "Open data catalogue (CKAN-based) for Government of British Columbia",
    "Dataset metadata search, filtering, and faceting",
    "Organization, group, and tag browsing",
    "Resource access (CSV, JSON, XML, GeoJSON, WMS, etc.)",
    "Tabular data querying via CKAN DataStore (search and SQL)",
    "Bulk metadata harvesting via CKAN APIs",
    "Public, unauthenticated read access",
    "Optional API key authentication for write/private operations"
  ],
  "raw_analysis": "The BC Data Catalogue (data.gov.bc.ca) is the provincial open data portal for British Columbia. It is a CKAN-based catalogue — the description explicitly references docs.ckan.org — and the HTML delivered appears to be a Vue.js single-page application front-end (Vuetify, Webpack chunks, Snowplow analytics). Beneath the SPA, the standard CKAN Action API (/api/3/action/...) is the canonical programmatic interface. The API is public and read-oriented; no auth is required for read operations (package_search, package_show, organization_list, datastore_search, datastore_search_sql, status_show). An API key would be needed only for write/admin actions. Pricing is free; data is open government data. Rate limits are not published; best practice is to paginate, cache, and avoid pounding the endpoint. Integrations: the catalogue feeds BC's open data ecosystem, supports CKAN harvesters (ckanext-harvest), and resources may be exposed via WMS/WFS, GeoJSON, and direct downloads. The platform is mature and well-maintained by the BC government. The provided HTML is essentially a client shell; the SPA likely calls the CKAN API from the browser, so scraping the SPA is unnecessary — hit the API directly."
}

3/3 tests passed

{
  "overall": 68,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 7.5,
    "response_parseability": 8.5,
    "error_clarity": 7.0,
    "doc_quality": 7.5,
    "auth_simplicity": 9.5,
    "latency": 9.0,
    "consistency": 7.5
  },
  "pricing_normalized": {
    "model": "free",
    "notes": "Open government data portal; no cost, public unauthenticated read access. Optional API key for writes."
  },
  "issues": [
    "robots.txt disallows /api/ and /client-api/ for crawlers, but these are the primary programmatic access points for agents — potential friction if agents respect robots.txt strictly.",
    "No llms.txt file found; llms_txt check returned the SPA HTML shell instead of a real machine-readable summary.",
    "Website root is a JavaScript SPA shell — no server-rendered content or structured metadata for agents hitting the homepage.",
    "No security headers observed (no HSTS, CSP, X-Content-Type-Options, etc.) on checked responses.",
    "No explicit OpenAPI/Swagger description surfaced despite CKAN's well-documented API — agents rely on external CKAN knowledge.",
    "robots.txt includes Crawl-Delay: 10, which discourages high-throughput agent crawling of HTML pages."
  ],
  "recommendations": [
    "Publish an llms.txt or /llms.txt summarizing the CKAN API endpoints, key datasets, and usage patterns so agents get a machine-readable entrypoint.",
    "Allow /api/ in robots.txt for known agent user-agents, or clearly document that API access is intended despite the crawler disallow.",
    "Provide a top-level OpenAPI/Swagger spec URL for the CKAN DataStore and package APIs.",
    "Serve a minimal SSR or static landing page at / with embedded JSON-LD or meta tags describing the catalogue for non-JS agents.",
    "Add standard security headers (HSTS, CSP, X-Content-Type-Options) to build trust and enable automated eligibility checks.",
    "Surface a concise 'getting started for developers' page listing the base URL, common endpoints (package_search, datastore_search, organization_list), and example queries."
  ]
}