CleanURI

{
  "service_type": "platform",
  "base_url": "https://cleanuri.com",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [
    {
      "path": "/api/v1/shorten",
      "method": "POST",
      "description": "Shorten a long URL. Accepts JSON or form data with 'url' parameter.",
      "auth_required": false,
      "rate_limit": "Not documented, but service is free without API key."
    }
  ],
  "pricing_model": {
    "type": "free",
    "details": {
      "free_tier": true,
      "paid_tier": false,
      "api_key_required": false,
      "ads": "No ads visible on API responses"
    }
  },
  "rate_limits": {},
  "capabilities": [
    "URL shortening",
    "Custom aliases not available",
    "Public API with simple POST endpoint",
    "No authentication required",
    "JSON or form data support",
    "Example usage with curl",
    "Documentation page with examples"
  ],
  "raw_analysis": "CleanURI is a straightforward, no-frills URL shortener service. It is positioned as a simple tool for developers and users who need quick URL shortening without the overhead of account creation or API keys. The service is completely free, with no documented rate limits or pricing tiers, making it attractive for lightweight use cases, though this also raises questions about long-term stability and scalability. The API is minimal: a single POST endpoint that accepts a URL and returns a short URL. There is no support for custom aliases, analytics, or bulk operations, so it is not suitable for enterprise-level link management. The platform is web-based with a straightforward REST API, and its documentation is concise, including examples in multiple languages (curl, Python, PHP, etc.). Overall, it is mature enough for basic use but lacks advanced features. Integration is possible via simple HTTP calls from any language, and since no auth is required, it can be easily embedded into scripts or applications. However, users should consider reliability and potential service changes, as free services without auth may have availability risks."
}

2/3 tests passed

```json
{
  "overall": 71,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 8.0,
    "response_parseability": 8.5,
    "error_clarity": 7.0,
    "doc_quality": 7.5,
    "auth_simplicity": 10.0,
    "latency": 8.0,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "free": true,
    "paid_tier_exists": false,
    "api_key_required": false,
    "notes": "Fully free, no authentication, no API key needed"
  },
  "issues": [
    "No llms.txt file, potentially confusing for AI agents discovering capabilities programmatically",
    "No custom aliases available - limits customization for branded links",
    "Documentation lacks explicit error code documentation or rate limit info"
  ],
  "recommendations": [
    "Add an llms.txt file to improve agent discoverability and capability description",
    "Document error response formats (e.g., 4xx/5xx codes) and rate limiting policies",
    "Consider adding optional custom aliases for power users while keeping the free core",
    "Add status page or uptime information to reinforce reliability"
  ]
}
```