Open Data API

{
  "service_type": "platform",
  "base_url": "https://openbanking.org.uk",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "note": "Open Banking standards are published openly and free to access; no API access fee is defined in the provided information."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Publishes Swagger/OpenAPI specifications for OpenData",
    "Standards and specifications for Open Banking APIs",
    "Documentation and specification distribution",
    "Enables data sharing and integration patterns across banking APIs"
  ],
  "raw_analysis": "The provided information identifies a service called 'Open Data API' at https://openbanking.org.uk, described as the 'Latest Swagger specification for OpenData'. However, the URL points to Open Banking (openbanking.org.uk), which is the UK Open Banking standards body/ecosystem, not a conventional REST API platform with runtime endpoints. It primarily publishes specifications (such as Swagger/OpenAPI documents) that define how banks and third parties should expose/consume open banking data. Therefore, it is best characterized as a standards/specification platform rather than an operational API with base URL, auth, and endpoints. No authentication method, rate limits, or actual callable endpoints are specified. It is likely free to access as an open standard. Its primary audience is financial institutions, fintechs, TPPs, and developers building on Open Banking. Maturity is high as a standard/specification source, but it does not itself provide a live data API; integrations would be with individual banks' implementations."
}

2/3 tests passed

```json
{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 5.0,
    "response_parseability": 6.0,
    "error_clarity": 6.0,
    "doc_quality": 6.0,
    "auth_simplicity": 7.0,
    "latency": 6.0,
    "consistency": 7.0
  },
  "pricing_normalized": {
    "model": "free",
    "notes": "Open Banking standards published openly and free to access; no API access fee. No per-request pricing. Value is specification/doc access rather than a metered API."
  },
  "issues": [
    "No llms.txt (404) — poor discoverability for AI agents seeking machine-readable orientation.",
    "Website latency ~784ms for main page and ~963ms on 404 path; inconsistent response times.",
    "Robots.txt points to https://www.openbanking.qa/sitemap_index.xml — wrong TLD (.qa instead of .uk), suggesting config/migration error and reducing crawl reliability.",
    "Specification-focused platform and not an operational API; agents cannot fetch live banking data directly, limiting 'parseability' to docs/OpenAPI specs.",
    "Auth/onboarding value proposition for agents is unclear — standards access is open, but no described agent-facing identity or token flow."
  ],
  "recommendations": [
    "Publish an llms.txt describing the Open Banking standards, key spec URLs, and versioning to improve AI-agent discoverability.",
    "Fix the sitemap URL in robots.txt (.qa -> .uk) to ensure correct crawler and agent indexing.",
    "Expose a stable, versioned OpenAPI/Swagger index page with predictable URLs so agents can parse specs without scraping HTML.",
    "Add an explicit machine-readable changelog and status/uptime endpoint to improve consistency perception.",
    "Reduce TTFB on the main page and 404 routes; cache static docs to cut sub-second latency consistently."
  ]
}
```