Hoppscotch

{
  "service_type": "platform",
  "base_url": "https://hoppscotch.io",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "notes": "Open-source, self-hostable (free). Cloud/on-prem offerings available via Hoppscotch Cloud and Enterprise plans. Self-hosted community edition is free under open-source license."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "API request creation and testing (REST)",
    "GraphQL query support",
    "WebSocket, SSE, and Socket.IO testing",
    "Collection and workspace management",
    "Environments and variables",
    "Request history and saved requests",
    "Team collaboration (Cloud/Enterprise)",
    "Web, Desktop, and CLI clients",
    "Self-hosted (on-prem) deployment",
    "Offline usage",
    "Import/export of API specifications (Swagger/OpenAPI parsing shim present)",
    "Pre-request scripts and tests"
  ],
  "raw_analysis": "Hoppscotch is an open-source API development ecosystem positioned as a lightweight, fast alternative to Postman and Insomnia. It provides clients across Web, Desktop, and CLI, and can be used offline, self-hosted on-prem, or via Hoppscotch Cloud. Its primary audience is API developers, QA engineers, and teams that need to construct, send, and test HTTP/REST, GraphQL, WebSocket, SSE, and Socket.IO requests.\n\nMaturity: The project is mature and well-known (originally named Postwoman). It has a large open-source community on GitHub, active development, and a commercially backed cloud/enterprise offering. The landing page is a SPA (Vite-built, served with module preloads, PWA manifest, service-worker-ready meta) and does not expose a public REST API directly at hoppscotch.io.\n\nPublic REST API: There is no documented public REST API served from the marketing/app domain itself. The platform's value is in being a client for consuming other APIs rather than exposing its own. The self-hosted and cloud instances expose internal API routes for account, workspace, and collection sync (e.g., under the app's backend), but these are not advertised as a stable public developer API and typically require authentication to that instance.\n\nAuth: Public-facing site requires no authentication to access the web app. Cloud account auth would be OAuth/email based; self-hosted instances support configurable auth providers. No standard API key mechanism is documented at the public root.\n\nIntegrations: Supports OpenAPI/Swagger import (swagger-parser shim in the DOM), code generation/snippets, environment variables, and team collaboration workspaces. CLI enables CI/CD integration. Since it is open source, teams can extend and integrate it into their own toolchains.\n\nPricing: Freemium — free open-source self-hosting and free tier, with paid Cloud/Enterprise plans. Exact rate limits and API quotas are not documented on the public landing page.\n\nConclusion: Hoppscotch is a platform (API development tool) rather than a public REST API service. Automated integration would target a self-hosted or cloud instance's internal endpoints (not publicly documented), or the CLI for CI usage. No public, unauthenticated REST API endpoints are exposed at the given URL."
}

3/3 tests passed

{
  "overall": 72,
  "dimensions": {
    "token_efficiency": 9.0,
    "first_try_success": 8.0,
    "response_parseability": 7.0,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 8.0,
    "latency": 6.0,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "model": "freemium",
    "open_source": true,
    "self_hostable": true,
    "community_edition": "free",
    "cloud_enterprise": "paid"
  },
  "issues": [
    "No native llms.txt or agent-oriented documentation file — llms.txt path returns HTML SPA fallback rather than structured machine-readable content",
    "No public REST/GraphQL API for programmatic management of collections/workspaces documented, limiting agent automation",
    "Website homepage response latency ~1.06s (above 500ms threshold)",
    "Product is fundamentally a GUI/developer tool, so agent-driven automation surfaces are limited"
  ],
  "recommendations": [
    "Publish an llms.txt or agent-oriented structured docs page describing capabilities, endpoints, and pricing",
    "Expose a documented headless API/CLI surface with stable schemas for collection/workspace CRUD",
    "Add magic-link / SSO-friendly onboarding path to reduce signup friction for agents onboarding users",
    "Provide a status page and explicit uptime/SLA documentation to strengthen reliability signals",
    "Reduce homepage TTFB below 500ms for snappier agent-driven previews"
  ]
}