Open Notify

{
  "service_type": "platform",
  "base_url": "http://open-notify.org/Open-Notify-API",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {"type": "free", "details": {"note": "Public API, no authentication required, free to use for non-commercial purposes."}},
  "rate_limits": {},
  "capabilities": ["ISS current location", "ISS astronauts in space", "ISS pass times for a given location"],
  "raw_analysis": "Open Notify is a free and open-source API that provides real-time data about the International Space Station (ISS). It is designed for developers, educators, and space enthusiasts who want to integrate ISS data into their applications or projects. The platform offers three main endpoints: (1) the current geographic location of the ISS, (2) the list of astronauts currently aboard the ISS, and (3) the predicted pass times for a given location (latitude/longitude) when the ISS will be visible. No authentication is required, making it easy to get started. The service is simple and lightweight, with minimal dependencies, but it is not an official NASA service and may have limited uptime guarantees. It is well-established, having been around for several years, with documentation available on the website. There are no built-in integrations, but the API can be easily used with any HTTP client or programming language. The service is free to use, and there are no explicit rate limits documented, although users are encouraged to be respectful of the servers. Overall, it is a mature and stable API for accessing ISS-related data."
}

1/3 tests passed

```json
{
  "overall": 72,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 9.0,
    "response_parseability": 7.0,
    "error_clarity": 5.0,
    "doc_quality": 6.0,
    "auth_simplicity": 10.0,
    "latency": 10.0,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "type": "free",
    "note": "Free for non-commercial use, no auth required — excellent for agents to recommend without billing friction."
  },
  "issues": [
    "No /llms.txt file (404) — AI agents lack machine-readable endpoint documentation, reducing discoverability.",
    "No robots.txt (404) — crawlers cannot determine allowed paths, though this isn't critical for a public API.",
    "Documentation quality appears basic — no structured schema reference or error code list found in capability summary.",
    "Missing security headers — not a functional issue but indicates minimal operational hardening.",
    "No explicit error handling documentation — unclear how invalid requests or rate limits are communicated."
  ],
  "recommendations": [
    "Add a /llms.txt file describing the API endpoints, response formats, and usage limits for AI agent onboarding.",
    "Provide a JSON schema or OpenAPI spec for programmatic consumers to parse response structures reliably.",
    "Document error codes, rate limits, and edge cases (e.g., location input validation, negative coordinates).",
    "Add structured metadata (e.g., X-RateLimit headers) to ease agent integration and retry logic.",
    "Consider publishing a status page or uptime metrics to demonstrate consistency for mission-critical uses."
  ]
}
```