Hoppscotch vs Insomnia
Hoppscotch
Hoppscotch
Insomnia wins · 13–21 (16 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to HoppscotchA direct probe confirms llms.txt is live at docs.hoppscotch.io/llms.txt returning HTTP 200 with structured documentation content, and the docs also expose agent-oriented resources like an official MCP server and CLI overview pages that an agent could consume. Missing for 10: no independent/community confirmation of an agent actually consuming llms.txt in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.hoppscotch.io/llms.txt # Hoppscotch Documentation > Find user guides, quickstarts, tutorials, use …”
- [probe] “official MCP server documented at https://docs.hoppscotch.io/documentation/clients/mcp-server/overview”
- [probe] “official CLI documented at https://docs.hoppscotch.io/documentation/clients/cli/overview”
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you.”
Kong's developer docs (which host Insomnia's documentation) expose a working llms.txt at the domain root and individual doc pages are directly fetchable as markdown (.md) files, which is agent-friendly, but this is a shared Kong-wide resource rather than an Insomnia-specific llms.txt, and a probe for an Insomnia-specific markdown index (insomnia/.md) returned 404. Missing for 10: a dedicated Insomnia-specific llms.txt or explicit agent-onboarding docs, and confirmation Insomnia itself (the product) references or promotes this file to agents.
- [probe] “PROBE llms.txt: HTTP 200 at https://developer.konghq.com/llms.txt # developer.konghq.com > Kong's developer documentation for Kong Gateway,…”
- [probe] “PROBE docs-md: HTTP 404 at https://developer.konghq.com/insomnia/.md”
- [claimed-docs] “Insomnia provides the ability to chain requests. This means you can extract values from the responses of other requests while also sharing s…”
- [claimed-docs] “Pre-request scripts allow you to execute tasks before a request is sent.”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round drawnHoppscotch ships an official CLI (hopp) explicitly designed to run API tests, automate monitoring, and manage collections from the terminal or automated systems, including CI-friendly JUnit report generation for collection runs — directly enabling headless/CI automation. missing for 10: independent third-party CI pipeline examples/case studies confirming real-world CI usage beyond vendor docs.
- [claimed-docs] “Use the Hoppscotch CLI to run API tests, automate monitoring, and manage collections from your terminal.”
- [claimed-docs] “The hopp test command now has the ability to generate a JUnit Report for collection runs in the CLI.”
- [claimed-docs] “With the command-line interface (CLI) you can interact with the Hoppscotch platform using a terminal, or through an automated system. This e…”
- [probe] “official CLI documented at https://docs.hoppscotch.io/documentation/clients/cli/overview”
Insomnia ships the Inso CLI, explicitly documented as designed for CI environments — it disables interactive prompts and returns exit codes to pass/fail builds, and supports test running, spec linting, and collection runs from CI/Git workflows without the GUI. This directly satisfies headless/automated execution for CI pipelines. Missing for 10: independent hands-on CI usage reports/case studies and more detail on advanced automation scenarios (e.g., parallelization, complex environment injection) beyond the docs themselves.
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
- [claimed-docs] “Use the Insomnia CLI to automate the execution of your API tests using your existing Git workflows.”
- [probe] “official CLI documented at https://developer.konghq.com/inso-cli/”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · round to InsomniaHoppscotchnone0/10Evidence only shows Hoppscotch exposing itself AS an MCP server (agents can connect to Hoppscotch to read/change collections, requests, etc.), which is the reverse of the story — Hoppscotch acting as an MCP client that consumes other servers' tools. No evidence of Hoppscotch connecting to or ingesting external MCP servers to use their tools.
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you.”
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you. It also sends real HTTP…”
- [probe] “official MCP server documented at https://docs.hoppscotch.io/documentation/clients/mcp-server/overview”
Insomnia has a documented MCP Client feature that connects to external MCP servers to access AI-ready tools, prompts, and resources, discovering and enabling invocation/testing of these elements directly in the app. This directly matches the story of plugging in MCP servers to use their tools. Missing for 10: independent/hands-on corroboration of the MCP client feature beyond first-party docs, and details on limitations or setup friction.
- [claimed-docs] “Use Insomnia to connect external Model Context Protocol (MCP) Servers to access AI-ready tools, prompts, and resources.”
- [claimed-docs] “The Insomnia MCP Client discovers these elements, which enables you to invoke, query, or test them directly in the app.”
- [claimed-docs] “Use MCP clients to connect Insomnia to Konnect for mocking, validating, and protecting requests in real time.”
ai-native userConnect an agent via an official MCP server
weight 3 · round to HoppscotchHoppscotch documents an official MCP server (docs-10, docs-22, probe-3) that exposes collections, requests, environments, and teams to an agent and can execute real HTTP requests, directly matching the story. Missing for 10: independent/hands-on community verification of the MCP server's behavior and any deeper docs on setup/auth scopes beyond the overview page.
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you.”
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you. It also sends real HTTP…”
- [probe] “official MCP server documented at https://docs.hoppscotch.io/documentation/clients/mcp-server/overview”
Insomnianone0/10Evidence shows Insomnia acts as an MCP *client* (docs-14, docs-30, docs-46) that connects to external MCP servers, not as an MCP server that an agent could connect to. No documentation of Insomnia exposing its own official MCP server endpoint was found in the evidence pack.
- [claimed-docs] “Use MCP clients to connect Insomnia to Konnect for mocking, validating, and protecting requests in real time.”
- [claimed-docs] “The Insomnia MCP Client discovers these elements, which enables you to invoke, query, or test them directly in the app.”
- [claimed-docs] “Use Insomnia to connect external Model Context Protocol (MCP) Servers to access AI-ready tools, prompts, and resources.”
ai-native userUse an official CLI
weight 2 · round drawnHoppscotch ships an official CLI (hopp) documented for running API tests, automating monitoring, managing collections from the terminal, and generating JUnit reports, corroborated by a probe confirming the official docs page. missing for 10: independent/hands-on community confirmation of CLI usage and more detail on full command coverage.
- [claimed-docs] “Use the Hoppscotch CLI to run API tests, automate monitoring, and manage collections from your terminal.”
- [claimed-docs] “The hopp test command now has the ability to generate a JUnit Report for collection runs in the CLI.”
- [claimed-docs] “With the command-line interface (CLI) you can interact with the Hoppscotch platform using a terminal, or through an automated system. This e…”
- [probe] “official CLI documented at https://docs.hoppscotch.io/documentation/clients/cli/overview”
Insomnia ships an official 'Inso CLI' documented for automating collection runs, linting OpenAPI specs, and running in CI pipelines with exit codes for pass/fail, which is exactly the kind of scriptable, agent-friendly interface an AI-native workflow would use. missing for 10: independent/hands-on community confirmation of Inso CLI usage and explicit framing of the CLI as AI/agent-oriented rather than just human CI tooling.
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
- [probe] “official CLI documented at https://developer.konghq.com/inso-cli/”
ai-native userDrive the product through a documented public API
weight 3 · round to HoppscotchHoppscotch documents a first-party MCP server that lets an agent read and modify collections, requests, environments, and teams and send real HTTP requests, plus a CLI for terminal/automated interaction (running tests, managing collections) — both are officially documented programmatic interfaces suited to AI-native/agentic use. Missing for 10: a general public REST/OpenAPI API for the platform itself (probe found openapi.json/swagger.json all 404), so agentic access is limited to the MCP/CLI surface rather than a broader documented API.
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you.”
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you. It also sends real HTTP…”
- [claimed-docs] “Use the Hoppscotch CLI to run API tests, automate monitoring, and manage collections from your terminal.”
- [claimed-docs] “With the command-line interface (CLI) you can interact with the Hoppscotch platform using a terminal, or through an automated system. This e…”
- [probe] “official MCP server documented at https://docs.hoppscotch.io/documentation/clients/mcp-server/overview”
- [probe] “official CLI documented at https://docs.hoppscotch.io/documentation/clients/cli/overview”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.hoppscotch.io/openapi.json, https://docs.hoppscotch.io/swagger.json, https://docs.hopps…”
Insomnia does not publish a documented public REST/programmatic API for driving the app itself (probe found no OpenAPI/swagger spec for the product), but it does offer the Inso CLI for scripted automation of tests, linting, and collection runs, plus an extensibility plugin system — giving AI-native users some programmatic control, just not a true public API surface. missing for 10: a documented HTTP/SDK-style public API for controlling Insomnia, independent confirmation the Inso CLI/plugin surface is used for AI-agent automation.
- [claimed-docs] “Use the Insomnia CLI to automate the execution of your API tests using your existing Git workflows.”
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “Unlimited access to plugins or build your own”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.konghq.com/openapi.json, https://developer.konghq.com/swagger.json, https://develo…”
- [probe] “official CLI documented at https://developer.konghq.com/inso-cli/”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnHoppscotchnone0/10Hoppscotch's MCP server docs describe granting an agent full read/write access to all collections, requests, environments, and teams, with no mention of scoped, least-privileged, or permission-limited credentials for agents. No evidence describes issuing restricted API keys/tokens specifically for AI agent use.
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you.”
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you. It also sends real HTTP…”
- [probe] “official MCP server documented at https://docs.hoppscotch.io/documentation/clients/mcp-server/overview”
Insomnianone0/10Insomnia offers RBAC for controlling access to its own resources, external vault integration for retrieving secrets, and environment variables for storing credentials, but there is no evidence of a feature to generate or issue scoped, least-privilege API credentials specifically for an AI agent to use. Given Insomnia's MCP client and AI features, this would be a plausible extension, but it's not documented anywhere in the evidence pack.
- [claimed-docs] “Use Role-based access control (RBAC) for fine-grain control over who can access which Insomnia resources.”
- [claimed-docs] “Insomnia supports integrating with external vault service providers to retrieve secret values automatically when sending requests.”
- [claimed-docs] “Use environments to define groups of variables that Insomnia applies across your requests. For example, you could create variables for base …”
- [claimed-docs] “Use Insomnia to connect external Model Context Protocol (MCP) Servers to access AI-ready tools, prompts, and resources.”
ai-native userBuild against official SDKs
weight 2 · round drawnHoppscotchnone0/10Evidence shows Hoppscotch offers a CLI, an MCP server, and AI-assisted scripting features, but there is no mention of official client SDKs (e.g., language libraries for programmatically building or extending Hoppscotch) anywhere in the docs or GitHub feature list.
Insomnianone0/10Evidence shows Insomnia's automation surface is the Inso CLI and plugin system, plus MCP client support, but no official SDK (e.g., a Node/Python/Go SDK) for programmatically building against Insomnia is documented anywhere in the pack.
- [claimed-docs] “Use the Insomnia CLI to automate the execution of your API tests using your existing Git workflows.”
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “Unlimited access to plugins or build your own”
- [probe] “official CLI documented at https://developer.konghq.com/inso-cli/”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to HoppscotchHoppscotch docs explicitly reference AI features including renaming API requests, generating structured request payloads, and scripting for pre-request/test logic, which count as AI-generated suggestions inside the product. However, evidence does not show deeper 'insights' from data (e.g., analyzing response data, anomaly detection, test result summarization) beyond these request-authoring helpers, and there's no independent/hands-on corroboration of these AI features' quality. missing for 10: evidence of AI-generated insights from response/test data (not just request scaffolding), independent user validation of AI feature usefulness.
- [claimed-docs] “These include renaming of API requests, generation of structured request payloads, and scripting capabilities for pre-request logic and test…”
Insomnia has narrow, specific AI features—generating mock servers from prompts/OpenAPI/URL and suggesting Git commit messages—but no evidence of AI analyzing request/response data to surface insights, debugging suggestions, or pattern recognition across a user's API data. Missing for 10: AI-driven analysis of actual request/response payloads, error/anomaly insights, or usage-pattern suggestions beyond mock generation and commit messages.
- [claimed-docs] “Creates a mock server from a prompt, OpenAPI definition, or live URL response. Automatically scaffolds routes, responses, and configurations…”
- [claimed-docs] “Auto-generate a mock server from a natural language prompt and one of the following input types: URL, OpenAPI, or JSON.”
- [claimed-docs] “AI-assisted mock server generation, which transforms prompts or API definitions into mock APIs.”
- [claimed-docs] “AI commit message suggestions, which help maintain clear and atomic commit histories.”
- [claimed-docs] “AI commit message suggestions, which help”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to HoppscotchHoppscotch's CLI supports running API tests/monitoring from the terminal, which can be scheduled via external cron/CI systems, but this requires an external scheduler rather than a native autonomous background automation/trigger system built into the product. There's no evidence of built-in schedulers, webhooks-triggered runs, or agent-orchestrated autonomous workflows. missing for 10: native scheduling/trigger engine, evidence of autonomous background execution without external cron/CI, monitoring automation details, independent confirmation of unattended runs.
- [claimed-docs] “Use the Hoppscotch CLI to run API tests, automate monitoring, and manage collections from your terminal.”
- [claimed-docs] “With the command-line interface (CLI) you can interact with the Hoppscotch platform using a terminal, or through an automated system. This e…”
- [probe] “official CLI documented at https://docs.hoppscotch.io/documentation/clients/cli/overview”
Insomnianone0/10Insomnia offers CI-triggered test automation via Inso CLI and manual Collection Runner runs, but there is no evidence of autonomous, self-scheduling background automations (e.g., cron-like triggers or agents running unattended) — all automation examples require an external CI pipeline or manual invocation.
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “Use the Collection Runner to send multiple requests in a specific order”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to HoppscotchDocs mention built-in AI features (auto-renaming requests, generating structured request payloads, and scripting for pre-request/test logic), showing some in-product AI delegation of specific tasks, but there's no evidence of a general-purpose conversational AI assistant that a user can delegate broader tasks to. Missing for 10: detailed documentation of assistant scope/UI, examples of multi-step task delegation, and independent/hands-on corroboration of these AI features in use.
- [claimed-docs] “These include renaming of API requests, generation of structured request payloads, and scripting capabilities for pre-request logic and test…”
Insomnia does ship some built-in AI features—generating mock servers from a natural-language prompt/OpenAPI spec (insomnia-docs-10, insomnia-docs-29, insomnia-docs-51) and AI-generated commit message suggestions (insomnia-docs-35, insomnia-docs-52)—but these are narrow, single-purpose AI helpers rather than a general-purpose assistant to which a user can delegate broader tasks (e.g., writing tests, debugging requests, multi-step workflows). Missing for 10: evidence of a general conversational/agentic AI assistant embedded in the app, ability to delegate arbitrary tasks beyond mock/commit generation, and independent/hands-on confirmation of these AI features' quality.
- [claimed-docs] “Creates a mock server from a prompt, OpenAPI definition, or live URL response. Automatically scaffolds routes, responses, and configurations…”
- [claimed-docs] “Auto-generate a mock server from a natural language prompt and one of the following input types: URL, OpenAPI, or JSON.”
- [claimed-docs] “AI-assisted mock server generation, which transforms prompts or API definitions into mock APIs.”
- [claimed-docs] “AI commit message suggestions, which help maintain clear and atomic commit histories.”
- [claimed-docs] “AI commit message suggestions, which help”
ai-native userOperate the product with natural-language commands
weight 2 · round to HoppscotchHoppscotch ships an official MCP server that hands an AI agent read/write access to collections, requests, environments and teams and lets it send real HTTP requests, effectively letting a natural-language-driven agent operate the product (hoppscotch-docs-10, hoppscotch-docs-22, hoppscotch-probe-3). There's also a docs page on in-app 'AI features' covering request renaming, payload generation, and script generation, suggesting some native NL-assisted actions (hoppscotch-docs-23). However, the MCP path requires an external AI client/agent rather than a built-in chat interface, and the AI-features doc is only a single thin line with no concrete examples or independent corroboration. Missing for 10: a first-party in-app natural-language command bar/chat demonstrated end-to-end, richer documentation/examples of the AI features, and independent/hands-on confirmation that these NL capabilities work as described.
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you.”
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you. It also sends real HTTP…”
- [claimed-docs] “These include renaming of API requests, generation of structured request payloads, and scripting capabilities for pre-request logic and test…”
- [probe] “official MCP server documented at https://docs.hoppscotch.io/documentation/clients/mcp-server/overview”
Insomnia offers targeted AI/natural-language features—generating a mock server from a natural-language prompt and AI-assisted commit message suggestions—but there is no evidence of broader natural-language command control over core operations like creating/running requests, collections, or environments. Missing for 10: NL-driven request creation/execution, NL-based test/collection running, general chat-style control of the app, and independent verification of the AI features' reliability.
- [claimed-docs] “Creates a mock server from a prompt, OpenAPI definition, or live URL response. Automatically scaffolds routes, responses, and configurations…”
- [claimed-docs] “Auto-generate a mock server from a natural language prompt and one of the following input types: URL, OpenAPI, or JSON.”
- [claimed-docs] “AI commit message suggestions, which help maintain clear and atomic commit histories.”
- [claimed-docs] “AI-assisted mock server generation, which transforms prompts or API definitions into mock APIs.”
- [claimed-docs] “AI commit message suggestions, which help”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnHoppscotch's Embed feature lets users create a mini-version of Hoppscotch embeddable in HTML pages so an audience can interact with API requests, which is a form of interactive, runnable API reference, and OpenAPI import can seed collections for such a reference. However there is no evidence of a dedicated 'API reference/documentation' generator with narrative docs plus embedded runnable examples (like Swagger UI or Postman's published docs), nor independent corroboration of the Embed feature in practice. Missing for 10: auto-generated narrative API reference pages, publishing/sharing workflow for such references, hands-on validation of the Embed feature.
- [claimed-docs] “Embed: Create a mini-version of Hoppscotch that you can embed in an HTML page, allowing your audience to interact with your API request.”
- [claimed-docs] “Use tags as folders when importing from OpenAPI.”
- [claimed-docs] “You can enter the API endpoint and choose the HTTP method according to your needs from the dropdown menu. Once it is configured, click on th…”
Insomnia lets users import OpenAPI/Swagger specs, preview them with linting, auto-generate code snippets in 12+ languages, and directly send/run requests against the spec — effectively turning any imported API spec into an interactive, runnable reference (insomnia-docs-16, insomnia-docs-17, insomnia-docs-18, insomnia-docs-5, insomnia-docs-48). However this requires manually importing a spec rather than offering a built-in, browsable reference experience, and there's no evidence of a dedicated 'try-it-out' documentation portal or AI-native example runner. Missing for 10: a first-party interactive documentation/reference viewer (vs. spec design+testing workflow), and independent/hands-on evidence of this specific 'explore reference with runnable examples' flow.
- [claimed-docs] “View a generated preview of your spec in the right pane.”
- [claimed-docs] “Automatically linted. Errors display at the bottom of the center pane and include error type, line number, and error message”
- [claimed-docs] “Generate code snippets automatically in over 12 different programming languages.”
- [claimed-docs] “Build and iterate on your OpenAPI specs to design your next API.”
- [claimed-docs] “Import a Postman collection or OpenAPI spec into Insomnia Method: UI → Import → choose File/Clipboard/URL.”
- [claimed-docs] “Use the Collection Runner to send multiple requests in a specific order”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to InsomniaHoppscotchnone0/10A direct probe for OpenAPI/Swagger specs at the Hoppscotch docs domain returned 404 on all candidate paths, and no other evidence shows a downloadable machine-readable spec of Hoppscotch's own API surface (the only OpenAPI-related mention is about importing external OpenAPI specs into Hoppscotch, not exposing one).
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.hoppscotch.io/openapi.json, https://docs.hoppscotch.io/swagger.json, https://docs.hopps…”
- [claimed-docs] “Use tags as folders when importing from OpenAPI.”
Insomnia's Design Hub lets users build/iterate OpenAPI specs, preview and lint them, and export/import in OpenAPI 3.0/3.1 (plus Swagger, Postman, HAR formats), and the Inso CLI can lint specs in CI (`inso lint spec`). This directly delivers a machine-readable, downloadable spec workflow. Missing for 10: no independent/hands-on confirmation of the export UX or format fidelity, and the Kong docs site itself has no discoverable OpenAPI spec (probe-3), slightly muddying 'AI-native' machine-readability of the docs layer.
- [claimed-docs] “Build and iterate on your OpenAPI specs to design your next API.”
- [claimed-docs] “Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “View a generated preview of your spec in the right pane.”
- [claimed-docs] “Automatically linted. Errors display at the bottom of the center pane and include error type, line number, and error message”
- [claimed-docs] “Import formats: Insomnia JSON (v4), Insomnia YAML (v5), Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “Import a Postman collection or OpenAPI spec into Insomnia Method: UI → Import → choose File/Clipboard/URL.”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round to InsomniaHoppscotch supports environment/variable management (including secret variables) and the MCP server exposes environments/collections to agents so a sandbox environment could in principle be selected, but there is no explicit feature or documentation describing isolation, safety checks, or a dedicated 'sandbox vs production' mode that prevents an agent from touching production data — the MCP docs even note it 'sends real HTTP requests.' Missing for 10: explicit sandbox-environment safeguard/isolation feature, documentation of environment-scoped access control for agents, and independent evidence confirming this prevents production impact.
- [claimed-docs] “Secret variables in environments.”
- [claimed-docs] “Request variables.”
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you. It also sends real HTTP…”
- [probe] “official MCP server documented at https://docs.hoppscotch.io/documentation/clients/mcp-server/overview”
Insomnia supports mock servers (including AI-generated ones from a prompt/OpenAPI spec) and environment variables that can separate dev/staging/production configs, letting users test flows without hitting real production endpoints. However, there is no explicit 'sandbox environment' feature or documented guarantee of production-data isolation — it relies on users manually configuring mock servers/environments rather than a dedicated sandboxed testing mode. Missing for 10: an explicit sandbox/staging isolation feature, documentation guaranteeing no production data exposure, and independent evidence of AI agents using this for safe testing.
- [claimed-docs] “The Insomnia Cloud mock servers allow you to create a mock endpoint in a few steps.”
- [claimed-docs] “Creates a mock server from a prompt, OpenAPI definition, or live URL response. Automatically scaffolds routes, responses, and configurations…”
- [claimed-docs] “Dynamic mocking renders Liquid templates so responses can include: - Data from the request (headers, query parameters, path, or body). - Ran…”
- [claimed-docs] “Auto-generate a mock server from a natural language prompt and one of the following input types: URL, OpenAPI, or JSON.”
- [claimed-docs] “Use environments to define groups of variables that Insomnia applies across your requests.”
- [claimed-docs] “Use environments to define groups of variables that Insomnia applies across your requests. For example, you could create variables for base …”
- [claimed-docs] “Global environments, which can be accessed by all collections in a project * Collection environments, which can be accessed by all requests …”
- [claimed-docs] “AI-assisted mock server generation, which transforms prompts or API definitions into mock APIs.”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnHoppscotchnone0/10No evidence of API versioning scheme or documented deprecation policy for Hoppscotch's own APIs/products; changelog shows feature releases but no version numbers or deprecation notices. Missing for 10: versioning scheme documentation, deprecation policy, migration guides, version support timeline.
Insomnianone0/10The evidence pack shows Insomnia has versioned file/import formats (e.g., Insomnia JSON v4/YAML v5, OpenAPI 3.0/3.1) but there is no documentation of a formal versioning scheme or deprecation policy for any Insomnia-exposed API, plugin API, or CLI interface that an AI agent would rely on for stability guarantees.
- [claimed-docs] “Import formats: Insomnia JSON (v4), Insomnia YAML (v5), Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round drawnThe CLI can execute an entire collection of requests in one command with JUnit reporting, and the MCP server lets an agent read/change collections, requests, environments, and teams programmatically, both of which support automation-style bulk actions across many items. However, there's no explicit documentation of a dedicated bulk-edit/bulk-delete/bulk-update operation spanning many items at once (e.g. batch renaming, batch parameter changes) beyond running/exporting collections. missing for 10: explicit bulk edit/update/delete API or UI across many requests/items simultaneously, independent hands-on confirmation of large-scale automation runs.
- [claimed-docs] “Use the Hoppscotch CLI to run API tests, automate monitoring, and manage collections from your terminal.”
- [claimed-docs] “The hopp test command now has the ability to generate a JUnit Report for collection runs in the CLI.”
- [claimed-docs] “With the command-line interface (CLI) you can interact with the Hoppscotch platform using a terminal, or through an automated system. This e…”
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you. It also sends real HTTP…”
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you.”
Insomnia's Collection Runner and unlimited collection runs let users execute many requests/tests in bulk, and the Inso CLI automates this across CI pipelines, giving solid bulk-execution support (insomnia-docs-4, insomnia-docs-20, insomnia-docs-39, insomnia-docs-53, insomnia-docs-55). However, evidence is limited to running/testing many requests together—there's no documented bulk editing, bulk tagging, or bulk deletion of items, and no independent/hands-on confirmation of this specific bulk workflow. Missing for 10: evidence of bulk editing/management of many items beyond execution, and independent corroboration of the Collection Runner/Inso CLI bulk workflow.
- [claimed-docs] “Automatically test multiple requests in your collections, with unlimited collection runs.”
- [claimed-docs] “Use the Collection Runner to send multiple requests in a specific order”
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “Unlimited collection runs * Unlimited environments”
- [claimed-docs] “Test complex workflows by chaining the responses from requests together”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to InsomniaHoppscotchnone0/10Hoppscotch offers pre-request/test scripts (gh-5) and a CLI for scheduled/automated test runs (docs-8, docs-21), but there is no evidence of a rules engine or event-triggered automation (e.g., 'when X happens, do Y') as described in the story.
Insomnia supports pre-request and after-response scripts that automatically execute logic tied to request lifecycle events, plus chained requests and CI-triggered automation via the Inso CLI, which constitutes a form of automatic action-on-event behavior. However, there is no evidence of a general-purpose rule/trigger system for arbitrary events (e.g., webhooks, scheduled triggers, or cross-tool event listeners) beyond the request-send/response lifecycle. missing for 10: evidence of a broader event-trigger/rule engine beyond request scripting, and independent confirmation of automation reliability.
- [claimed-docs] “Pre-request scripts allow you to execute tasks before a request is sent.”
- [claimed-docs] “Pre-request scripts allow you to execute tasks before a request is sent. They can be used to: * Manipulate environment variables or authenti…”
- [claimed-docs] “Pre-request and after-response scripting to add logic to your requests”
- [claimed-docs] “Test complex workflows by chaining the responses from requests together”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnHoppscotchnone0/10Hoppscotch offers a CLI for running tests/monitoring and an MCP server for agent access, but there is no evidence of any scheduler, cron-like trigger, or recurring workflow orchestration feature — automation still requires an external scheduler (e.g., cron, CI) to invoke the CLI repeatedly. missing for 10: any built-in scheduling/recurrence mechanism, workflow chaining across multiple requests, or trigger-based automation.
- [claimed-docs] “Use the Hoppscotch CLI to run API tests, automate monitoring, and manage collections from your terminal.”
- [claimed-docs] “With the command-line interface (CLI) you can interact with the Hoppscotch platform using a terminal, or through an automated system. This e…”
- [claimed-docs] “The hopp test command now has the ability to generate a JUnit Report for collection runs in the CLI.”
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you. It also sends real HTTP…”
Insomnianone0/10Insomnia offers Inso CLI for CI-triggered test runs and collection runners, but there is no evidence of any built-in scheduler or recurring-job feature (e.g., cron-like monitors) comparable to what competitors offer; scheduling would have to be bolted on via external CI cron jobs, which isn't documented as part of Insomnia itself.
ai-native userVersion, review, and roll back my automations
weight 1 · round to InsomniaHoppscotchnone0/10No evidence Hoppscotch offers versioning, review workflows, or rollback for automations/scripts/collections; a GitHub issue explicitly requests git-friendly storage/sync as an unmet feature, indicating this capability doesn't exist today.
- [community] “Would be nice to sync storage over git. My team runs into this problem with Postman and any other web request UI out there - that the web re…”
Insomnia's Git Sync connects collections/environments directly to a Git repo, offers a merge view to review and resolve conflicts, and lets you convert projects between Local Vault, Cloud Sync, and Git Sync — giving version history and review workflows for automations (collections, scripts, environments). Rollback is implied via standard Git history rather than a dedicated in-app rollback UI. Missing for 10: explicit in-app rollback/versioned-restore feature beyond relying on external Git tooling, and independent hands-on confirmation of the merge/review workflow in practice.
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “Insomnia opens a merge view so you can review and resolve conflicts without leaving the app.”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository. Insomnia does not host or manage it.”
- [claimed-docs] “Collaboratively create APIs with an unlimited number of contributors (free accounts allow unlimited contributors on one project) and git ver…”
- [claimed-docs] “You can convert a project to: - Local Vault - Cloud Sync - Git Sync”
- [claimed-docs] “You can convert a project to: Local Vault, Cloud Sync, Git Sync”
- [github] “Git Sync: for Git storage using any 3rd party Git repository, without going through the cloud.”
Ci scripting — stories about ci scripting in this arenaCi scripting
Stories about ci scripting in this arena
Ci
developerRun my API test collections in CI with a CLI and fail the build on regressions
weight 3 · round to InsomniaHoppscotch ships an official CLI (hopp) explicitly documented for running API test collections and automated monitoring from the terminal, with JUnit report generation for CI integration (hoppscotch-docs-8, hoppscotch-docs-9, hoppscotch-docs-21, hoppscotch-probe-4). However, the evidence never explicitly documents exit-code/fail-on-regression behavior or shows independent hands-on CI pipeline examples. Missing for 10: explicit documentation of non-zero exit codes on test failure, and independent/community confirmation of CI usage.
- [claimed-docs] “Use the Hoppscotch CLI to run API tests, automate monitoring, and manage collections from your terminal.”
- [claimed-docs] “The hopp test command now has the ability to generate a JUnit Report for collection runs in the CLI.”
- [claimed-docs] “With the command-line interface (CLI) you can interact with the Hoppscotch platform using a terminal, or through an automated system. This e…”
- [probe] “official CLI documented at https://docs.hoppscotch.io/documentation/clients/cli/overview”
Insomnia's docs explicitly describe the Inso CLI as designed for CI environments with disabled prompts and pass/fail exit codes, plus commands like 'inso lint spec' to fail builds on errors, and general CLI automation of test collections tied to Git workflows. missing for 10: independent/hands-on confirmation of CI CLI reliability, real-world CI pipeline examples beyond vendor docs
- [claimed-docs] “Use the Insomnia CLI to automate the execution of your API tests using your existing Git workflows.”
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [probe] “official CLI documented at https://developer.konghq.com/inso-cli/”
Monitors
developerSchedule collection runs as monitors that alert me when an API breaks
weight 2 · round drawnHoppscotch's CLI docs mention the ability to 'automate monitoring' and 'manage automated API monitoring' via collection runs, implying it can be scripted/scheduled externally (e.g., via cron/CI) to catch API failures, and can output JUnit reports for CI integration. However, there is no evidence of a built-in monitor scheduler or native alerting/notification mechanism (email, Slack, webhook) when a run fails. Missing for 10: dedicated 'Monitors' feature with scheduling UI, built-in alert/notification delivery on failure, independent confirmation of this workflow.
- [claimed-docs] “Use the Hoppscotch CLI to run API tests, automate monitoring, and manage collections from your terminal.”
- [claimed-docs] “With the command-line interface (CLI) you can interact with the Hoppscotch platform using a terminal, or through an automated system. This e…”
- [claimed-docs] “The hopp test command now has the ability to generate a JUnit Report for collection runs in the CLI.”
Insomnia's Inso CLI can run collection tests in CI with exit codes to pass/fail builds, and can lint OpenAPI specs to fail builds on errors, which developers could wire into a scheduled CI job to approximate a monitor. However, there is no evidence of a native scheduling feature or built-in alerting mechanism (email/Slack/webhook) for failed runs, unlike a dedicated Monitors product — the burden of scheduling and alerting falls on external CI tooling. missing for 10: native monitor scheduling UI, built-in alert/notification channel on failure, and any hands-on confirmation this workflow is used for uptime-style monitoring.
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
- [claimed-docs] “Use the Collection Runner to send multiple requests in a specific order”
- [claimed-docs] “Unlimited collection runs * Unlimited environments”
Scripting
developerScript pre-request and post-response logic to chain requests and massage data
weight 2 · round to HoppscotchGitHub feature list explicitly confirms pre-request scripting ('Snippets of code... executed before the request is sent'), and the AI-features doc mentions 'scripting capabilities for pre-request logic and test cases', implying post-response test scripts exist too. However, no dedicated documentation details post-response script syntax, variable-setting APIs, or examples of chaining/massaging data across requests. missing for 10: explicit post-response/test-script documentation, examples of setting/reading environment variables between chained requests, independent hands-on confirmation of scripting workflow.
- [github] “Snippets of code associated with a request that is executed before the request is sent.”
- [claimed-docs] “These include renaming of API requests, generation of structured request payloads, and scripting capabilities for pre-request logic and test…”
Insomniadisputedcontradicted6/10Docs clearly document pre-request and after-response scripting, chaining responses across requests, environment variables, and CI automation via Inso CLI (insomnia-docs-2, -21, -37, -38, -39, -53), which directly matches the story. However, a hands-on community comment contradicts this, calling Insomnia's scripting/glue-code support 'garbage-tier' compared to Postman (insomnia-comm-15), indicating the scripting capability may be weaker or less mature in practice than the docs suggest. Missing for 10: independent verification of scripting robustness/parity with competitors, and more recent hands-on confirmation resolving the community critique.
- [claimed-docs] “Pre-request scripts allow you to execute tasks before a request is sent.”
- [claimed-docs] “Pre-request scripts allow you to execute tasks before a request is sent. They can be used to: * Manipulate environment variables or authenti…”
- [claimed-docs] “Pre-request and after-response scripting to add logic to your requests”
- [claimed-docs] “Test complex workflows by chaining the responses from requests together”
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [community] “'Even insomnia had garbage-tier glue code support, something that was very much missing coming from Postman,' notes a user comparing scripti…”
Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaboration
Working as a team — sharing, comments, roles, simultaneous editing
Access control
platform-engineerControl who can view or edit APIs and collections with roles and permissions
weight 2 · round to InsomniaHoppscotch has team collaboration features and an admin dashboard with 'enhanced user management' plus enterprise SSO/audit logs, implying some access-control capability, but there is no explicit documentation of granular roles/permissions for viewing vs editing specific APIs or collections. missing for 10: explicit role/permission model docs (e.g. viewer vs editor roles per collection), evidence of enforcement, independent confirmation of granular access control.
- [github] “Helps you collaborate across your teams to design, develop, and test APIs faster.”
- [claimed-docs] “Enhanced user management in admin dashboard.”
- [claimed-docs] “You can manage your server configurations directly from the self-host admin dashboard.”
- [claimed-docs] “SAML-based SSO, on-prem deployment, audit logs, and more.”
Insomnia documents RBAC for fine-grained control over Insomnia resources and organizations for secure collaboration/sharing, plus SAML 2.0 SSO for identity, directly matching the platform-engineer's need to control who can view/edit APIs and collections. However, there's no detail on granularity (e.g., per-collection vs per-project roles), no independent/hands-on validation of RBAC in practice, and it's gated behind paid tiers per pricing page rather than shown in a workflow. Missing for 10: detailed documentation on role granularity/permission scopes for collections specifically, independent or community validation that RBAC works as described, and any hands-on walkthrough of setting collection-level permissions.
- [claimed-docs] “Use Role-based access control (RBAC) for fine-grain control over who can access which Insomnia resources.”
- [claimed-docs] “Role-based access control (RBAC)”
- [claimed-docs] “Insomnia organizations allows users to share collections and environments safely and securely with their colleagues.”
- [claimed-docs] “You can use any identity provider (IdP) that supports SAML 2.0.”
Api catalog
platform-engineerPublish an internal catalog or portal where teams discover and consume our APIs
weight 2 · round to HoppscotchHoppscotch offers an 'Embed' feature to expose a mini API-interaction UI in a page and team/collection sharing for collaboration, which can serve as a lightweight internal portal, but there is no dedicated catalog/discovery portal product (no API marketplace, search, or documentation-portal feature) documented. missing for 10: a dedicated API catalog/portal product, discovery/search across published APIs, and evidence of teams actually using it as an internal developer portal.
- [claimed-docs] “Embed: Create a mini-version of Hoppscotch that you can embed in an HTML page, allowing your audience to interact with your API request.”
- [github] “Helps you collaborate across your teams to design, develop, and test APIs faster.”
- [claimed-docs] “You can add multiple requests to a collection and even create subfolders inside a collection to further organize your requests.”
Insomnianone0/10Insomnia's evidence covers request collaboration, organizations, Git sync, and RBAC for sharing collections among teammates inside the app, but nothing describes a published catalog or developer portal for broader API discovery/consumption by other teams. missing for 10: any mention of a public/internal API catalog, developer portal, or discovery UI outside the Insomnia app itself.
- [claimed-docs] “Insomnia organizations allows users to share collections and environments safely and securely with their colleagues.”
- [claimed-docs] “Use Role-based access control (RBAC) for fine-grain control over who can access which Insomnia resources.”
- [claimed-docs] “Collaboratively create APIs with an unlimited number of contributors (free accounts allow unlimited contributors on one project) and git ver…”
Team workspaces
developerShare collections with my team in a synced shared workspace
weight 3 · round to InsomniaHoppscotch documents Teams/workspace collaboration features (shared collections, headers/auth applied at collection level, admin dashboard, SSO) and GitHub explicitly claims it 'helps you collaborate across your teams to design, develop, and test APIs faster,' with community evidence confirming easy collection sharing. However, evidence also surfaces real gaps: a feature request shows syncing/storage across teams (e.g., git-based sync) is unmet, self-hosted login/workspace sync in the desktop app is limited, and some enterprise-grade sync features (SSO, audit logs) are gated behind paid tiers. Missing for 10: independent verification of real-time sync fidelity across team members, clarity on offline/desktop workspace sync limitations, and confirmation that core sharing works without hitting paywalled features.
- [github] “Helps you collaborate across your teams to design, develop, and test APIs faster.”
- [claimed-docs] “When you add a header or auth to a collection, it will be applied to all requests in that collection.”
- [community] “Love hoppscotch! Moved to it from postman back in the postwoman days. They really cleaned up the UI recently, made saving and sharing collec…”
- [community] “It has a clean UI and can be self-hosted. The downside is - Only one workspace is available when offline. You can't point your Workspace dat…”
- [community] “Would be nice to sync storage over git. My team runs into this problem with Postman and any other web request UI out there - that the web re…”
- [claimed-docs] “SAML-based SSO, on-prem deployment, audit logs, and more.”
Insomnia organizations support sharing collections/environments securely with colleagues, with RBAC, Cloud Sync, and Git Sync as alternate sync backends, plus merge conflict resolution for team workflows. missing for 10: independent/hands-on evidence of team sync experience (community comments focus on rug-pull login requirement and lightweight vs bloat, not team sync workflow specifics), and no detail on real-time collaboration limits or seat/team size constraints.
- [claimed-docs] “Insomnia organizations allows users to share collections and environments safely and securely with their colleagues.”
- [claimed-docs] “Use Role-based access control (RBAC) for fine-grain control over who can access which Insomnia resources.”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “Insomnia opens a merge view so you can review and resolve conflicts without leaving the app.”
- [claimed-docs] “You can convert a project to: - Local Vault - Cloud Sync - Git Sync”
- [claimed-docs] “Collaboratively create APIs with an unlimited number of contributors (free accounts allow unlimited contributors on one project) and git ver…”
- [claimed-docs] “At no point in the sync process can the Insomnia servers read or access sensitive application project data.”
Collections workspaces — stories about collections workspaces in this arenaCollections workspaces
Stories about collections workspaces in this arena
Collections
developerStore collections as plain text files in my repo and version them with git
weight 3 · round to InsomniaHoppscotchnone0/10There is no evidence Hoppscotch stores collections as plain-text files suitable for git version control; instead, community evidence explicitly shows this is a requested-but-unimplemented feature (an open GitHub issue asking Hoppscotch to make storage git-friendly) and a comparison noting Bruno supports directory-based storage while Hoppscotch does not let you point a workspace to a specific directory.
- [community] “Would be nice to sync storage over git. My team runs into this problem with Postman and any other web request UI out there - that the web re…”
- [community] “It has a clean UI and can be self-hosted. The downside is - Only one workspace is available when offline. You can't point your Workspace dat…”
Insomnia's Git Sync feature explicitly stores project/collection data directly in a user's own Git repository as files (not on Insomnia's servers), supports merge conflict resolution, and can be toggled per-project alongside Cloud/Local storage — directly matching the story. Documentation also confirms this is a longstanding, git-native workflow (git version control mentioned for collaborative API design) and the GitHub README corroborates 'Git Sync: for Git storage using any 3rd party Git repository.' Missing for 10: independent hands-on confirmation of the exact plain-text file format on disk and no community verification of git-diff friendliness.
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “Insomnia opens a merge view so you can review and resolve conflicts without leaving the app.”
- [claimed-docs] “You can convert a project to: - Local Vault - Cloud Sync - Git Sync”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository. Insomnia does not host or manage it.”
- [claimed-docs] “You can convert a project to: Local Vault, Cloud Sync, Git Sync”
- [claimed-docs] “Collaboratively create APIs with an unlimited number of contributors (free accounts allow unlimited contributors on one project) and git ver…”
- [github] “Git Sync: for Git storage using any 3rd party Git repository, without going through the cloud.”
developerImport and export collections in portable formats to move between tools
weight 2 · round to InsomniaDocs and GitHub evidence show robust import support (cURL import, OpenAPI import with tag-based folder organization, collections/folders organization) but there is no explicit documentation of exporting collections to portable formats, and a community feature request (git-friendly storage sync) suggests export/interop is limited. missing for 10: explicit export-to-file/format documentation, independent confirmation of round-trip export/import between tools like Postman.
- [github] “Import cURL”
- [github] “Import `cURL`”
- [claimed-docs] “Use tags as folders when importing from OpenAPI.”
- [github] “Keep your API requests organized with collections and folders. Reuse them with a single click.”
- [community] “Love hoppscotch! Moved to it from postman back in the postwoman days. They really cleaned up the UI recently, made saving and sharing collec…”
- [community] “Would be nice to sync storage over git. My team runs into this problem with Postman and any other web request UI out there - that the web re…”
Docs explicitly detail import/export in multiple portable formats (Insomnia JSON/YAML, Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, cURL) with UI import methods and Inso CLI support for automation/CI, plus Git Sync for version-controlled portability across tools. Missing for 10: no independent hands-on verification of round-trip fidelity between tools beyond vendor docs.
- [claimed-docs] “Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “Import formats: Insomnia JSON (v4), Insomnia YAML (v5), Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “Import a Postman collection or OpenAPI spec into Insomnia Method: UI → Import → choose File/Clipboard/URL.”
- [claimed-docs] “Import your tests from Postman”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
developerOrganize API requests into collections and folders and rerun them anytime
weight 3 · round drawnHoppscotch explicitly documents organizing requests into collections and subfolders, reusing them with a single click, and applying shared headers/auth at the collection level, backed by both first-party docs and GitHub feature list; community reviews corroborate collections/saving as a core, easy-to-use feature. Missing for 10: deeper independent hands-on evidence of long-term rerun workflows across large collections.
- [claimed-docs] “You can add multiple requests to a collection and even create subfolders inside a collection to further organize your requests.”
- [claimed-docs] “When you add a header or auth to a collection, it will be applied to all requests in that collection.”
- [github] “Keep your API requests organized with collections and folders. Reuse them with a single click.”
- [community] “Love hoppscotch! Moved to it from postman back in the postwoman days. They really cleaned up the UI recently, made saving and sharing collec…”
Insomnia's docs clearly show organizing requests into collections/folders, with Collection Runner to rerun multiple requests in order, unlimited collection runs, environments scoped to collections/folders, and persistent storage via Git Sync/Cloud Sync for rerunning anytime. Community evidence corroborates long-term real-world use of saved/frequently-used requests. Missing for 10: independent hands-on verification specifically of folder-nesting UX and rerun reliability at scale beyond vendor docs.
- [claimed-docs] “Use the Collection Runner to send multiple requests in a specific order”
- [claimed-docs] “Automatically test multiple requests in your collections, with unlimited collection runs.”
- [claimed-docs] “Unlimited collection runs * Unlimited environments”
- [claimed-docs] “Use environments to define groups of variables that Insomnia applies across your requests.”
- [claimed-docs] “Global environments, which can be accessed by all collections in a project * Collection environments, which can be accessed by all requests …”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [community] “I've been using [cocoa-rest-client] for a couple of years, I just tried Insomnia and I think I'll be switching: having the ability to call f…”
Offline
developerWork fully offline in a local workspace without a cloud account
weight 2 · round to HoppscotchHoppscotch offers a desktop app, installable PWA, and self-hosted deployment with login clearly optional (hoppscotch-docs-29, hoppscotch-docs-13, hoppscotch-comm-9), supporting local/offline use without a cloud account. However, hands-on community evidence shows real limits: 'Only one workspace is available when offline. You can't point your Workspace data to a specific directory like bruno does. Self-hosting login is not possible in the desktop app' (hoppscotch-comm-10), and installing self-hosted locally was reported as unclear/undocumented at one point (hoppscotch-comm-2, hoppscotch-comm-3). Missing for 10: multi-workspace offline support, directory-based local workspace storage, and clearer first-party docs/independent confirmation of a fully-featured offline-only workflow.
- [claimed-docs] “Hoppscotch Desktop App is a cross-platform desktop application that helps you create and manage API requests.”
- [claimed-docs] “No installation is required.”
- [community] “Nice. Downloaded and installed. Clean UI (almost bordering on a rip-off of Postman.. but I guess familiarity helps users get going faster). …”
- [community] “It has a clean UI and can be self-hosted. The downside is - Only one workspace is available when offline. You can't point your Workspace dat…”
- [community] “Am I going crazy or is there no way to install this locally apart from a 'development' setup with git clone or docker?”
Insomniadisputedcontradicted5/10Insomnia's docs describe offline-friendly options — Scratch Pad requires 'No login ever required' (insomnia-docs-31), a 'Local Vault' project-storage mode (insomnia-docs-32/45), and Git Sync that keeps data in the user's own repo without touching Insomnia's cloud (insomnia-gh-1, insomnia-docs-22/44). However, a first-hand community report states the main Insomnia REST client 'now requires an account,' prompting users to call it a 'rug pull' and switch to fully offline-first alternatives like Bruno (insomnia-comm-14), directly contradicting the no-account claim for general (non-Scratch-Pad) usage. missing for 10: clear vendor confirmation that the main workspace (not just Scratch Pad) can be used indefinitely without ever creating a cloud account, and independent hands-on verification resolving the community complaint.
- [claimed-docs] “No login ever required for Scratch Pad”
- [claimed-docs] “You can convert a project to: - Local Vault - Cloud Sync - Git Sync”
- [claimed-docs] “You can convert a project to: Local Vault, Cloud Sync, Git Sync”
- [github] “Git Sync: for Git storage using any 3rd party Git repository, without going through the cloud.”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository. Insomnia does not host or manage it.”
- [community] “Insomnia REST client now requires an account, prompting users to seek alternatives; one commenter says 'Tired of these rug pulls' and lists …”
Protocols
developerSend GraphQL, gRPC, WebSocket, and SSE requests, not just REST
weight 2 · round to InsomniaGitHub evidence explicitly confirms GraphQL support and full-duplex (WebSocket-like) communication over a single TCP connection, but there's no direct evidence for gRPC or SSE support, and no independent/hands-on corroboration of actually sending requests via these protocols. missing for 10: explicit gRPC support evidence, SSE support evidence, hands-on confirmation of sending GraphQL/WebSocket requests.
Docs explicitly confirm HTTP, gRPC, GraphQL, and WebSocket request support (insomnia-docs-15, insomnia-docs-7/43, insomnia-docs-26), with GraphQL type-aware autocomplete and gRPC protobuf upload support. SSE is not explicitly named in the docs, though WebSocket/streaming support is documented. missing for 10: explicit SSE (Server-Sent Events) documentation, independent hands-on corroboration of multi-protocol usage.
- [claimed-docs] “With Insomnia, you can send requests via HTTP, gRPC, GraphQL, and WebSockets.”
- [claimed-docs] “Insomnia supports making gRPC requests.”
- [claimed-docs] “Insomnia supports making gRPC requests. You can create one by clicking the + button on the left panel of a collection and selecting gRPC Req…”
- [claimed-docs] “Insomnia uses this type system to provide auto-completion and linting of GraphQL queries.”
- [claimed-docs] “Insomnia allows you to upload Protobuf files to a request. You can upload a single file or a directory containing multiple files.”
- [github] “Debug APIs using the most popular protocols and formats.”
Environments secrets — stories about environments secrets in this arenaEnvironments secrets
Stories about environments secrets in this arena
Environments
developerSwitch requests between dev, staging, and prod using environment variable sets
weight 3 · round to InsomniaDocs confirm the existence of an environments system (with secret variables and request variables that resolve within environments), implying multiple environment sets can be defined and swapped, but no direct evidence describes selecting/switching between dev/staging/prod environments or a dropdown UI for env selection. missing for 10: explicit documentation or screenshot of environment switcher UI, workflow for maintaining separate dev/staging/prod variable sets, and independent/community confirmation of this specific switching behavior.
- [claimed-docs] “Secret variables in environments.”
- [claimed-docs] “Request variables.”
Insomnia explicitly supports environments as groups of variables (base URLs, tokens, credentials) with global, collection, and folder-level scoping, enabling switching between dev/staging/prod configurations; unlimited environments are confirmed in pricing docs. Missing for 10: no explicit hands-on/community example of a dev/staging/prod switching workflow, only first-party docs.
- [claimed-docs] “Use environments to define groups of variables that Insomnia applies across your requests.”
- [claimed-docs] “Use environments to define groups of variables that Insomnia applies across your requests. For example, you could create variables for base …”
- [claimed-docs] “Global environments, which can be accessed by all collections in a project * Collection environments, which can be accessed by all requests …”
- [claimed-docs] “Unlimited collection runs * Unlimited environments”
Secrets
platform-engineerKeep credentials out of shared files with masked secrets or an external vault integration
weight 2 · round to InsomniaHoppscotch docs explicitly list 'Secret variables in environments' as a changelog feature, directly matching the masked-secrets need, and self-host docs mention on-prem deployment and audit logs for enterprise-grade control. However, there is no evidence of an external vault integration (e.g., Vault, AWS Secrets Manager) or independent/hands-on confirmation of how secret variables are masked in shared collection files. Missing for 10: external vault/secret-manager integration, hands-on verification that secrets are excluded from exported/shared collection files, and independent corroboration beyond the vendor changelog.
- [claimed-docs] “Secret variables in environments.”
- [claimed-docs] “SAML-based SSO, on-prem deployment, audit logs, and more.”
- [claimed-docs] “Self-host Hoppscotch on your own infrastructure with full data ownership.”
Insomnia explicitly documents external vault integration to retrieve secret values automatically when sending requests, and environments are described as a way to store credentials/tokens without hardcoding them in shared collection files. RBAC and organization-level sharing controls further support keeping secrets scoped safely. Missing for 10: explicit documentation of a 'masked' or obfuscated secret display feature in the UI, and independent/hands-on confirmation that vault integration works reliably in practice.
- [claimed-docs] “Insomnia supports integrating with external vault service providers to retrieve secret values automatically when sending requests.”
- [claimed-docs] “Use environments to define groups of variables that Insomnia applies across your requests. For example, you could create variables for base …”
- [claimed-docs] “Use environments to define groups of variables that Insomnia applies across your requests.”
- [claimed-docs] “Use Role-based access control (RBAC) for fine-grain control over who can access which Insomnia resources.”
Gateway traffic — stories about gateway traffic in this arenaGateway traffic
Stories about gateway traffic in this arena
Gateway ops
platform-engineerManage API infrastructure as declarative config and sync it from CI (GitOps/APIOps)
weight 2 · round to InsomniaHoppscotchnone0/10Hoppscotch offers a CLI for running collections in CI (docs-8) and a self-host admin dashboard for server settings (docs-6), but there is no evidence of declarative, git-syncable configuration for API infrastructure/gateway routing—in fact a long-standing community request for git-friendly collection storage remains unresolved (comm-14), indicating this GitOps/APIOps capability is not delivered.
- [claimed-docs] “Use the Hoppscotch CLI to run API tests, automate monitoring, and manage collections from your terminal.”
- [claimed-docs] “You can manage your server configurations directly from the self-host admin dashboard.”
- [community] “Would be nice to sync storage over git. My team runs into this problem with Postman and any other web request UI out there - that the web re…”
Insomnia supports Git Sync so projects/specs/collections live as files in a Git repo, and Inso CLI is explicitly designed to run in CI (disabling prompts, providing exit codes) to lint OpenAPI specs and run tests as part of pipelines. This gives a real GitOps-style workflow for API design/testing artifacts, but Insomnia manages API client/design/test config, not actual gateway infrastructure (routes, plugins, gateway resources) — that lives in Kong Gateway/Konnect, not Insomnia. Missing for 10: evidence of declaratively managing live gateway/infrastructure resources (not just specs/tests) from Insomnia, and independent/hands-on confirmation of CI pipelines using Inso CLI successfully.
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository. Insomnia does not host or manage it.”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “Automate your tests with Inso CLI”
- [github] “Git Sync: for Git storage using any 3rd party Git repository, without going through the cloud.”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round drawnHoppscotch offers a CLI for running tests/monitoring/collection management and an MCP server that lets an agent read and modify collections, requests, environments, and teams and send real HTTP requests, giving substantial programmatic parity with core UI actions. However, there is no documented general-purpose REST/GraphQL API (probe found no OpenAPI/swagger spec), and features like team collaboration, SSO/admin settings, or UI-specific extras (themes, PWA, client certs) aren't shown as scriptable. Missing for 10: a documented public API covering full UI feature parity, evidence for automating admin/enterprise/team-collab features, and independent confirmation of CLI/MCP completeness.
- [claimed-docs] “Use the Hoppscotch CLI to run API tests, automate monitoring, and manage collections from your terminal.”
- [claimed-docs] “With the command-line interface (CLI) you can interact with the Hoppscotch platform using a terminal, or through an automated system. This e…”
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you. It also sends real HTTP…”
- [probe] “official MCP server documented at https://docs.hoppscotch.io/documentation/clients/mcp-server/overview”
- [probe] “official CLI documented at https://docs.hoppscotch.io/documentation/clients/cli/overview”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.hoppscotch.io/openapi.json, https://docs.hoppscotch.io/swagger.json, https://docs.hopps…”
Insomnia ships an official CLI (Inso CLI) that can run collections, lint OpenAPI specs, and automate tests in CI (insomnia-docs-3, -39, -49, -53, insomnia-probe-4), giving CLI/automation parity for a meaningful subset of workflows. However, there's no evidence of a full programmatic/API surface covering all UI capabilities (e.g., AI-assisted mock server creation, GraphQL design/linting, gRPC/Protobuf uploads, environment/Git-sync management, RBAC) — these remain UI-only per the docs. A community comment even flags weak scripting/glue-code support relative to competitors (insomnia-comm-15). missing for 10: CLI/API coverage for mock servers, GraphQL/gRPC workflows, environment & Git sync management, and independent confirmation that Inso CLI matches full UI functionality.
- [claimed-docs] “Use the Insomnia CLI to automate the execution of your API tests using your existing Git workflows.”
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [probe] “official CLI documented at https://developer.konghq.com/inso-cli/”
- [community] “'Even insomnia had garbage-tier glue code support, something that was very much missing coming from Postman,' notes a user comparing scripti…”
ai-native userExport all of my data in open formats and leave
weight 3 · round to InsomniaHoppscotch is fully open-source (MIT) and can be self-hosted with 'full data ownership' (hoppscotch-docs-11, hoppscotch-docs-14, hoppscotch-docs-24), and its CLI/MCP server can read and manage collections, environments and requests in structured form (hoppscotch-docs-8, hoppscotch-docs-10, hoppscotch-docs-22), implying data is accessible outside the UI. However, there is no explicit documentation of a dedicated 'export' feature or open file format (e.g. JSON export of collections) for a user to take their data and leave, only import (cURL, OpenAPI) is explicitly evidenced. missing for 10: explicit export/download-my-data feature documentation, confirmation of an open interchange format for collections/environments, independent confirmation that self-hosted data is fully portable without vendor lock-in.
- [claimed-docs] “Hoppscotch Community Edition is free and open-source. It is licensed under the MIT License.”
- [claimed-docs] “Self-host Hoppscotch on your own infrastructure with full data ownership.”
- [claimed-docs] “For full data ownership and control over your API development and testing, you can self-host Hoppscotch on your infrastructure.”
- [claimed-docs] “Use the Hoppscotch CLI to run API tests, automate monitoring, and manage collections from your terminal.”
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you.”
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you. It also sends real HTTP…”
- [github] “Import cURL”
Insomnia supports export in multiple open formats (Postman v2, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, cURL, plus its own JSON/YAML) and Git Sync keeps project data in a user-controlled repository rather than locked in a proprietary cloud, giving strong data portability. However, there's no explicit 'export everything' bulk/full-account export guarantee (e.g., all environments, secrets, RBAC configs, org settings) and no independent verification that exported data is fully lossless/complete outside vendor docs. missing for 10: evidence of a comprehensive full-account/workspace export (not just collections), independent/hands-on confirmation of lossless round-trip export, and documentation on exporting non-collection data like vault secrets or org settings.
- [claimed-docs] “Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “Import formats: Insomnia JSON (v4), Insomnia YAML (v5), Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository. Insomnia does not host or manage it.”
- [github] “Git Sync: for Git storage using any 3rd party Git repository, without going through the cloud.”
- [claimed-docs] “You can convert a project to: - Local Vault - Cloud Sync - Git Sync”
- [claimed-docs] “You can convert a project to: Local Vault, Cloud Sync, Git Sync”
ai-native userRead the product's source under an open license
weight 2 · round drawnHoppscotch's Community Edition source is publicly hosted on GitHub and documented as MIT-licensed, satisfying the 'read source under open license' story with an active, browsable repo (hoppscotch-docs-11, hoppscotch-gh-1..11). Missing for 10: no explicit clarification of licensing for the separate enterprise/self-host admin features, and community commentary notes it is 'open core' with some contributed functionality restricted (hoppscotch-comm-7, hoppscotch-comm-8), which is a scope caveat rather than a contradiction of the core MIT-licensed repo.
- [claimed-docs] “Hoppscotch Community Edition is free and open-source. It is licensed under the MIT License.”
- [github] “Import cURL”
- [community] “I believe both Bruno and Hoppscotch are 'open core' with expensive paid plans for additional/enterprise functionality, and they limit commun…”
- [community] “Going to leave this here for shady practices. A pull request was declined by the CEO since they were planning to build an OIDC feature into …”
The official GitHub repository explicitly ships an Apache-2.0 LICENSE file, confirming Insomnia's source code is available under a recognized open-source license for anyone (including AI-native users) to read. Missing for 10: independent scrutiny of whether all components (e.g., cloud sync backend) are covered by the same license, and no third-party audit confirming license accuracy beyond the repo itself.
- [github] “Apache License Version 2.0, January 2004 — repository LICENSE file; the README's License section states: [Apache-2.0](LICENSE) (c) Insomnia …”
ai-native userSelf-host the core product
weight 3 · round to HoppscotchHoppscotch documents a full self-host path (open-source MIT Community Edition, dedicated self-host getting-started guide, admin dashboard for server config, full data ownership) confirming the core product can run on a user's own infrastructure. Some older community comments note friction in the self-host setup process, but they don't contradict the current documented capability. Missing for 10: independent hands-on verification of a smooth current self-host deployment and more detail on infra requirements/scaling.
- [claimed-docs] “Hoppscotch Community Edition is free and open-source. It is licensed under the MIT License.”
- [claimed-docs] “SAML-based SSO, on-prem deployment, audit logs, and more.”
- [claimed-docs] “Self-host Hoppscotch on your own infrastructure with full data ownership.”
- [claimed-docs] “For full data ownership and control over your API development and testing, you can self-host Hoppscotch on your infrastructure.”
- [claimed-docs] “SAML-based SSO, on-prem deployment, audit logs, and more. Hoppscotch Enterprise Edition is a self-hosted version of Hoppscotch Cloud with en…”
- [claimed-docs] “You can manage your server configurations directly from the self-host admin dashboard.”
- [community] “Am I going crazy or is there no way to install this locally apart from a 'development' setup with git clone or docker?”
- [community] “I only wish they can provide a self-hosting step.”
Insomnia's core client is Apache-2.0 licensed and open source, and Git Sync explicitly keeps all project data in the user's own Git repo with 'Insomnia does not host or manage it,' letting AI-native users avoid the vendor's cloud entirely. However, there is no documented self-hosted server/backend package (e.g., a self-hosted sync or collaboration server) analogous to on-prem deployments some competitors offer—self-hosting here is effectively 'run the open-source desktop client + your own git remote,' not a full self-hosted service stack. Missing for 10: an official self-hosted server/Docker deployment guide, and independent confirmation that self-built/self-hosted setups work end-to-end.
- [github] “Apache License Version 2.0, January 2004 — repository LICENSE file; the README's License section states: [Apache-2.0](LICENSE) (c) Insomnia …”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository. Insomnia does not host or manage it.”
- [claimed-docs] “At no point in the sync process can the Insomnia servers read or access sensitive application project data.”
- [claimed-docs] “You can convert a project to: - Local Vault - Cloud Sync - Git Sync”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round to HoppscotchHoppscotch supports self-hosting on your own infrastructure with 'full data ownership' and on-prem deployment (Enterprise), which indirectly lets users control where their data resides by choosing their own hosting location, rather than offering explicit region-selection within a managed cloud service. missing for 10: an explicit region/residency selector in the hosted Hoppscotch Cloud offering, and independent confirmation of data-location controls.
- [claimed-docs] “Self-host Hoppscotch on your own infrastructure with full data ownership.”
- [claimed-docs] “For full data ownership and control over your API development and testing, you can self-host Hoppscotch on your infrastructure.”
- [claimed-docs] “SAML-based SSO, on-prem deployment, audit logs, and more. Hoppscotch Enterprise Edition is a self-hosted version of Hoppscotch Cloud with en…”
- [claimed-docs] “SAML-based SSO, on-prem deployment, audit logs, and more.”
Insomnia lets users choose storage mode—Local Vault, Cloud Sync, or Git Sync to a self-hosted/3rd-party repo—giving some control over where data physically resides, and Kong states its cloud servers cannot read synced project data. However there is no evidence of selectable geographic region/data-residency options within Insomnia's cloud offering itself. Missing for 10: explicit region selection for cloud-hosted data, documented data-residency/compliance zones, independent confirmation of storage location guarantees.
- [claimed-docs] “You can convert a project to: - Local Vault - Cloud Sync - Git Sync”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “At no point in the sync process can the Insomnia servers read or access sensitive application project data.”
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnHoppscotchnone0/10No evidence in the pack addresses AI-training data usage, opt-out settings, or a privacy policy statement about model training; self-hosting for data ownership is documented but does not speak to whether cloud/AI features use data for training.
Insomnianone0/10Insomnia's docs describe AI features (mock generation, commit suggestions) and data-security claims about sync servers not reading project data, but there is no evidence of any control or policy letting users opt out of their data being used for AI model training.
- [claimed-docs] “At no point in the sync process can the Insomnia servers read or access sensitive application project data.”
- [claimed-docs] “AI-assisted mock server generation, which transforms prompts or API definitions into mock APIs.”
- [claimed-docs] “AI commit message suggestions, which help”
ai-native userControl data retention and deletion
weight 2 · round to InsomniaHoppscotch offers self-hosting with 'full data ownership' and is open-source (MIT), which lets an organization control where data lives and effectively manage retention/deletion by owning the infrastructure. However, there is no explicit documentation of account/data deletion tools, configurable retention periods, or export/erasure APIs for the cloud-hosted version. Missing for 10: explicit data retention/deletion controls or APIs, documented GDPR-style erasure workflow, and independent confirmation that self-hosting alone satisfies deletion requirements.
- [claimed-docs] “Self-host Hoppscotch on your own infrastructure with full data ownership.”
- [claimed-docs] “Hoppscotch Community Edition is free and open-source. It is licensed under the MIT License.”
- [claimed-docs] “SAML-based SSO, on-prem deployment, audit logs, and more.”
Insomnia lets users choose where data lives (Local Vault, Git Sync, Cloud Sync) and states its servers cannot read synced project data, plus a no-login Scratch Pad mode, which gives meaningful control over data storage/retention posture. However there is no explicit documentation of account/data deletion mechanisms, retention periods, or GDPR-style data export/erasure workflows. Missing for 10: explicit data deletion/retention policy documentation, account/data purge controls, independent confirmation of these claims.
- [claimed-docs] “You can convert a project to: - Local Vault - Cloud Sync - Git Sync”
- [claimed-docs] “You can convert a project to: Local Vault, Cloud Sync, Git Sync”
- [claimed-docs] “At no point in the sync process can the Insomnia servers read or access sensitive application project data.”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository. Insomnia does not host or manage it.”
- [claimed-docs] “No login ever required for Scratch Pad”
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnHoppscotchnone0/10No evidence pack item addresses telemetry, analytics, or opt-out settings for Hoppscotch; self-hosting is mentioned as giving 'full data ownership' but that is distinct from an explicit telemetry opt-out control.
Spec design — stories about spec design in this arenaSpec design
Stories about spec design in this arena
Docs generation
developerGenerate and publish API documentation from my collections or specs
weight 2 · round to InsomniaHoppscotchnone0/10Hoppscotch offers OpenAPI import and an 'Embed' feature to share interactive requests, but there is no evidence of an actual documentation-generation/publishing feature from collections or specs; a community review explicitly notes 'Can't create documentation for a folder/request', directly indicating this capability is absent.
- [claimed-docs] “Embed: Create a mini-version of Hoppscotch that you can embed in an HTML page, allowing your audience to interact with your API request.”
- [claimed-docs] “Use tags as folders when importing from OpenAPI.”
- [community] “It has a clean UI and can be self-hosted. The downside is - Only one workspace is available when offline. You can't point your Workspace dat…”
Insomnia's design mode lets you build/iterate on OpenAPI specs, view a generated preview, get linting and auto-generated code snippets in 12+ languages, which serves as a form of documentation generation from specs (insomnia-docs-5, insomnia-docs-16, insomnia-docs-17, insomnia-docs-18). However, there is no evidence of a dedicated 'publish' feature (e.g., hosting a documentation site or public API reference) — only in-app preview and collaborative editing via Git are documented. Missing for 10: a documented publish/export-to-hosted-docs capability, evidence of turning collections (not just specs) into shareable documentation, and any independent confirmation of a publishing workflow.
- [claimed-docs] “Build and iterate on your OpenAPI specs to design your next API.”
- [claimed-docs] “View a generated preview of your spec in the right pane.”
- [claimed-docs] “Automatically linted. Errors display at the bottom of the center pane and include error type, line number, and error message”
- [claimed-docs] “Generate code snippets automatically in over 12 different programming languages.”
- [claimed-docs] “Collaboratively create APIs with an unlimited number of contributors (free accounts allow unlimited contributors on one project) and git ver…”
Governance
platform-engineerLint API specs against configurable style and governance rules
weight 3 · round to InsomniaHoppscotchnone0/10Hoppscotch is an API client/testing tool with request building, collections, CLI test runner, and MCP server, but there is no evidence of spec linting against configurable style/governance rules (e.g., no Spectral-like ruleset engine or OpenAPI governance checks) in any doc, changelog, or CLI feature listed.
Insomnia's Design view auto-lints OpenAPI specs showing error type/line/message (insomnia-docs-17), and the Inso CLI can run 'inso lint spec' in CI to fail builds on errors (insomnia-docs-49, insomnia-docs-53), giving a platform-engineer a way to gate specs on validation issues. However, there is no evidence of configurable style/governance rulesets (e.g., custom rule files, organization-wide style guides, or Spectral-like rule configuration) — the linting appears to be basic schema/structural validation rather than customizable governance policy enforcement. Missing for 10: evidence of configurable lint rule files or style-guide customization, evidence of org-level governance policy enforcement, and independent confirmation the lint rules can be tailored beyond basic OpenAPI validity checks.
- [claimed-docs] “Automatically linted. Errors display at the bottom of the center pane and include error type, line number, and error message”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “View a generated preview of your spec in the right pane.”
Spec import export
developerDesign an API spec-first and export it as OpenAPI
weight 2 · round to InsomniaHoppscotchnone0/10Evidence shows Hoppscotch can import OpenAPI specs (e.g., using tags as folders when importing) but there is no mention of designing an API spec-first and exporting it as OpenAPI; the only OpenAPI-related capability documented is import, not export.
- [claimed-docs] “Use tags as folders when importing from OpenAPI.”
Insomnia has a dedicated 'Design' feature for building OpenAPI specs with live preview, automatic linting, and code-snippet generation, and it supports full import/export of OpenAPI 3.0/3.1 specs (including via the inso CLI for CI linting), directly matching a spec-first workflow with OpenAPI export. missing for 10: independent hands-on validation of the spec-design workflow specifically (community evidence only discusses general client usage, not OpenAPI spec-first design).
- [claimed-docs] “Build and iterate on your OpenAPI specs to design your next API.”
- [claimed-docs] “View a generated preview of your spec in the right pane.”
- [claimed-docs] “Automatically linted. Errors display at the bottom of the center pane and include error type, line number, and error message”
- [claimed-docs] “Generate code snippets automatically in over 12 different programming languages.”
- [claimed-docs] “Collaboratively create APIs with an unlimited number of contributors (free accounts allow unlimited contributors on one project) and git ver…”
- [claimed-docs] “Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “Import formats: Insomnia JSON (v4), Insomnia YAML (v5), Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
- [probe] “official CLI documented at https://developer.konghq.com/inso-cli/”
developerImport an OpenAPI spec to generate requests and collections
weight 3 · round to InsomniaDocs explicitly mention OpenAPI import ('Use tags as folders when importing from OpenAPI') implying native OpenAPI import into collections, alongside cURL import and collection/folder organization features. However, there's no detailed documentation on the full import workflow (e.g., generating requests from spec, handling auth/schemas) or independent/hands-on confirmation of fidelity. missing for 10: detailed OpenAPI import workflow docs, independent/hands-on validation of spec-to-collection accuracy.
- [claimed-docs] “Use tags as folders when importing from OpenAPI.”
- [github] “Keep your API requests organized with collections and folders. Reuse them with a single click.”
- [github] “Import cURL”
Insomnia's docs explicitly list OpenAPI 3.0/3.1 (and Swagger) as supported import formats and describe the UI flow (Import → File/Clipboard/URL) to bring specs into collections, with CI-side linting via `inso lint spec`. missing for 10: independent/hands-on confirmation that OpenAPI import correctly generates requests/collections without manual fixes.
- [claimed-docs] “Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “Import formats: Insomnia JSON (v4), Insomnia YAML (v5), Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “Import a Postman collection or OpenAPI spec into Insomnia Method: UI → Import → choose File/Clipboard/URL.”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
Testing mocking — stories about testing mocking in this arenaTesting mocking
Stories about testing mocking in this arena
Ai assist
ai-native userHave AI generate test cases or assertions for an endpoint from its spec or responses
weight 2 · round to HoppscotchDocs mention AI features that include "scripting capabilities for pre-request logic and test cases," implying AI can help generate test/assertion scripts, but there's no detail on generating tests specifically from an endpoint's spec or response data, nor independent corroboration of this feature in use. Missing for 10: detailed documentation on spec/response-driven test generation, examples of AI-generated assertions, and community/hands-on validation of this specific capability.
- [claimed-docs] “These include renaming of API requests, generation of structured request payloads, and scripting capabilities for pre-request logic and test…”
Insomnianone0/10Insomnia's AI features documented are limited to mock server generation from prompts/specs and AI commit message suggestions; there is no evidence of AI generating test cases or assertions from an endpoint's spec or responses. Testing capabilities (collection runner, pre-request scripts, chaining) are manual, not AI-driven.
- [claimed-docs] “Creates a mock server from a prompt, OpenAPI definition, or live URL response. Automatically scaffolds routes, responses, and configurations…”
- [claimed-docs] “Auto-generate a mock server from a natural language prompt and one of the following input types: URL, OpenAPI, or JSON.”
- [claimed-docs] “AI-assisted mock server generation, which transforms prompts or API definitions into mock APIs.”
- [claimed-docs] “AI commit message suggestions, which help”
- [claimed-docs] “Automatically test multiple requests in your collections, with unlimited collection runs.”
- [claimed-docs] “Use the Collection Runner to send multiple requests in a specific order”
Contract testing
platform-engineerValidate live responses against the API contract to catch drift
weight 2 · round drawnHoppscotchnone0/10Evidence shows Hoppscotch supports API testing scripts, CLI test runs with JUnit reports, and OpenAPI import for building requests/collections, but nothing describes validating live responses against an API contract (e.g., OpenAPI schema) to detect drift.
Insomnianone0/10Insomnia's docs describe general request/response testing, chaining, and OpenAPI spec linting (via 'inso lint spec') for validating the spec file itself, but there is no evidence of a feature that validates live API responses at runtime against an OpenAPI/schema contract to detect drift.
Testing
developerRun an entire collection as an automated test suite with a pass/fail report
weight 3 · round drawnHoppscotch's official CLI (hopp test) runs entire collections from the terminal and generates JUnit reports for collection runs, which is a standard pass/fail CI test report format; docs also describe running API tests and automated monitoring via CLI. Missing for 10: no independent/hands-on community corroboration of the CLI test-runner experience or assertion/scripting depth was found in the pack.
- [claimed-docs] “Use the Hoppscotch CLI to run API tests, automate monitoring, and manage collections from your terminal.”
- [claimed-docs] “The hopp test command now has the ability to generate a JUnit Report for collection runs in the CLI.”
- [claimed-docs] “With the command-line interface (CLI) you can interact with the Hoppscotch platform using a terminal, or through an automated system. This e…”
- [probe] “official CLI documented at https://docs.hoppscotch.io/documentation/clients/cli/overview”
Insomnia supports collection runs (Collection Runner, unlimited collection runs), chaining requests, pre/post-request scripts, and the Inso CLI which 'disables prompts and provides exit codes to pass or fail the CI workflow,' enabling automated test suites with pass/fail reporting in CI. Docs also show lint commands failing builds on errors, reinforcing pass/fail semantics. missing for 10: no independent/hands-on report confirming the CLI pass/fail report format or reliability in practice, and no detail on report output formatting (e.g., JUnit/HTML report generation).
- [claimed-docs] “Use the Insomnia CLI to automate the execution of your API tests using your existing Git workflows.”
- [claimed-docs] “Automatically test multiple requests in your collections, with unlimited collection runs.”
- [claimed-docs] “Use the Collection Runner to send multiple requests in a specific order”
- [claimed-docs] “Test complex workflows by chaining the responses from requests together”
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
developerWrite test assertions against response status, body, and headers
weight 3 · round to InsomniaHoppscotch docs reference scripting capabilities for 'pre-request logic and test cases' and a CLI 'hopp test' command that can generate JUnit reports for collection runs, implying support for test assertions, but no evidence details how assertions target response status, body, or headers specifically. missing for 10: explicit documentation/examples of assertion syntax (pw.expect-style) for status/body/headers, independent hands-on confirmation of test script execution.
- [claimed-docs] “These include renaming of API requests, generation of structured request payloads, and scripting capabilities for pre-request logic and test…”
- [claimed-docs] “The hopp test command now has the ability to generate a JUnit Report for collection runs in the CLI.”
- [claimed-docs] “With the command-line interface (CLI) you can interact with the Hoppscotch platform using a terminal, or through an automated system. This e…”
- [github] “Snippets of code associated with a request that is executed before the request is sent.”
Insomnia's docs describe a dedicated testing feature set—chaining requests, pre-/after-response scripting to add logic, automatic cookie handling, and CLI-driven automated test runs across collections—strongly implying support for assertions on response status/body/headers, but no evidence pack item shows explicit assertion syntax or examples asserting on status codes, body content, or headers specifically. Missing for 10: explicit assertion API/examples (e.g., expect(response.status).to.equal), documented header/body matcher functions, and independent hands-on confirmation of assertion authoring.
- [claimed-docs] “Pre-request and after-response scripting to add logic to your requests”
- [claimed-docs] “Test complex workflows by chaining the responses from requests together”
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “Insomnia automatically stores cookies from every response and sends them with future requests”
- [claimed-docs] “Automatically test multiple requests in your collections, with unlimited collection runs.”
- [claimed-docs] “Pre-request scripts allow you to execute tasks before a request is sent. They can be used to: * Manipulate environment variables or authenti…”
Not comparable on these axes
ai-native userSubscribe to events via webhooks
weight 2 · not comparableHoppscotchnone0/10Hoppscotch is an API client/testing tool; nothing in the evidence shows any webhook subscription or event-notification mechanism for AI agents—the closest agentic features (MCP server, CLI) let an agent send requests and manage collections but do not provide a way to subscribe to incoming events. No evidence of webhook support at all.
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you.”
- [claimed-docs] “It hands the host your collections, requests, environments, and teams, so an agent can read and change them for you. It also sends real HTTP…”
- [claimed-docs] “With the command-line interface (CLI) you can interact with the Hoppscotch platform using a terminal, or through an automated system. This e…”
Insomnian/aInsomnia is an API client/design tool for making requests, testing, and mocking; there is no evidence of a webhook subscription/event-notification feature, and 'subscribing to events via webhooks' is not a natural axis for this product category (it's a client, not a service that emits events).
ai-native userProxy and govern LLM/MCP traffic (token limits, prompt guards, provider routing) through the platform
weight 2 · not comparableHoppscotchn/aHoppscotch is an API client/testing platform (with an MCP server exposing its own collections to agents), not an LLM/MCP gateway or proxy product designed to govern AI traffic with token limits, prompt guards, or provider routing. This capability is a category error for this product type.
Insomnianone0/10Insomnia's MCP support is client-side only (docs-30, docs-46) — it lets users discover and invoke external MCP servers' tools/prompts, and a brief mention of connecting to Konnect for 'protecting requests' (docs-14), but there is no evidence of built-in token-limit enforcement, prompt guards, or LLM provider routing/proxying within Insomnia itself. Missing for 10: any documentation of token/rate limiting, prompt injection guards, or multi-provider routing/proxy governance features.
- [claimed-docs] “Use MCP clients to connect Insomnia to Konnect for mocking, validating, and protecting requests in real time.”
- [claimed-docs] “The Insomnia MCP Client discovers these elements, which enables you to invoke, query, or test them directly in the app.”
- [claimed-docs] “Use Insomnia to connect external Model Context Protocol (MCP) Servers to access AI-ready tools, prompts, and resources.”
platform-engineerMonitor API traffic with metrics, logging, and tracing integrations
weight 2 · not comparableHoppscotchnone0/10Hoppscotch is an API client/testing tool; evidence covers request building, collections, CLI testing, self-hosting, SSO, and audit logs, but nothing describes metrics export, logging pipelines, or tracing integrations for monitoring API traffic (e.g., no OpenTelemetry, Prometheus, or log-shipping integrations mentioned). This axis is plausible for a platform aimed at API teams, so absence of evidence yields 'none' rather than 'na'.
- [claimed-docs] “With the command-line interface (CLI) you can interact with the Hoppscotch platform using a terminal, or through an automated system. This e…”
- [claimed-docs] “SAML-based SSO, on-prem deployment, audit logs, and more.”
- [claimed-docs] “SAML-based SSO, on-prem deployment, audit logs, and more. Hoppscotch Enterprise Edition is a self-hosted version of Hoppscotch Cloud with en…”
platform-engineerEnforce authentication (API keys, OAuth2, JWT, mTLS) on upstream APIs via gateway plugins or policies
weight 3 · not comparableHoppscotchn/aHoppscotch is an API client/testing tool, not an API gateway; it supports auth methods (OAuth2, mTLS, JWT) for making requests to APIs but does not act as a gateway enforcing authentication policies on upstream APIs via plugins/policies. This is a category mismatch — the gateway-traffic axis does not apply to a request client.
Insomnian/aInsomnia is an API client/testing tool for designing, sending, and debugging requests, not an API gateway that enforces authentication/authorization policies on upstream traffic; that role belongs to products like Kong Gateway. The evidence only shows Insomnia's own auth support for making requests (SAML IdP support, vault integration) and RBAC on its collaboration platform, not gateway-plugin-based enforcement on upstream APIs.
platform-engineerEnforce rate limits on API traffic per consumer or route
weight 3 · not comparableHoppscotchn/aHoppscotch is an API client/testing tool, not an API gateway or traffic-management product; enforcing rate limits per consumer or route is a gateway/infra concern outside its category, so the axis does not apply.
platform-engineerRoute, load-balance, and transform requests between consumers and upstream services
weight 2 · not comparableHoppscotchn/aHoppscotch is an API client/testing tool for building, sending, and testing requests, not an API gateway or load balancer. There is no evidence it provides routing, load balancing, or traffic transformation between consumers and upstream services — this is a category error for this product type.
Insomnian/aInsomnia is an API client/design/testing tool used by developers to build, test, and mock API requests locally; it does not sit in the request path routing, load-balancing, or transforming live traffic between consumers and upstream production services. That gateway/proxy functionality is a different product category (e.g., Kong Gateway), so this axis is a category error for Insomnia.
developerSpin up a mock server from saved examples or a spec so consumers can build before the API exists
weight 3 · not comparableHoppscotchn/aHoppscotch is an API request/testing client (with collections, CLI, MCP server) and does not offer mock server generation from examples or specs; this is a category error for this product type — no evidence of such a feature exists.
Insomnia Cloud mock servers can be created directly from OpenAPI definitions, prompts, or live URL responses, auto-scaffolding routes/responses so consumers can build against the API before it's complete, and dynamic mocking supports realistic templated/fake data responses. missing for 10: independent/hands-on verification of mock server reliability and no evidence of generating mocks directly from saved request 'examples' (only prompt/spec/URL inputs documented).
- [claimed-docs] “The Insomnia Cloud mock servers allow you to create a mock endpoint in a few steps.”
- [claimed-docs] “Creates a mock server from a prompt, OpenAPI definition, or live URL response. Automatically scaffolds routes, responses, and configurations…”
- [claimed-docs] “Auto-generate a mock server from a natural language prompt and one of the following input types: URL, OpenAPI, or JSON.”
- [claimed-docs] “Dynamic mocking renders Liquid templates so responses can include: - Data from the request (headers, query parameters, path, or body). - Ran…”
- [claimed-docs] “Dynamic mocking renders Liquid templates so responses can include: Data from the request (headers, query parameters, path, or body).”
- [claimed-docs] “AI-assisted mock server generation, which transforms prompts or API definitions into mock APIs.”