I created Postwoman, an online, open-source API

{
  "service_type": "platform",
  "base_url": "https://hoppscotch.io",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "open_source": true,
      "self_hostable": true,
      "cloud_pro": "paid tier for advanced features"
    }
  },
  "rate_limits": {},
  "capabilities": [
    "API request builder",
    "HTTP/HTTPS methods: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS",
    "Request headers and params customization",
    "Query string generation",
    "Request body support (JSON, form-data, raw text)",
    "Response viewer with pretty-printed JSON/XML",
    "Response headers and status code display",
    "Response time and size metrics",
    "Collections for organizing requests",
    "History of past requests",
    "Environment variables",
    "WebSocket testing (real-time)",
    "Server-Sent Events (SSE) testing",
    "GraphQL support (compose and execute queries)",
    "Pre-request scripts and tests (via custom scripting)",
    "Import/export workspaces (JSON)",
    "Shareable links for requests",
    "Proxy support for cross-origin requests",
    "PWA installable",
    "Theme customization",
    "Multi-account support (via login with GitHub/Google)",
    "Offline mode (local storage)",
    "Self-hosting option"
  ],
  "raw_analysis": "The service described is Postwoman (now Hoppscotch), an open-source, browser-based API request builder created by Liyas Thomas. It was initially launched as a Show HN on Indie Hackers and quickly gained popularity among developers for its lightweight, fast, and minimal interface compared to tools like Postman. Originally named Postwoman, the project was rebranded to Hoppscotch to avoid trademark conflicts. The platform is fully web-based, requiring no native installation, and works entirely in the browser with an optional PWA for offline use. It supports standard HTTP requests, WebSocket, SSE, and GraphQL, making it a versatile tool for API testing and development. It is self-hostable, allowing teams to run their own instance for security and data privacy. The primary audience is developers and API testers who prefer a quick, open-source alternative to commercial tools. The product is mature, with an active community on GitHub, integrations with CI/CD via Hoppscotch CLI (for automated testing), and browser extensions for additional features. It offers both free open-source features and a premium cloud service (Hoppscotch Pro) with collaboration and advanced capabilities. Since it's a web app, there is no traditional REST API for external use; the platform itself acts as a client to interact with other APIs. Therefore, the endpoint list is empty as it does not expose a public API for programmatic access (aside from its own web interface). Pricing is free for the open-source version, with optional paid tiers on Hoppscotch Cloud for team collaboration and advanced features like environment sync and unlimited history. There are no explicit rate limits documented for the open-source version, as it is client-side, but the cloud service may have usage-based limits for premium plans."
}

3/3 tests passed

```json
{
  "overall": 79,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 9.0,
    "response_parseability": 6.0,
    "error_clarity": 5.0,
    "doc_quality": 6.0,
    "auth_simplicity": 7.0,
    "latency": 9.0,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "free_tier": true,
    "open_source": true,
    "self_hostable": true,
    "pro_tier_available": true,
    "trial_required": false
  },
  "issues": [
    "llms.txt endpoint returns HTML instead of structured text, hindering agent-based documentation access",
    "Limited structured export formats (only JSON for workspaces), not ideal for direct API consumption",
    "Error clarity in docs not explicitly detailed for edge cases"
  ],
  "recommendations": [
    "Add a proper llms.txt endpoint with plain-text or markdown format for AI agents",
    "Provide OpenAPI/Swagger specification for API-based access to collections",
    "Document common error scenarios and troubleshooting steps explicitly"
  ]
}
```