departureboard.io API

{
  "service_type": "platform",
  "base_url": "https://departureboard.io",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "JSON API wrapper around the legacy National Rail SOAP API",
    "High-performance API written in Go",
    "Provides access to UK National Rail departure board data",
    "Documentation portal / developer website"
  ],
  "raw_analysis": "departureboard.io is positioned as a high-performance API written in Go that acts primarily as a JSON-API interface over the legacy UK National Rail SOAP API. Its stated goals include (1) exposing the legacy SOAP endpoints as modern JSON, and (at least one more function implied but truncated). It is aimed at developers building transport, travel, or departure-board applications for the UK rail network.\n\nThe page served at https://departureboard.io is a client-side single-page application (React, bundled under /static/js/main.*.js and /static/css/main.*.css), hosted on Cloudflare Pages with Cloudflare Rocket Loader and Cloudflare Pages Analytics enabled. It contains no server-rendered content describing API endpoints, auth, or pricing, so those details cannot be derived from this HTML alone. The presence of a documentation/developer-facing SPA strongly suggests the platform is mature enough to offer a self-service developer experience, but concrete endpoint paths, authentication scheme (likely an API key given the SOAP-wrapper nature), and rate limits are not visible here.\n\nThe title and meta tags indicate a dedicated product ('departureboard.io') with social presence (@departureboard_io on Twitter/X), Apple/Android web-app splash assets, and an OG image, which suggests it targets both web and mobile integrations. No pricing page or subscription tier information is exposed in the fetched markup, so the pricing model is recorded as unknown.\n\nBecause this service is fundamentally an API (not a generic SaaS dashboard), it does not fit the typical 'platform analyzer' profile of collaboration tools or dev environments, but it is not a simple REST API either: it wraps a legacy SOAP service, meaning integration requires understanding the upstream National Rail data model. Developers should expect to consult the SPA's documentation for endpoint details, authentication (likely API key), and rate limits. No public REST endpoints can be confirmed from this response, so endpoints are listed as empty rather than guessed."
}

3/3 tests passed

{
  "overall": 68,
  "dimensions": {
    "token_efficiency": 7.5,
    "first_try_success": 6.5,
    "response_parseability": 8.0,
    "error_clarity": 5.5,
    "doc_quality": 6.0,
    "auth_simplicity": 6.0,
    "latency": 9.5,
    "consistency": 7.0
  },
  "pricing_normalized": {},
  "issues": [
    "Pricing model is unknown/unclear — no public pricing documentation surfaced for agent or user decision-making",
    "No llms.txt found; /llms.txt request returned HTML fallback (status 200 but wrong content type), which can confuse agents expecting structured orientation",
    "Authentication/onboarding flow is not documented in the checks — unclear if API keys are self-serve or require manual approval",
    "Error and rate-limit documentation is not evidenced in the checks; SOAP-wrapper legacy origins suggest possible quirks",
    "Documentation appears minimal and may be ad-supported/generic, potentially low signal-to-noise for agents",
    "robots.txt allows all crawling (good) but no sitemap or structured discovery hints present"
  ],
  "recommendations": [
    "Publish a clear pricing page (free tier, quota, overage) so agents can represent cost accurately",
    "Add /llms.txt with concise API summary, endpoints, auth steps, and example calls",
    "Provide a self-serve API key flow (magic link or instant key) to maximize first-try success",
    "Document rate limits, error codes, and SOAP-wrapper caveats (e.g., station codes, data freshness)",
    "Expose OpenAPI/JSON schema for endpoint contracts to improve response parseability",
    "Add a status page for uptime transparency to boost consistency perception",
    "Include quickstart examples (curl + one SDK) directly in an agent-readable format"
  ]
}