Squiggle

{
  "service_type": "platform",
  "base_url": "https://api.squiggle.com.au",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [
    "/squiggle/sources",
    "/squiggle/teams",
    "/squiggle/games",
    "/squiggle/standings",
    "/squiggle/tips",
    "/squiggle/ladder",
    "/squiggle/venues",
    "/squiggle/seasons",
    "/squiggle/player_games",
    "/squiggle/players"
  ],
  "pricing_model": {
    "type": "free",
    "details": {
      "no api key required",
      "donations accepted via website",
      "terms of service apply"
    }
  },
  "rate_limits": {
    "unknown": "No explicit limits documented; but reasonable use expected."
  },
  "capabilities": [
    "AFL match fixtures",
    "Match results and scores",
    "Team and season statistics",
    "Ladder positions and standings",
    "Player statistics (if available)",
    "Tips and predictions from squiggle model",
    "Venue information",
    "Historical data across seasons"
  ],
  "raw_analysis": "Squiggle is a free, open API service focused exclusively on Australian Football League (AFL) data. It provides comprehensive data on fixtures, results, tips, and statistical predictions, developed by a solo enthusiast (Michael). The API is simple, uses JSON or text via GET requests, and requires no authentication, making it accessible for hobbyist developers, data analysts, and sports fans. The project appears mature, having been active for many years, with continuous updates during the AFL season. Integration is straightforward for any app needing AFL data, but lacks official SDKs and is limited to AFL sports. Data quality is generally reliable given its long-standing reputation among the AFL analytics community. The API is hosted at api.squiggle.com.au, with endpoints covering sources, teams, games, tips, and more. There are no built-in rate limits, but users should be respectful. Overall, it's a niche but valuable resource for AFL-related projects."
}

2/3 tests passed

```json
{
  "overall": 45,
  "dimensions": {
    "token_efficiency": 5.0,
    "first_try_success": 4.0,
    "response_parseability": 3.0,
    "error_clarity": 4.0,
    "doc_quality": 3.0,
    "auth_simplicity": 3.0,
    "latency": 8.5,
    "consistency": 5.0
  },
  "pricing_normalized": {},
  "issues": [
    "No /llms.txt file (404) — makes AI agent discovery harder",
    "No clear feature documentation or capabilities visible from checks",
    "Missing security headers on all responses",
    "Limited metadata about authentication or API structure",
    "Response previews show only generic HTML with no useful content signals"
  ],
  "recommendations": [
    "Add an /llms.txt file with structured API documentation and capabilities",
    "Publish clear getting-started guides and API reference docs",
    "Implement standard security headers (CORS, HSTS, etc.)",
    "Provide explicit auth flow documentation and quickstart examples",
    "Add a public status page or uptime metrics to demonstrate reliability"
  ]
}
```