KONTESTS

{
  "service_type": "platform",
  "base_url": "https://kontests.net/api",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [
    {
      "path": "/",
      "method": "GET",
      "description": "Fetches all upcoming and ongoing contests from multiple platforms, combined into a single array. No parameters, returns JSON array of contest objects with fields: name, url, start_time, end_time, duration, site, in_24_hours, status."
    },
    {
      "path": "/sites",
      "method": "GET",
      "description": "Returns a list of supported contest platform identifiers (e.g., 'CodeForces', 'CodeChef', 'LeetCode', etc.)."
    },
    {
      "path": "/{site}",
      "method": "GET",
      "description": "Fetches contests for a specific site (e.g., /CodeForces). Returns only contests from that platform. Site name is in the path, case-insensitive."
    }
  ],
  "pricing_model": {
    "type": "free",
    "details": "Public API, no API key required, no rate limit explicitly documented."
  },
  "rate_limits": {},
  "capabilities": [
    "Fetch all contests from multiple coding platforms in one call",
    "Filter contests by platform (site)",
    "List supported platforms",
    "Provides contest metadata: name, URL, start/end times, duration, site, whether within 24 hours, status (ongoing/upcoming)"
  ],
  "raw_analysis": "KONTESTS is a free public API service that aggregates competitive programming contest schedules from various online judges and coding platforms. It is designed for developers who want to integrate contest listings into their applications, tools, or dashboards without requiring authentication. The API is lightweight and simple: the root endpoint returns a JSON array of all contests (both ongoing and upcoming) from all supported sites, while the /sites endpoint lists the supported platform names. Additional endpoints like /{site} allow filtering by a specific platform, e.g., /CodeForces. The service is mature enough to be widely referenced in developer communities, with a simple and reliable interface. It does not require an API key, making it accessible for hobby projects and production use alike. However, rate limits are not documented, and the API is read-only with no write endpoints. The response data includes essential fields such as contest name, URL, start and end times (in ISO 8601), duration (in seconds), site identifier, a flag indicating if the contest starts within 24 hours, and a status field indicating 'CODING' or 'BEFORE'. The API is ideal for building contest trackers, reminder systems, or aggregator feeds. There is no official SDK, but its simplicity allows easy integration in any language. Overall, it is a useful, free utility for the competitive programming community."
}

0/3 tests passed

```json
{
  "overall": 35,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 4.0,
    "response_parseability": 9.0,
    "error_clarity": 4.0,
    "doc_quality": 3.0,
    "auth_simplicity": 10.0,
    "latency": 1.0,
    "consistency": 1.0
  },
  "pricing_normalized": {
    "cost": 0,
    "currency": "USD",
    "billing": "free",
    "notes": "Public API, no API key required"
  },
  "issues": [
    "Extreme latency: ~30 seconds response time across all checks (website, robots.txt, llms.txt)",
    "No HTTPS security headers detected",
    "All three checks returned null status codes, suggesting server timeout or unresponsiveness",
    "Response preview is null, indicating no actual content was served during testing",
    "llms.txt not available for automated documentation discovery"
  ],
  "recommendations": [
    "Investigate and fix server performance — 30s response times are unacceptable for production API use",
    "Add proper HTTPS security headers (HSTS, CSP, X-Content-Type-Options)",
    "Publish an llms.txt file for AI agent documentation discovery",
    "Document rate limits and error response formats explicitly",
    "Add reliability/status page to communicate uptime expectations"
  ]
}
```