Postman vs Hoppscotch

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   Postman✓fullprobed9/10

   Postman's docs site serves a live llms.txt (HTTP 200) and supports appending .md to any docs page for clean Markdown content, directly enabling an agent to be pointed at agent-oriented docs; this is confirmed hands-on via probes rather than just claimed. missing for 10: independent third-party corroboration that an agent successfully consumed llms.txt end-to-end in a real workflow.

   • [probe] “PROBE llms.txt: HTTP 200 at https://learning.postman.com/llms.txt # Postman Docs # Postman Docs Learn how to use Postman. Search the docs …”
   • [probe] “PROBE docs-md: HTTP 200 at https://learning.postman.com/docs/getting-started/overview/.md > For clean Markdown content of this page, append …”

   proof ↗⚑ flag

   Hoppscotch✓fullprobed9/10

   A 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.”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Postman
   Postman✓fullprobed9/10

   Postman CLI (and Newman) explicitly support headless execution of collections, mocks, and governance checks in CI/CD pipelines, and this is documented alongside the Postman API for programmatic integration into toolchains. Missing for 10: independent/hands-on CI benchmark or third-party case study confirming real-world CI reliability beyond vendor docs.

   • [claimed-docs] “Run and manage collections with extensive configuration options and built-in reporters.”
   • [claimed-docs] “You can also use the Postman CLI to run test collections as part of your continuous integration and continuous delivery (CI/CD) pipeline.”
   • [claimed-docs] “combine the Postman API with the Postman CLI to integrate Postman with your CI/CD workflow.”
   • [claimed-docs] “The Postman CLI enables you to run collections, lint API schemas, run security and governance checks, and log in and out.”
   • [claimed-docs] “Newman allows you to run and test a Postman Collections directly from the command-line.”
   • [probe] “official CLI documented at https://learning.postman.com/docs/postman-cli/postman-cli-overview/”

   proof ↗⚑ flag

   Hoppscotch✓fullprobed8/10

   Hoppscotch 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”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Postman—none0/10

   Evidence shows Postman can generate/register MCP servers (docs-7, docs-9) and has an AI 'Agent Mode' (docs-8), but there is no documentation or hands-on evidence that Postman itself acts as an MCP client, letting users plug in external MCP servers so its AI/tools can consume them. Missing for 10: explicit MCP-client integration inside Postman's AI/Agent Mode, UI/config for adding external MCP servers, and any hands-on proof of tool invocation from a connected MCP server.

   • [claimed-docs] “This guide walks you through registering a Model Context Protocol (MCP) server with the gateway and making it available to your team.”
   • [claimed-docs] “With Agent Mode, you can turn your words into action across the API lifecycle. Send requests, fix errors, update tests, and more, using natu…”
   • [claimed-docs] “With Postman’s MCP Generator, you can create your own MCP server with public APIs from the Postman API Network”

   proof ↗⚑ flag

   Hoppscotch—none0/10

   Evidence 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”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Postman
   Postman✓fullprobed8/10

   Postman publishes an official MCP server (postman-mcp-server) and documents both registering MCP servers with its Fabric Gateway and generating MCP servers from Postman API collections, giving AI agents a standard way to connect. Missing for 10: independent/hands-on corroboration that the official MCP server works reliably with third-party agents beyond first-party docs.

   • [probe] “official MCP server documented at https://www.postman.com/postman-mcp-server/”
   • [claimed-docs] “This guide walks you through registering a Model Context Protocol (MCP) server with the gateway and making it available to your team.”
   • [claimed-docs] “With Postman’s MCP Generator, you can create your own MCP server with public APIs from the Postman API Network”

   proof ↗⚑ flag

   Hoppscotch✓fullprobed7/10

   Hoppscotch 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”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Postman✓fullprobed8/10

   Postman ships an official Postman CLI with detailed docs covering running collections, linting, security/governance checks, mock servers, and CI/CD integration, and explicitly documents giving coding agents CLI context for API discovery, code generation, and maintenance tasks, directly matching an AI-native CLI story. A probe confirms the CLI docs page is live and first-party. Missing for 10: independent/hands-on community validation of AI-agent CLI usage beyond vendor docs.

   • [claimed-docs] “Give coding agents Postman CLI context for API discovery, code generation, and maintenance tasks.”
   • [claimed-docs] “The Postman CLI enables you to run collections, lint API schemas, run security and governance checks, and log in and out.”
   • [probe] “official CLI documented at https://learning.postman.com/docs/postman-cli/postman-cli-overview/”

   proof ↗⚑ flag

   Hoppscotch✓fullprobed8/10

   Hoppscotch 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”

   proof ↗⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round to Postman
   Postman✓fullprobed9/10

   Postman documents a public Postman API for programmatically managing assets (postman-docs-5,41), an OpenAPI spec is live (postman-probe-3), and the API can be combined with CLI/CI-CD workflows (postman-docs-6,19). This is a well-documented, first-party public API surface for driving Postman programmatically. Missing for 10: no independent/hands-on corroboration of API robustness or rate limits from community sources.

   • [claimed-docs] “Use the Postman API to programmatically manage your Postman assets and integrate Postman into your development toolchain.”
   • [claimed-docs] “combine the Postman API with the Postman CLI to integrate Postman with your CI/CD workflow.”
   • [claimed-docs] “You can also use the Postman CLI to run test collections as part of your continuous integration and continuous delivery (CI/CD) pipeline.”
   • [claimed-docs] “Integrate Postman into your development toolchain”
   • [probe] “PROBE openapi: HTTP 200 at https://learning.postman.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   Hoppscotch✓fullprobed8/10

   Hoppscotch 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…”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Postman—none0/10

   Evidence shows Postman has team/workspace role permissions and a Vault for secrets, but nothing documents issuing scoped or least-privilege API credentials specifically for an AI agent's use (e.g., agent-specific API keys, granular scopes, or token restrictions tied to Agent Mode or MCP usage).

   ⚑ flag

   Hoppscotch—none0/10

   Hoppscotch'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”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Postman—none0/10

   Evidence shows Postman's own API (postman-docs-5, postman-docs-41) and a CLI (postman-probe-5) for programmatic access, and a feature to generate SDKs *from* user collections (postman-docs-4), but there is no evidence of officially maintained Postman SDKs (e.g., Node/Python/Go client libraries) that an AI-native developer could build against to integrate with Postman itself.

   • [claimed-docs] “Generate and manage client SDKs from your Postman Collections and API specifications.”
   • [claimed-docs] “Use the Postman API to programmatically manage your Postman assets and integrate Postman into your development toolchain.”
   • [claimed-docs] “Integrate Postman into your development toolchain”

   proof ↗⚑ flag

   Hoppscotch—none0/10

   Evidence 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.

   ⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Postman
   Postman~partialclaimed6/10

   Postman CLI docs explicitly mention creating, managing, and forwarding webhooks for event-driven integrations and local development, which supports webhook subscription/handling. However, this is a thin CLI feature mention rather than a full first-class webhook subscription API/product surface with detailed setup, event types, or independent corroboration. Missing for 10: dedicated webhook subscription API docs, event catalog/type list, hands-on/independent verification of webhook reliability, and integration examples beyond a single line mention.

   • [claimed-docs] “Create, manage, and forward webhooks for event-driven integrations and local development.”
   • [claimed-docs] “The Postman CLI enables you to run collections, lint API schemas, run security and governance checks, and log in and out.”

   proof ↗⚑ flag

   Hoppscotch—none0/10

   Hoppscotch 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…”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Postman
   Postman✓fullclaimed7/10

   Postman ships an in-product AI layer (Agent Mode/Postbot) that generates suggestions and takes actions on your API data via natural language — sending requests, fixing errors, updating tests, visualizing responses, and writing documentation — which matches the 'AI-generated insights and suggestions from data' story. Missing for 10: independent/hands-on corroboration of Agent Mode's suggestion quality and no evidence of deeper analytics-driven insights (e.g., AI-derived patterns from usage/monitoring data) beyond action-oriented suggestions.

   • [claimed-docs] “With Agent Mode, you can turn your words into action across the API lifecycle. Send requests, fix errors, update tests, and more, using natu…”
   • [claimed-docs] “You can ask Agent Mode to add tests to requests, visualize responses, write documentation, and more.”
   • [claimed-docs] “Postbot is free to try on all Postman plans . Monthly usage is limited to 50 activities per user.”
   • [claimed-docs] “With Postman’s MCP Generator, you can create your own MCP server with public APIs from the Postman API Network”

   proof ↗⚑ flag

   Hoppscotch~partialclaimed5/10

   Hoppscotch 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…”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Postman~partialclaimed4/10

   Postman offers automation building blocks — CLI collection runs in CI/CD pipelines, webhooks, and a programmatic API (postman-docs-1, postman-docs-6, postman-docs-19, postman-docs-24, postman-docs-32) — and an MCP Generator/Agent Mode for AI interaction (postman-docs-8, postman-docs-9), but these are schedule/CI-triggered or interactive assistant features rather than evidence of self-directed, unattended AI agent automations running continuously in the background. Missing for 10: documented scheduled/monitor-style autonomous jobs, evidence of AI agents independently triggering and managing Postman workflows without human or CI trigger, and any hands-on validation of such autonomous runs.

   • [claimed-docs] “Run and manage collections with extensive configuration options and built-in reporters.”
   • [claimed-docs] “combine the Postman API with the Postman CLI to integrate Postman with your CI/CD workflow.”
   • [claimed-docs] “You can also use the Postman CLI to run test collections as part of your continuous integration and continuous delivery (CI/CD) pipeline.”
   • [claimed-docs] “Create, manage, and forward webhooks for event-driven integrations and local development.”
   • [claimed-docs] “With Agent Mode, you can turn your words into action across the API lifecycle. Send requests, fix errors, update tests, and more, using natu…”
   • [claimed-docs] “With Postman’s MCP Generator, you can create your own MCP server with public APIs from the Postman API Network”
   • [claimed-docs] “The Postman CLI enables you to run collections, lint API schemas, run security and governance checks, and log in and out.”

   proof ↗⚑ flag

   Hoppscotch~partialprobed4/10

   Hoppscotch'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”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Postman
   Postman✓fullclaimed8/10

   Postman ships Agent Mode, a built-in AI assistant that can send requests, fix errors, update tests, and write documentation using natural language (postman-docs-8, postman-docs-33), plus Postbot, another in-app AI assistant with defined usage limits (postman-docs-48). This is a first-party, in-product delegation capability. Missing for 10: independent/hands-on user reports validating Agent Mode's real-world reliability and depth beyond vendor docs.

   • [claimed-docs] “With Agent Mode, you can turn your words into action across the API lifecycle. Send requests, fix errors, update tests, and more, using natu…”
   • [claimed-docs] “You can ask Agent Mode to add tests to requests, visualize responses, write documentation, and more.”
   • [claimed-docs] “Postbot is free to try on all Postman plans . Monthly usage is limited to 50 activities per user.”

   proof ↗⚑ flag

   Hoppscotch~partialclaimed5/10

   Docs 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…”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Postman
   Postman✓fullclaimed8/10

   Postman's Agent Mode explicitly lets users 'turn words into action across the API lifecycle' — sending requests, fixing errors, updating tests — using natural language, plus Postbot for adding tests/docs via natural-language prompts, both first-party documented features. Missing for 10: independent hands-on validation of natural-language command reliability/accuracy beyond vendor docs.

   • [claimed-docs] “With Agent Mode, you can turn your words into action across the API lifecycle. Send requests, fix errors, update tests, and more, using natu…”
   • [claimed-docs] “You can ask Agent Mode to add tests to requests, visualize responses, write documentation, and more.”
   • [claimed-docs] “Postbot is free to try on all Postman plans . Monthly usage is limited to 50 activities per user.”

   proof ↗⚑ flag

   Hoppscotch~partialprobed6/10

   Hoppscotch 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”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Postman
   Postman~partialclaimed6/10

   Postman's quick-start docs show a real, runnable example (send a request to postman-echo.com/get and view the response) and the API Network lets users 'find any API' with published collections/docs, plus response visualization and Spec Hub for API structure exploration — all consistent with an interactive, runnable API reference. However, there is no explicit evidence of a dedicated 'published documentation with Run-in-Postman' interactive reference page or AI-specific reference browsing feature. missing for 10: explicit documentation of a generated public API reference page with embedded runnable/try-it examples, and any AI-native framing of browsing that reference.

   • [claimed-docs] “Enter `postman-echo.com/get` for the request URL. 3. Click **Send**. Postman displays the response data sent from the server in the lower p…”
   • [claimed-docs] “You'll also learn how to save your request to a collection and write a basic test to validate the API response.”
   • [claimed-docs] “Postman's API client enables you to create and send API [requests](/docs/getting-started/basics/postman-elements/#requests), including HTTP,…”
   • [claimed-docs] “Find any API you need. This is where publishers share their APIs with the world.”
   • [claimed-docs] “[Response visualization](https://learning.postman.com/docs/sending-requests/response-data/visualizer/)”
   • [claimed-docs] “Use [Spec Hub](/docs/design-apis/specifications/overview/) to design your API's structure, or use [types in collections](/docs/design-apis/c…”

   proof ↗⚑ flag

   Hoppscotch~partialclaimed5/10

   Hoppscotch'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…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Postman
   Postman✓fullprobed8/10

   A probe confirms Postman publishes a machine-readable OpenAPI spec at learning.postman.com/openapi.json (valid 'openapi' key), and Postman's own developer API docs and Spec Hub further support spec-based API design/consumption. This directly satisfies the AI-native need to fetch a structured API spec. Missing for 10: no independent/community corroboration of using this spec file in real workflows, and no explicit versioning/documentation of the spec's completeness.

   • [probe] “PROBE openapi: HTTP 200 at https://learning.postman.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “Use the Postman API to programmatically manage your Postman assets and integrate Postman into your development toolchain.”
   • [claimed-docs] “Use Spec Hub to design your API’s structure, or use types in collections to design your API with the Postman Collection format.”
   • [claimed-docs] “Use [Spec Hub](/docs/design-apis/specifications/overview/) to design your API's structure, or use [types in collections](/docs/design-apis/c…”

   proof ↗⚑ flag

   Hoppscotch—none0/10

   A 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.”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Postman
   Postman~partialclaimed6/10

   Postman's mock servers and environment/variable management let users simulate API behavior and separate sandbox/staging config from production, directly supporting isolated testing without touching real production data, and these are usable from Agent Mode/CLI workflows that an AI-native user might drive. However, no evidence explicitly frames this as an AI-agent-specific 'sandbox mode' or guarantees isolation from production systems beyond the mock-server abstraction. Missing for 10: explicit documentation tying mock/sandbox environments to AI-agent workflows, an explicit no-production-impact guarantee, and independent/hands-on corroboration of safe sandbox testing.

   • [claimed-docs] “Create a mock server in Postman to simulate a real API server that’s always available to handle requests.”
   • [claimed-docs] “Create a _mock server_ in Postman to simulate a real API server that’s always available to handle requests.”
   • [claimed-docs] “[Deploy a mock server](/docs/design-apis/mock-apis/set-up-mock-servers)”
   • [claimed-docs] “[Create dynamic mock responses](/docs/design-apis/mock-apis/create-dynamic-responses)”
   • [claimed-docs] “Run simulations against local mock servers to test how your service responds to disruptions and performance constraints.”
   • [claimed-docs] “[Variables](https://learning.postman.com/docs/sending-requests/variables/variables/) [Environments](https://learning.postman.com/docs/sendi…”
   • [claimed-docs] “With Agent Mode, you can turn your words into action across the API lifecycle. Send requests, fix errors, update tests, and more, using natu…”

   proof ↗⚑ flag

   Hoppscotch~partialprobed3/10

   Hoppscotch 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”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Postman—none0/10

   The evidence pack shows the Postman API exists and is documented for programmatic use (postman-docs-5, postman-docs-41) and an OpenAPI spec is publicly served (postman-probe-3), but nothing in the pack references API versioning conventions or a documented deprecation policy for that API. Since a platform API is a reasonable place to expect version/deprecation documentation, absence of such evidence yields 'none' rather than 'na'.

   • [claimed-docs] “Use the Postman API to programmatically manage your Postman assets and integrate Postman into your development toolchain.”
   • [claimed-docs] “Integrate Postman into your development toolchain”
   • [probe] “PROBE openapi: HTTP 200 at https://learning.postman.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   Hoppscotch—none0/10

   No 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.

   ⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Postman
   Postman✓fullclaimed7/10

   Postman lets users run entire collections (many requests) at once via the CLI/Newman and lets AI-native workflows programmatically manage many Postman assets in bulk through the Postman API (postman-docs-1, postman-docs-5, postman-docs-6, postman-docs-19, postman-docs-42). This directly supports bulk operations across many items (requests, collections, assets) in an automatable, scriptable way suited to AI-native/CI use. missing for 10: no explicit documentation of bulk-specific batch limits/throughput, and no independent hands-on evidence confirming large-scale bulk runs work reliably.

   • [claimed-docs] “Run and manage collections with extensive configuration options and built-in reporters.”
   • [claimed-docs] “Use the Postman API to programmatically manage your Postman assets and integrate Postman into your development toolchain.”
   • [claimed-docs] “combine the Postman API with the Postman CLI to integrate Postman with your CI/CD workflow.”
   • [claimed-docs] “You can also use the Postman CLI to run test collections as part of your continuous integration and continuous delivery (CI/CD) pipeline.”
   • [claimed-docs] “Newman allows you to run and test a Postman Collections directly from the command-line.”

   proof ↗⚑ flag

   Hoppscotch~partialclaimed6/10

   The 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.”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Postman
   Postman~partialclaimed4/10

   Postman supports pre-request/post-response scripts that execute automatically around request events (docs-12), webhook creation for event-driven integrations (docs-24), and CI/CD-triggered collection runs (docs-19), which together provide some event-triggered automation. However there is no documented general-purpose rules/trigger engine (e.g., monitors, scheduled alerts, conditional if-event-then-action builder) that lets a user declaratively define arbitrary event-based rules. Missing for 10: a dedicated rule/trigger builder UI or API, conditional logic mapping arbitrary events to arbitrary actions, and independent/hands-on confirmation of this automation working reliably.

   • [claimed-docs] “Postman can run scripts before a request is sent (pre-request) or after (post-response).”
   • [claimed-docs] “Create, manage, and forward webhooks for event-driven integrations and local development.”
   • [claimed-docs] “You can also use the Postman CLI to run test collections as part of your continuous integration and continuous delivery (CI/CD) pipeline.”

   proof ↗⚑ flag

   Hoppscotch—none0/10

   Hoppscotch 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.

   ⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Postman—none0/10

   The evidence pack shows CI/CD integration via the Postman CLI and API, but nothing about a native scheduler or recurring job/workflow trigger within Postman itself; scheduling would depend on external CI/CD orchestration, not documented here.

   • [claimed-docs] “combine the Postman API with the Postman CLI to integrate Postman with your CI/CD workflow.”
   • [claimed-docs] “You can also use the Postman CLI to run test collections as part of your continuous integration and continuous delivery (CI/CD) pipeline.”
   • [claimed-docs] “Use the Postman API to programmatically manage your Postman assets and integrate Postman into your development toolchain.”

   proof ↗⚑ flag

   Hoppscotch—none0/10

   Hoppscotch 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…”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round to Postman
   Postman~partialcommunity4/10

   Postman documents workspace 'versioning' and team review mechanisms (comments, live sessions, roles/permissions) that could support reviewing automations, but there is no explicit documented rollback/version-history feature for collections or automations, and a community report shows a case where a user's collections were deleted and had to be manually restored via support rather than self-service rollback. missing for 10: explicit version-history/rollback UI or API for collections/automations, first-party docs describing rollback workflow, and independent confirmation that rollback works reliably.

   • [claimed-docs] “Create internal workspaces, where team members can share, version, and discuss their work and collaborate on API projects.”
   • [claimed-docs] “[Comment on APIs](/docs/collaborating-in-postman/comments)”
   • [claimed-docs] “you can start a live session in an HTTP request to collaborate with your team in real time as you test, develop, and troubleshoot.”
   • [community] “One person had 'deleted' all his collections and workspaces after layoff... Postman support restored all the collections but the 'environmen…”

   proof ↗⚑ flag

   Hoppscotch—none0/10

   No 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…”

   proof ↗⚑ flag

Ci

1. developerRun my API test collections in CI with a CLI and fail the build on regressions

   weight 3 · round to Postman
   Postman✓fullprobed8/10

   Postman CLI is well-documented for running collections, linting schemas, and running security/governance checks from the command line, and docs explicitly describe combining it with the Postman API to integrate into CI/CD pipelines (fail-on-regression behavior is implicit in collection test run exit codes, standard for such CLIs). Newman is also cited as a longstanding CLI runner for CI use. Missing for 10: explicit documentation/example of exit-code-based build failure and a third-party CI pipeline case study confirming this in practice.

   • [claimed-docs] “Run and manage collections with extensive configuration options and built-in reporters.”
   • [claimed-docs] “combine the Postman API with the Postman CLI to integrate Postman with your CI/CD workflow.”
   • [claimed-docs] “You can also use the Postman CLI to run test collections as part of your continuous integration and continuous delivery (CI/CD) pipeline.”
   • [claimed-docs] “The Postman CLI enables you to run collections, lint API schemas, run security and governance checks, and log in and out.”
   • [claimed-docs] “Newman allows you to run and test a Postman Collections directly from the command-line.”
   • [probe] “official CLI documented at https://learning.postman.com/docs/postman-cli/postman-cli-overview/”

   proof ↗⚑ flag

   Hoppscotch~partialprobed7/10

   Hoppscotch 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”

   proof ↗⚑ flag

Monitors

1. developerSchedule collection runs as monitors that alert me when an API breaks

   weight 2 · round to Hoppscotch
   Postman—none0/10

   The evidence pack covers Postman CLI, CI/CD integration, mock servers, and collaboration features, but contains no mention of a 'Monitors' capability, scheduling, or automated alerting when API tests fail. Without any documentation of scheduled runs or alerting, this specific story is unevidenced.

   ⚑ flag

   Hoppscotch~partialclaimed4/10

   Hoppscotch'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.”

   proof ↗⚑ flag

Scripting

1. developerScript pre-request and post-response logic to chain requests and massage data

   weight 2 · round to Postman
   Postman✓fullclaimed9/10

   Postman docs explicitly confirm pre-request and post-response scripting, passing data between requests, and dynamic parameters, plus CI/CD integration via CLI/Newman to chain and automate these scripted workflows. Missing for 10: independent hands-on corroboration of complex data-massaging scripts beyond vendor docs.

   • [claimed-docs] “Postman can run scripts before a request is sent (pre-request) or after (post-response).”
   • [claimed-docs] “Write scripts to add dynamic behavior to requests and collections. Perform API tests, add dynamic parameters, pass data between requests, an…”
   • [claimed-docs] “You can also use the Postman CLI to run test collections as part of your continuous integration and continuous delivery (CI/CD) pipeline.”
   • [claimed-docs] “Newman allows you to run and test a Postman Collections directly from the command-line.”
   • [claimed-docs] “[Variables](https://learning.postman.com/docs/sending-requests/variables/variables/) [Environments](https://learning.postman.com/docs/sendi…”

   proof ↗⚑ flag

   Hoppscotch~partialclaimed6/10

   GitHub 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…”

   proof ↗⚑ flag

Access control

1. platform-engineerControl who can view or edit APIs and collections with roles and permissions

   weight 2 · round to Postman
   Postman✓fullclaimed8/10

   Postman docs explicitly state roles and permissions can be defined at team, workspace, and element levels, directly matching the platform-engineer's need to control view/edit access on APIs and collections. Missing for 10: no independent/hands-on corroboration of granular permission enforcement in practice, and no detail on specific role types (admin/editor/viewer) or audit logging.

   • [claimed-docs] “You can define the roles and permissions assigned to team members at the team, workspace, and element levels.”
   • [claimed-docs] “Create internal workspaces, where team members can share, version, and discuss their work and collaborate on API projects.”
   • [claimed-docs] “Workspaces enable you to collaborate with teammates or anyone in the Postman community.”

   proof ↗⚑ flag

   Hoppscotch~partialclaimed4/10

   Hoppscotch 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.”

   proof ↗⚑ flag

Api catalog

1. platform-engineerPublish an internal catalog or portal where teams discover and consume our APIs

   weight 2 · round to Postman
   Postman~partialclaimed6/10

   Postman supports internal workspaces for sharing/discovering collections and APIs, an API Network for publishing APIs, and Spec Hub/collection design docs, which together enable an internal catalog-like experience. However, there is no explicit evidence of a dedicated 'developer portal' product or public-facing catalog publishing feature distinct from workspaces. missing for 10: dedicated API portal/catalog publishing feature, evidence of external-facing discovery UI, governance/catalog curation tooling beyond workspace sharing.

   • [claimed-docs] “Create internal workspaces, where team members can share, version, and discuss their work and collaborate on API projects.”
   • [claimed-docs] “Workspaces enable you to collaborate with teammates or anyone in the Postman community.”
   • [claimed-docs] “Find any API you need. This is where publishers share their APIs with the world.”
   • [claimed-docs] “Use Spec Hub to design your API’s structure, or use types in collections to design your API with the Postman Collection format.”
   • [claimed-docs] “Use [Spec Hub](/docs/design-apis/specifications/overview/) to design your API's structure, or use [types in collections](/docs/design-apis/c…”

   proof ↗⚑ flag

   Hoppscotch~partialclaimed4/10

   Hoppscotch 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.”

   proof ↗⚑ flag

Team workspaces

1. developerShare collections with my team in a synced shared workspace

   weight 3 · round drawn
   Postman~partialcommunity6/10

   First-party docs clearly document shared team workspaces with roles/permissions, live sessions, and comments for collaborating on collections (postman-docs-18, postman-docs-21, postman-docs-14, postman-docs-13, postman-docs-39, postman-docs-40). However, community reports describe real friction: syncing/sharing collections is gated behind per-seat cloud subscriptions, and forced account-login flows have in some cases wiped local collections/workspaces (postman-comm-17, postman-comm-4, postman-comm-15), which are concrete caveats around the exact 'shared workspace sync' experience. missing for 10: independent hands-on confirmation that team-shared workspaces sync reliably without data loss, and evidence the feature works well outside the paid/cloud-gated tier.

   • [claimed-docs] “Create internal workspaces, where team members can share, version, and discuss their work and collaborate on API projects.”
   • [claimed-docs] “Workspaces enable you to collaborate with teammates or anyone in the Postman community.”
   • [claimed-docs] “You can define the roles and permissions assigned to team members at the team, workspace, and element levels.”
   • [claimed-docs] “you can start a live session in an HTTP request to collaborate with your team in real time as you test, develop, and troubleshoot.”
   • [claimed-docs] “[Comment on APIs](/docs/collaborating-in-postman/comments)”
   • [claimed-docs] “[Collaborate with Live Sessions](/docs/collaborating-in-postman/live-sessions)”
   • [community] “My main gripe with Postman and Insomnia isn't actually the web based UI, but the lock-in. Postman especially tries to push people towards ge…”
   • [community] “One person had 'deleted' all his collections and workspaces after layoff... Postman support restored all the collections but the 'environmen…”
   • [community] “I have been using postman offline without an account for a long time. Today when I opened the program it asked me to create an account. When…”

   proof ↗⚑ flag

   Hoppscotch~partialcommunity6/10

   Hoppscotch 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.”

   proof ↗⚑ flag

Collections

1. developerStore collections as plain text files in my repo and version them with git

   weight 3 · round drawn
   Postman—none0/10

   Postman's docs describe collections living in cloud workspaces with sharing/versioning via Postman's own platform, but there is no documentation of a native git-friendly, plain-text file storage workflow for collections. Community evidence even shows developers explicitly switching to Bruno specifically because it stores collections as files that can be put in git, implying Postman does not offer this as a first-class workflow.

   • [claimed-docs] “Create internal workspaces, where team members can share, version, and discuss their work and collaborate on API projects.”
   • [claimed-docs] “Workspaces enable you to collaborate with teammates or anyone in the Postman community.”
   • [community] “I've replaced Postman with Bruno (desktop app), works great so far! It's nice to put the collection folder in git so I can collaborate with …”
   • [community] “I remember when one of the 'Core Goals' of Postman was 'Complete control over your data - Keep simple JSON based data formats which can be e…”

   proof ↗⚑ flag

   Hoppscotch—none0/10

   There 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…”

   proof ↗⚑ flag

2. developerImport and export collections in portable formats to move between tools

   weight 2 · round to Hoppscotch
   Postman~partialcommunity3/10

   Evidence only indirectly touches this story: docs reference the 'Postman Collection format' as the basis for API design (postman-docs-16, postman-docs-38), and community comments recall Postman's original goal of 'simple JSON based data formats which can be exported and shared' (postman-comm-14) and a user manually restoring collections from a local backup file (postman-comm-16). None of these are explicit first-party documentation of an import/export UI/CLI workflow for moving collections between tools. Missing for 10: explicit docs on collection import/export dialogs or CLI commands, confirmation of cross-tool interoperability (e.g., OpenAPI/Postman format conversion), and independent hands-on verification of round-trip fidelity.

   • [claimed-docs] “Use Spec Hub to design your API’s structure, or use types in collections to design your API with the Postman Collection format.”
   • [claimed-docs] “Use [Spec Hub](/docs/design-apis/specifications/overview/) to design your API's structure, or use [types in collections](/docs/design-apis/c…”
   • [community] “I remember when one of the 'Core Goals' of Postman was 'Complete control over your data - Keep simple JSON based data formats which can be e…”
   • [community] “I was able to manually import/restore using a backup I found in ~/.config/Postman but I have no trust for continued use of this tool.”

   proof ↗⚑ flag

   Hoppscotch~partialcommunity5/10

   Docs 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…”

   proof ↗⚑ flag

3. developerOrganize API requests into collections and folders and rerun them anytime

   weight 3 · round to Hoppscotch
   Postman✓fullcommunity8/10

   Postman's core docs confirm collections/folders (postman-docs-15,17,18,29) and rerunning via Postman CLI/Newman or CI/CD (postman-docs-19,32,42), directly matching the story. Missing for 10: independent hands-on verification of folder-level reruns and no first-party mention of nested folder organization specifics; some community reports (postman-comm-4, postman-comm-15) describe collection data loss tied to account/cloud sync issues, which slightly dents reliability confidence though they don't contradict the core organize/rerun feature.

   • [claimed-docs] “Send API requests, group them in collections, and secure your data with Postman Vault.”
   • [claimed-docs] “Write scripts to add dynamic behavior to requests and collections. Perform API tests, add dynamic parameters, pass data between requests, an…”
   • [claimed-docs] “Create internal workspaces, where team members can share, version, and discuss their work and collaborate on API projects.”
   • [claimed-docs] “You can also use the Postman CLI to run test collections as part of your continuous integration and continuous delivery (CI/CD) pipeline.”
   • [claimed-docs] “The Postman CLI enables you to run collections, lint API schemas, run security and governance checks, and log in and out.”
   • [claimed-docs] “Newman allows you to run and test a Postman Collections directly from the command-line.”
   • [community] “One person had 'deleted' all his collections and workspaces after layoff... Postman support restored all the collections but the 'environmen…”
   • [community] “I have been using postman offline without an account for a long time. Today when I opened the program it asked me to create an account. When…”

   proof ↗⚑ flag

   Hoppscotch✓fullcommunity9/10

   Hoppscotch 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…”

   proof ↗⚑ flag

Offline

1. developerWork fully offline in a local workspace without a cloud account

   weight 2 · round to Hoppscotch
   Postman!disputedcontradicted4/10

   Docs mention a 'lightweight API client' usable without signing in (postman-docs-34), suggesting some offline capability, but multiple hands-on community reports directly contradict full offline/local-only operation: users report Postman wiping all collections when declining account creation (postman-comm-15), requiring telemetry/online connectivity even for local secrets (postman-comm-11, postman-comm-12), and pushing forced cloud sign-in for data migration (postman-comm-13), plus lost workspaces after account issues (postman-comm-4). This is a concrete, documented conflict between vendor claims and real-world failures, not mere skepticism. Missing for 10: first-party documentation of a persistent fully-offline local workspace mode, and any official acknowledgment/fix of the reported data-loss-on-offline-use bugs.

   • [claimed-docs] “If you're not signed in to a Postman account, you can still send multi-protocol requests using the [lightweight API client]”
   • [community] “I have been using postman offline without an account for a long time. Today when I opened the program it asked me to create an account. When…”
   • [community] “It connects to their servers when it starts up; have to assume their server is down. It used to be so much nicer before they added this 'fea…”
   • [community] “Apparently Postman needs to be online in order to send 'telemetry': postman is logging all your secrets and environment variables.”
   • [community] “I moved from Postman to RapidAPI when Postman tried to get me to sign up for their cloud service just to migrate my data to a new laptop.”
   • [community] “One person had 'deleted' all his collections and workspaces after layoff... Postman support restored all the collections but the 'environmen…”

   proof ↗⚑ flag

   Hoppscotch~partialcommunity6/10

   Hoppscotch 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?”

   proof ↗⚑ flag

Protocols

1. developerSend GraphQL, gRPC, WebSocket, and SSE requests, not just REST

   weight 2 · round drawn
   Postman~partialclaimed6/10

   Docs confirm Postman's API client supports HTTP, GraphQL, and gRPC requests explicitly (postman-docs-31, postman-docs-34 mentions 'multi-protocol requests'), but there is no explicit documented evidence in this pack of WebSocket or SSE request support. missing for 10: explicit documentation of WebSocket request support, explicit documentation of SSE request support, independent hands-on corroboration of multi-protocol usage.

   • [claimed-docs] “Postman's API client enables you to create and send API [requests](/docs/getting-started/basics/postman-elements/#requests), including HTTP,…”
   • [claimed-docs] “If you're not signed in to a Postman account, you can still send multi-protocol requests using the [lightweight API client]”

   proof ↗⚑ flag

   Hoppscotch~partialclaimed6/10

   GitHub 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.

   • [github] “GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data.”
   • [github] “Establish full-duplex communication channels over a single TCP connection.”

   proof ↗⚑ flag

Environments

1. developerSwitch requests between dev, staging, and prod using environment variable sets

   weight 3 · round to Postman
   Postman✓fullcommunity6/10

   Postman docs explicitly reference an 'Environments' feature alongside Variables, and community evidence confirms teams use Postman to test/validate APIs 'across environments,' supporting the dev/staging/prod switching workflow via environment variable sets. However, the evidence pack lacks a detailed first-party doc excerpt walking through creating multiple environments and switching between them. Missing for 10: a direct doc excerpt describing environment creation/switching UI, and independent hands-on confirmation of variable-set switching specifically.

   • [claimed-docs] “[Variables](https://learning.postman.com/docs/sending-requests/variables/variables/) [Environments](https://learning.postman.com/docs/sendi…”
   • [community] “We've been using Postman for a while now, it's invaluable for testing/validating APIs across our environments. One feature we've been waitin…”

   proof ↗⚑ flag

   Hoppscotch~partialclaimed5/10

   Docs 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.”

   proof ↗⚑ flag

Secrets

1. platform-engineerKeep credentials out of shared files with masked secrets or an external vault integration

   weight 2 · round to Hoppscotch
   Postman!disputedcontradicted4/10

   Postman advertises 'Postman Vault' to secure credentials (postman-docs-15), but multiple independent community reports claim Postman actually syncs/uploads or logs secrets and environment variables to its servers via telemetry, undermining the 'keep credentials out of shared files' promise (postman-comm-6, postman-comm-12). Missing for 10: detailed docs on secret masking mechanics, external vault (e.g., HashiCorp) integration specifics, and a vendor response addressing the telemetry/secret-leak claims.

   • [claimed-docs] “Send API requests, group them in collections, and secure your data with Postman Vault.”
   • [community] “Be careful with Postman. It seems they upload all your secrets to their servers. We stopped to use it a time ago.”
   • [community] “Apparently Postman needs to be online in order to send 'telemetry': postman is logging all your secrets and environment variables.”

   proof ↗⚑ flag

   Hoppscotch~partialclaimed6/10

   Hoppscotch 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.”

   proof ↗⚑ flag

Gateway ops

1. platform-engineerManage API infrastructure as declarative config and sync it from CI (GitOps/APIOps)

   weight 2 · round to Postman
   Postman~partialclaimed5/10

   Postman's API (postman-docs-5/6/41) lets teams programmatically manage collections/specs, and the CLI can run governance/lint checks and tests inside CI/CD pipelines (postman-docs-19, postman-docs-22, postman-docs-32), which supports an APIOps-style workflow. However there's no explicit gateway/infrastructure declarative-config model, no Git-native sync mechanism, or IaC-style (Terraform/K8s) integration described—this is closer to CI-triggered testing/governance than full GitOps management of API gateway infra. Missing for 10: explicit gateway-infrastructure-as-code support, native Git-sync workflow, and evidence of managing routing/gateway policies (not just collections/specs) declaratively from CI.

   • [claimed-docs] “Use the Postman API to programmatically manage your Postman assets and integrate Postman into your development toolchain.”
   • [claimed-docs] “combine the Postman API with the Postman CLI to integrate Postman with your CI/CD workflow.”
   • [claimed-docs] “You can also use the Postman CLI to run test collections as part of your continuous integration and continuous delivery (CI/CD) pipeline.”
   • [claimed-docs] “Check API specifications against configured API governance rules.”
   • [claimed-docs] “The Postman CLI enables you to run collections, lint API schemas, run security and governance checks, and log in and out.”

   proof ↗⚑ flag

   Hoppscotch—none0/10

   Hoppscotch 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…”

   proof ↗⚑ flag

Monitoring

1. platform-engineerMonitor API traffic with metrics, logging, and tracing integrations

   weight 2 · round drawn
   Postman—none0/10

   Postman's evidence pack focuses on API testing, collections, mock servers, collaboration, and an Analytics API for Postman's own usage reporting, but there is no evidence of metrics/logging/tracing integrations (e.g., OpenTelemetry, Prometheus, Datadog) for monitoring live API gateway traffic, which is what a platform-engineer would need. Missing for 10: any documented observability/tracing integration, gateway traffic metrics dashboard, or logging pipeline connecting Postman to APM/observability tools.

   • [claimed-docs] “The Analytics API enables you to explore Postman’s analytics reports programmatically.”
   • [claimed-docs] “This guide walks you through registering a Model Context Protocol (MCP) server with the gateway and making it available to your team.”

   proof ↗⚑ flag

   Hoppscotch—none0/10

   Hoppscotch 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…”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Postman
   Postman~partialprobed6/10

   Postman ships a documented Postman API for programmatic management of assets (collections, workspaces, environments, mocks, analytics) plus a CLI and an official OpenAPI spec, showing broad but not exhaustive API parity with the UI. There's no evidence that UI-only features like Live Sessions, Postbot/Agent Mode, or real-time collaboration have full API equivalents. missing for 10: explicit documentation confirming 1:1 API coverage of collaboration/AI features, independent verification of parity, and any gaps/limitations list.

   • [claimed-docs] “Use the Postman API to programmatically manage your Postman assets and integrate Postman into your development toolchain.”
   • [claimed-docs] “Integrate Postman into your development toolchain”
   • [claimed-docs] “The Analytics API enables you to explore Postman’s analytics reports programmatically.”
   • [probe] “PROBE openapi: HTTP 200 at https://learning.postman.com/openapi.json — contains "openapi" key”
   • [probe] “official CLI documented at https://learning.postman.com/docs/postman-cli/postman-cli-overview/”
   • [claimed-docs] “The Postman CLI enables you to run collections, lint API schemas, run security and governance checks, and log in and out.”

   proof ↗⚑ flag

   Hoppscotch~partialprobed5/10

   Hoppscotch 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…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Hoppscotch
   Postman!disputedcontradicted4/10

   Postman's Collection format is JSON-based and documented as exportable (postman-docs-16, comm-14 recalls Postman's stated 'core goal' of JSON export for full data control), but multiple hands-on community reports concretely contradict free portability: users had all collections/workspaces wiped when declining a forced account creation (postman-comm-15), had to dig into hidden config folders to manually recover a backup (postman-comm-16), were pushed to a paid cloud subscription just to migrate data to a new machine (postman-comm-13), and reported secrets/environment data being silently uploaded to Postman's servers (postman-comm-6, postman-comm-12). missing for 10: an official bulk/full-account data export tool, evidence of successful account-free clean exits, and a rebuttal to the documented forced-login data-wipe incidents.

   • [claimed-docs] “Use Spec Hub to design your API’s structure, or use types in collections to design your API with the Postman Collection format.”
   • [community] “I remember when one of the 'Core Goals' of Postman was 'Complete control over your data - Keep simple JSON based data formats which can be e…”
   • [community] “I have been using postman offline without an account for a long time. Today when I opened the program it asked me to create an account. When…”
   • [community] “I was able to manually import/restore using a backup I found in ~/.config/Postman but I have no trust for continued use of this tool.”
   • [community] “I moved from Postman to RapidAPI when Postman tried to get me to sign up for their cloud service just to migrate my data to a new laptop.”
   • [community] “Be careful with Postman. It seems they upload all your secrets to their servers. We stopped to use it a time ago.”
   • [community] “Apparently Postman needs to be online in order to send 'telemetry': postman is logging all your secrets and environment variables.”

   proof ↗⚑ flag

   Hoppscotch~partialclaimed5/10

   Hoppscotch 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”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Hoppscotch
   Postman—none0/10

   Postman is a closed-source, proprietary SaaS/desktop product; no evidence of an open-source license for its core codebase is provided, and community comments actually reflect frustration with lock-in and lack of local/offline data control, not openness of source. Since the axis (open license to read source) applies to any product category, absence of evidence means 'none'.

   • [community] “Postman dug its own grave after selling out itself for VC money... The 'File over app' philosophy is a direction that we should be supportin…”
   • [community] “I remember when one of the 'Core Goals' of Postman was 'Complete control over your data - Keep simple JSON based data formats which can be e…”
   • [community] “My main gripe with Postman and Insomnia isn't actually the web based UI, but the lock-in. Postman especially tries to push people towards ge…”

   proof ↗⚑ flag

   Hoppscotch✓fullcommunity8/10

   Hoppscotch'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 …”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Hoppscotch
   Postman—none0/10

   Postman is a cloud-based SaaS product with a desktop client that syncs to Postman's servers; there is no evidence of a self-hostable core product (e.g., on-prem/enterprise server package). Community evidence even highlights forced cloud sync and telemetry requirements, but no self-hosting option is documented anywhere in the pack.

   • [community] “Be careful with Postman. It seems they upload all your secrets to their servers. We stopped to use it a time ago.”
   • [community] “It connects to their servers when it starts up; have to assume their server is down. It used to be so much nicer before they added this 'fea…”
   • [community] “Apparently Postman needs to be online in order to send 'telemetry': postman is logging all your secrets and environment variables.”
   • [community] “I have been using postman offline without an account for a long time. Today when I opened the program it asked me to create an account. When…”

   proof ↗⚑ flag

   Hoppscotch✓fullcommunity8/10

   Hoppscotch 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.”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Hoppscotch
   Postman—none0/10

   No evidence in the pack mentions data residency, region selection, or geographic storage controls for Postman workspaces/collections. Community evidence instead raises concerns about data being uploaded to Postman's servers and telemetry, but this doesn't address region choice specifically. missing for 10: any documentation of regional data residency options, EU/US data center selection, or enterprise data-locality controls.

   ⚑ flag

   Hoppscotch~partialclaimed6/10

   Hoppscotch 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.”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Postman—none0/10

   No evidence pack item addresses AI training data opt-out or a data-use policy control for AI features (Agent Mode/Postbot); in fact community reports raise concerns about data/telemetry being sent to Postman's servers without any documented opt-out for AI training use. Missing for 10: any documentation of an AI-training opt-out setting, privacy policy statement on model training, or admin control to restrict data use for AI training.

   • [community] “Be careful with Postman. It seems they upload all your secrets to their servers. We stopped to use it a time ago.”
   • [community] “Apparently Postman needs to be online in order to send 'telemetry': postman is logging all your secrets and environment variables.”

   proof ↗⚑ flag

   Hoppscotch—none0/10

   No 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.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Hoppscotch
   Postman—none0/10

   No documentation describes explicit data retention or deletion controls (e.g., configurable retention windows, GDPR-style delete API, data export/purge tools) for Postman. Community reports actually describe the opposite experience — data being wiped without consent, forced cloud account creation, and secrets/telemetry being uploaded to Postman's servers — reinforcing the absence of user-controlled retention/deletion.

   • [community] “One person had 'deleted' all his collections and workspaces after layoff... Postman support restored all the collections but the 'environmen…”
   • [community] “I moved from Postman to RapidAPI when Postman tried to get me to sign up for their cloud service just to migrate my data to a new laptop.”
   • [community] “I have been using postman offline without an account for a long time. Today when I opened the program it asked me to create an account. When…”
   • [community] “I was able to manually import/restore using a backup I found in ~/.config/Postman but I have no trust for continued use of this tool.”
   • [community] “Apparently Postman needs to be online in order to send 'telemetry': postman is logging all your secrets and environment variables.”

   proof ↗⚑ flag

   Hoppscotch~partialclaimed4/10

   Hoppscotch 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.”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Postman—none0/10

   No documentation in the evidence pack describes a telemetry/usage-tracking opt-out setting for Postman, and community reports indicate the opposite — users note Postman 'needs to be online in order to send telemetry' and that it uploads secrets/environment data without an apparent way to disable this (postman-comm-11, postman-comm-12, postman-comm-6). No first-party privacy/opt-out control is documented anywhere in the pack.

   • [community] “It connects to their servers when it starts up; have to assume their server is down. It used to be so much nicer before they added this 'fea…”
   • [community] “Apparently Postman needs to be online in order to send 'telemetry': postman is logging all your secrets and environment variables.”
   • [community] “Be careful with Postman. It seems they upload all your secrets to their servers. We stopped to use it a time ago.”

   proof ↗⚑ flag

   Hoppscotch—none0/10

   No 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.

   ⚑ flag

Docs generation

1. developerGenerate and publish API documentation from my collections or specs

   weight 2 · round drawn
   Postman—none0/10

   The evidence pack covers Postman's collections, mock servers, Spec Hub, CLI, and API, but no citation describes generating or publishing API documentation from collections/specs — a well-known Postman feature not evidenced here. missing for 10: explicit documentation generation/publish feature evidence, public doc hosting/sharing links, generated reference examples.

   ⚑ flag

   Hoppscotch—none0/10

   Hoppscotch 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…”

   proof ↗⚑ flag

Governance

1. platform-engineerLint API specs against configurable style and governance rules

   weight 3 · round to Postman
   Postman✓fullclaimed8/10

   Postman CLI explicitly supports checking API specs against configured governance rules ('Check API specifications against configured API governance rules' and 'run security and governance checks') and can be wired into CI/CD pipelines, matching the platform-engineer's need to lint specs against configurable style/governance rules. Missing for 10: no independent/hands-on evidence of custom rule authoring depth or third-party validation of linting accuracy.

   • [claimed-docs] “Check API specifications against configured API governance rules.”
   • [claimed-docs] “The Postman CLI enables you to run collections, lint API schemas, run security and governance checks, and log in and out.”
   • [claimed-docs] “You can also use the Postman CLI to run test collections as part of your continuous integration and continuous delivery (CI/CD) pipeline.”
   • [claimed-docs] “combine the Postman API with the Postman CLI to integrate Postman with your CI/CD workflow.”

   proof ↗⚑ flag

   Hoppscotch—none0/10

   Hoppscotch 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.

   ⚑ flag

Spec import export

1. developerDesign an API spec-first and export it as OpenAPI

   weight 2 · round to Postman
   Postman~partialclaimed5/10

   Postman's docs explicitly mention 'Spec Hub' for designing an API's structure before building requests/collections, supporting spec-first design (postman-docs-16, postman-docs-38). However, the evidence pack never explicitly documents exporting that spec as an OpenAPI file/format, only that specs can be created and CLI can 'lint API schemas' (postman-docs-32), leaving the export step unconfirmed. Missing for 10: explicit documentation of OpenAPI export/download from Spec Hub, and independent/hands-on confirmation of round-tripping a spec-first design to OpenAPI.

   • [claimed-docs] “Use Spec Hub to design your API’s structure, or use types in collections to design your API with the Postman Collection format.”
   • [claimed-docs] “Use [Spec Hub](/docs/design-apis/specifications/overview/) to design your API's structure, or use [types in collections](/docs/design-apis/c…”
   • [claimed-docs] “The Postman CLI enables you to run collections, lint API schemas, run security and governance checks, and log in and out.”

   proof ↗⚑ flag

   Hoppscotch—none0/10

   Evidence 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.”

   proof ↗⚑ flag

2. developerImport an OpenAPI spec to generate requests and collections

   weight 3 · round to Hoppscotch
   Postman~partialclaimed4/10

   Docs reference a 'Spec Hub' for designing API structure and using Postman Collection format types, which implies API-spec-driven authoring, but no evidence explicitly describes importing an OpenAPI spec file to auto-generate requests/collections. missing for 10: explicit OpenAPI import feature documentation, generated request/collection examples, and any independent confirmation of the import workflow.

   • [claimed-docs] “Use Spec Hub to design your API’s structure, or use types in collections to design your API with the Postman Collection format.”
   • [claimed-docs] “Use [Spec Hub](/docs/design-apis/specifications/overview/) to design your API's structure, or use [types in collections](/docs/design-apis/c…”
   • [claimed-docs] “Send API requests, group them in collections, and secure your data with Postman Vault.”

   proof ↗⚑ flag

   Hoppscotch~partialclaimed6/10

   Docs 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”

   proof ↗⚑ flag

Ai assist

1. ai-native userHave AI generate test cases or assertions for an endpoint from its spec or responses

   weight 2 · round to Postman
   Postman✓fullclaimed7/10

   Postman's Agent Mode/Postbot is documented to generate and update tests via natural language directly from requests/responses ('ask Agent Mode to add tests to requests', 'fix errors, update tests'), directly matching the AI-native test/assertion generation story. Missing for 10: independent/hands-on community corroboration of AI-generated test quality, and explicit documentation of generating tests directly from an OpenAPI/API spec rather than just live requests.

   • [claimed-docs] “With Agent Mode, you can turn your words into action across the API lifecycle. Send requests, fix errors, update tests, and more, using natu…”
   • [claimed-docs] “You can ask Agent Mode to add tests to requests, visualize responses, write documentation, and more.”
   • [claimed-docs] “Postbot is free to try on all Postman plans . Monthly usage is limited to 50 activities per user.”

   proof ↗⚑ flag

   Hoppscotch~partialclaimed5/10

   Docs 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…”

   proof ↗⚑ flag

Contract testing

1. platform-engineerValidate live responses against the API contract to catch drift

   weight 2 · round to Postman
   Postman~partialclaimed6/10

   Postman supports writing test scripts that assert on live response status/body/schema, contract/governance checks against API specs via the CLI, and mock servers to compare expected vs actual behavior, which together enable a platform engineer to catch drift between live responses and a contract. However, there's no dedicated 'contract testing' feature that explicitly diffs live responses against an OpenAPI/spec definition — it relies on manually written test scripts or governance rule checks rather than automated schema validation of live traffic. missing for 10: a first-party automated schema-diff/contract-validation feature (e.g., built-in OpenAPI response validation against live traffic), and independent/hands-on evidence confirming this workflow catches real drift in practice.

   • [claimed-docs] “Check API specifications against configured API governance rules.”
   • [claimed-docs] “Postman can run scripts before a request is sent (pre-request) or after (post-response).”
   • [claimed-docs] “Write scripts to add dynamic behavior to requests and collections. Perform API tests, add dynamic parameters, pass data between requests, an…”
   • [claimed-docs] “You can also use the Postman CLI to run test collections as part of your continuous integration and continuous delivery (CI/CD) pipeline.”
   • [claimed-docs] “You'll also learn how to save your request to a collection and write a basic test to validate the API response.”

   proof ↗⚑ flag

   Hoppscotch—none0/10

   Evidence 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.

   ⚑ flag

Testing

1. developerRun an entire collection as an automated test suite with a pass/fail report

   weight 3 · round to Postman
   Postman✓fullclaimed9/10

   Postman documents running collections with the Postman CLI (and Newman) which includes built-in reporters for pass/fail output, plus writing test scripts (pre-request/post-response) that assert on responses, and explicit CI/CD integration guidance for automated test suite runs. This covers the full workflow: writing tests, running a collection as a suite, and getting a pass/fail report. Missing for 10: independent/hands-on confirmation of the reporter output format or a third-party account of CI pass/fail usage.

   • [claimed-docs] “Run and manage collections with extensive configuration options and built-in reporters.”
   • [claimed-docs] “You can also use the Postman CLI to run test collections as part of your continuous integration and continuous delivery (CI/CD) pipeline.”
   • [claimed-docs] “Newman allows you to run and test a Postman Collections directly from the command-line.”
   • [claimed-docs] “The Postman CLI enables you to run collections, lint API schemas, run security and governance checks, and log in and out.”
   • [claimed-docs] “Postman can run scripts before a request is sent (pre-request) or after (post-response).”
   • [claimed-docs] “combine the Postman API with the Postman CLI to integrate Postman with your CI/CD workflow.”

   proof ↗⚑ flag

   Hoppscotch✓fullprobed8/10

   Hoppscotch'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”

   proof ↗⚑ flag

2. developerWrite test assertions against response status, body, and headers

   weight 3 · round to Postman
   Postman✓fullclaimed8/10

   Postman's docs confirm scripting-based test assertions via pre-request/post-response scripts (postman-docs-12, postman-docs-17), explicit test writing against API responses (postman-docs-29, postman-docs-33), and CI/CD execution of these tests via CLI/Newman (postman-docs-19, postman-docs-42). This directly covers assertions against status, body, and headers, which is Postman's classic 'Tests' tab functionality referenced across multiple docs. Missing for 10: no explicit doc snippet showing pm.test()/pm.response.to.have.status/header assertion syntax or independent hands-on confirmation of assertion behavior.

   • [claimed-docs] “Postman can run scripts before a request is sent (pre-request) or after (post-response).”
   • [claimed-docs] “Write scripts to add dynamic behavior to requests and collections. Perform API tests, add dynamic parameters, pass data between requests, an…”
   • [claimed-docs] “You'll also learn how to save your request to a collection and write a basic test to validate the API response.”
   • [claimed-docs] “You can ask Agent Mode to add tests to requests, visualize responses, write documentation, and more.”
   • [claimed-docs] “You can also use the Postman CLI to run test collections as part of your continuous integration and continuous delivery (CI/CD) pipeline.”
   • [claimed-docs] “Newman allows you to run and test a Postman Collections directly from the command-line.”

   proof ↗⚑ flag

   Hoppscotch~partialclaimed5/10

   Hoppscotch 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.”

   proof ↗⚑ flag