Agent-ready API

3/3 tests passed

```json
{
  "overall": 52,
  "dimensions": {
    "token_efficiency": 4.0,
    "first_try_success": 5.0,
    "response_parseability": 6.0,
    "error_clarity": 4.0,
    "doc_quality": 6.0,
    "auth_simplicity": 5.0,
    "latency": 8.0,
    "consistency": 7.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "free_tier": "unknown",
    "enterprise_tier": "unknown"
  },
  "issues": [
    "No capabilities or pricing model data provided — agent cannot determine what this platform actually offers or costs",
    "Website is a single-page app with minimal initial content; actual functionality is behind client-side rendering",
    "Robots.txt disallows /api/, /dashboard/, /sign-in, /sign-up, /compare — critical paths for AI agents are blocked from crawling",
    "llms.txt indicates the site is a 'tool that scores websites' (Agent Ready), not the platform being evaluated — likely an MCP/agent tool, making core value proposition unclear from the data",
    "No auth flow documented — sign-in path is disallowed in robots.txt, suggesting the onboarding process is not agent-friendly",
    "No error messages or limitation documentation observed in the checks"
  ],
  "recommendations": [
    "Provide explicit capability list (e.g., 'scores websites against Vercel spec, 69 checks, MCP support') so agents can describe it in one sentence",
    "Publish a clear pricing page with free tier details and API limits — currently unknown to agents",
    "Allow crawl access to key onboarding paths (e.g., /docs, /getting-started, /pricing) or provide an api-reference in llms.txt",
    "Add a publicly accessible /llms.json or full API spec covering auth, endpoints, and rate limits",
    "Document error handling — what happens when a site fails checks, how to interpret scores",
    "Consider adding a simple OAuth/magic-link signup flow with public docs for agent-driven account creation"
  ]
}
```