Postman vs Insomnia
free-tier · subscription-per-seat · enterprise-custom
·open-source · free-tier · subscription-per-seat · enterprise-custom
Insomnia wins · 21–21 (10 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to PostmanPostman'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 …”
Kong's developer docs (which host Insomnia's documentation) expose a working llms.txt at the domain root and individual doc pages are directly fetchable as markdown (.md) files, which is agent-friendly, but this is a shared Kong-wide resource rather than an Insomnia-specific llms.txt, and a probe for an Insomnia-specific markdown index (insomnia/.md) returned 404. Missing for 10: a dedicated Insomnia-specific llms.txt or explicit agent-onboarding docs, and confirmation Insomnia itself (the product) references or promotes this file to agents.
- [probe] “PROBE llms.txt: HTTP 200 at https://developer.konghq.com/llms.txt # developer.konghq.com > Kong's developer documentation for Kong Gateway,…”
- [probe] “PROBE docs-md: HTTP 404 at https://developer.konghq.com/insomnia/.md”
- [claimed-docs] “Insomnia provides the ability to chain requests. This means you can extract values from the responses of other requests while also sharing s…”
- [claimed-docs] “Pre-request scripts allow you to execute tasks before a request is sent.”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to PostmanPostman 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/”
Insomnia ships the Inso CLI, explicitly documented as designed for CI environments — it disables interactive prompts and returns exit codes to pass/fail builds, and supports test running, spec linting, and collection runs from CI/Git workflows without the GUI. This directly satisfies headless/automated execution for CI pipelines. Missing for 10: independent hands-on CI usage reports/case studies and more detail on advanced automation scenarios (e.g., parallelization, complex environment injection) beyond the docs themselves.
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
- [claimed-docs] “Use the Insomnia CLI to automate the execution of your API tests using your existing Git workflows.”
- [probe] “official CLI documented at https://developer.konghq.com/inso-cli/”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · round to InsomniaPostmannone0/10Evidence 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”
Insomnia has a documented MCP Client feature that connects to external MCP servers to access AI-ready tools, prompts, and resources, discovering and enabling invocation/testing of these elements directly in the app. This directly matches the story of plugging in MCP servers to use their tools. Missing for 10: independent/hands-on corroboration of the MCP client feature beyond first-party docs, and details on limitations or setup friction.
- [claimed-docs] “Use Insomnia to connect external Model Context Protocol (MCP) Servers to access AI-ready tools, prompts, and resources.”
- [claimed-docs] “The Insomnia MCP Client discovers these elements, which enables you to invoke, query, or test them directly in the app.”
- [claimed-docs] “Use MCP clients to connect Insomnia to Konnect for mocking, validating, and protecting requests in real time.”
ai-native userConnect an agent via an official MCP server
weight 3 · round to PostmanPostman 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”
Insomnianone0/10Evidence shows Insomnia acts as an MCP *client* (docs-14, docs-30, docs-46) that connects to external MCP servers, not as an MCP server that an agent could connect to. No documentation of Insomnia exposing its own official MCP server endpoint was found in the evidence pack.
- [claimed-docs] “Use MCP clients to connect Insomnia to Konnect for mocking, validating, and protecting requests in real time.”
- [claimed-docs] “The Insomnia MCP Client discovers these elements, which enables you to invoke, query, or test them directly in the app.”
- [claimed-docs] “Use Insomnia to connect external Model Context Protocol (MCP) Servers to access AI-ready tools, prompts, and resources.”
ai-native userUse an official CLI
weight 2 · round drawnPostman 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/”
Insomnia ships an official 'Inso CLI' documented for automating collection runs, linting OpenAPI specs, and running in CI pipelines with exit codes for pass/fail, which is exactly the kind of scriptable, agent-friendly interface an AI-native workflow would use. missing for 10: independent/hands-on community confirmation of Inso CLI usage and explicit framing of the CLI as AI/agent-oriented rather than just human CI tooling.
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
- [probe] “official CLI documented at https://developer.konghq.com/inso-cli/”
ai-native userDrive the product through a documented public API
weight 3 · round to PostmanPostman 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”
Insomnia does not publish a documented public REST/programmatic API for driving the app itself (probe found no OpenAPI/swagger spec for the product), but it does offer the Inso CLI for scripted automation of tests, linting, and collection runs, plus an extensibility plugin system — giving AI-native users some programmatic control, just not a true public API surface. missing for 10: a documented HTTP/SDK-style public API for controlling Insomnia, independent confirmation the Inso CLI/plugin surface is used for AI-agent automation.
- [claimed-docs] “Use the Insomnia CLI to automate the execution of your API tests using your existing Git workflows.”
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “Unlimited access to plugins or build your own”
- [probe] “PROBE openapi: all candidate paths 404 (https://developer.konghq.com/openapi.json, https://developer.konghq.com/swagger.json, https://develo…”
- [probe] “official CLI documented at https://developer.konghq.com/inso-cli/”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnPostmannone0/10Evidence 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).
Insomnianone0/10Insomnia offers RBAC for controlling access to its own resources, external vault integration for retrieving secrets, and environment variables for storing credentials, but there is no evidence of a feature to generate or issue scoped, least-privilege API credentials specifically for an AI agent to use. Given Insomnia's MCP client and AI features, this would be a plausible extension, but it's not documented anywhere in the evidence pack.
- [claimed-docs] “Use Role-based access control (RBAC) for fine-grain control over who can access which Insomnia resources.”
- [claimed-docs] “Insomnia supports integrating with external vault service providers to retrieve secret values automatically when sending requests.”
- [claimed-docs] “Use environments to define groups of variables that Insomnia applies across your requests. For example, you could create variables for base …”
- [claimed-docs] “Use Insomnia to connect external Model Context Protocol (MCP) Servers to access AI-ready tools, prompts, and resources.”
ai-native userBuild against official SDKs
weight 2 · round drawnPostmannone0/10Evidence 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”
Insomnianone0/10Evidence shows Insomnia's automation surface is the Inso CLI and plugin system, plus MCP client support, but no official SDK (e.g., a Node/Python/Go SDK) for programmatically building against Insomnia is documented anywhere in the pack.
- [claimed-docs] “Use the Insomnia CLI to automate the execution of your API tests using your existing Git workflows.”
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “Unlimited access to plugins or build your own”
- [probe] “official CLI documented at https://developer.konghq.com/inso-cli/”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to PostmanPostman 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”
Insomnia has narrow, specific AI features—generating mock servers from prompts/OpenAPI/URL and suggesting Git commit messages—but no evidence of AI analyzing request/response data to surface insights, debugging suggestions, or pattern recognition across a user's API data. Missing for 10: AI-driven analysis of actual request/response payloads, error/anomaly insights, or usage-pattern suggestions beyond mock generation and commit messages.
- [claimed-docs] “Creates a mock server from a prompt, OpenAPI definition, or live URL response. Automatically scaffolds routes, responses, and configurations…”
- [claimed-docs] “Auto-generate a mock server from a natural language prompt and one of the following input types: URL, OpenAPI, or JSON.”
- [claimed-docs] “AI-assisted mock server generation, which transforms prompts or API definitions into mock APIs.”
- [claimed-docs] “AI commit message suggestions, which help maintain clear and atomic commit histories.”
- [claimed-docs] “AI commit message suggestions, which help”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to PostmanPostman 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.”
Insomnianone0/10Insomnia offers CI-triggered test automation via Inso CLI and manual Collection Runner runs, but there is no evidence of autonomous, self-scheduling background automations (e.g., cron-like triggers or agents running unattended) — all automation examples require an external CI pipeline or manual invocation.
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “Use the Collection Runner to send multiple requests in a specific order”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to PostmanPostman 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.”
Insomnia does ship some built-in AI features—generating mock servers from a natural-language prompt/OpenAPI spec (insomnia-docs-10, insomnia-docs-29, insomnia-docs-51) and AI-generated commit message suggestions (insomnia-docs-35, insomnia-docs-52)—but these are narrow, single-purpose AI helpers rather than a general-purpose assistant to which a user can delegate broader tasks (e.g., writing tests, debugging requests, multi-step workflows). Missing for 10: evidence of a general conversational/agentic AI assistant embedded in the app, ability to delegate arbitrary tasks beyond mock/commit generation, and independent/hands-on confirmation of these AI features' quality.
- [claimed-docs] “Creates a mock server from a prompt, OpenAPI definition, or live URL response. Automatically scaffolds routes, responses, and configurations…”
- [claimed-docs] “Auto-generate a mock server from a natural language prompt and one of the following input types: URL, OpenAPI, or JSON.”
- [claimed-docs] “AI-assisted mock server generation, which transforms prompts or API definitions into mock APIs.”
- [claimed-docs] “AI commit message suggestions, which help maintain clear and atomic commit histories.”
- [claimed-docs] “AI commit message suggestions, which help”
ai-native userOperate the product with natural-language commands
weight 2 · round to PostmanPostman'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.”
Insomnia offers targeted AI/natural-language features—generating a mock server from a natural-language prompt and AI-assisted commit message suggestions—but there is no evidence of broader natural-language command control over core operations like creating/running requests, collections, or environments. Missing for 10: NL-driven request creation/execution, NL-based test/collection running, general chat-style control of the app, and independent verification of the AI features' reliability.
- [claimed-docs] “Creates a mock server from a prompt, OpenAPI definition, or live URL response. Automatically scaffolds routes, responses, and configurations…”
- [claimed-docs] “Auto-generate a mock server from a natural language prompt and one of the following input types: URL, OpenAPI, or JSON.”
- [claimed-docs] “AI commit message suggestions, which help maintain clear and atomic commit histories.”
- [claimed-docs] “AI-assisted mock server generation, which transforms prompts or API definitions into mock APIs.”
- [claimed-docs] “AI commit message suggestions, which help”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to PostmanPostman'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…”
Insomnia lets users import OpenAPI/Swagger specs, preview them with linting, auto-generate code snippets in 12+ languages, and directly send/run requests against the spec — effectively turning any imported API spec into an interactive, runnable reference (insomnia-docs-16, insomnia-docs-17, insomnia-docs-18, insomnia-docs-5, insomnia-docs-48). However this requires manually importing a spec rather than offering a built-in, browsable reference experience, and there's no evidence of a dedicated 'try-it-out' documentation portal or AI-native example runner. Missing for 10: a first-party interactive documentation/reference viewer (vs. spec design+testing workflow), and independent/hands-on evidence of this specific 'explore reference with runnable examples' flow.
- [claimed-docs] “View a generated preview of your spec in the right pane.”
- [claimed-docs] “Automatically linted. Errors display at the bottom of the center pane and include error type, line number, and error message”
- [claimed-docs] “Generate code snippets automatically in over 12 different programming languages.”
- [claimed-docs] “Build and iterate on your OpenAPI specs to design your next API.”
- [claimed-docs] “Import a Postman collection or OpenAPI spec into Insomnia Method: UI → Import → choose File/Clipboard/URL.”
- [claimed-docs] “Use the Collection Runner to send multiple requests in a specific order”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnA 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…”
Insomnia's Design Hub lets users build/iterate OpenAPI specs, preview and lint them, and export/import in OpenAPI 3.0/3.1 (plus Swagger, Postman, HAR formats), and the Inso CLI can lint specs in CI (`inso lint spec`). This directly delivers a machine-readable, downloadable spec workflow. Missing for 10: no independent/hands-on confirmation of the export UX or format fidelity, and the Kong docs site itself has no discoverable OpenAPI spec (probe-3), slightly muddying 'AI-native' machine-readability of the docs layer.
- [claimed-docs] “Build and iterate on your OpenAPI specs to design your next API.”
- [claimed-docs] “Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “View a generated preview of your spec in the right pane.”
- [claimed-docs] “Automatically linted. Errors display at the bottom of the center pane and include error type, line number, and error message”
- [claimed-docs] “Import formats: Insomnia JSON (v4), Insomnia YAML (v5), Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “Import a Postman collection or OpenAPI spec into Insomnia Method: UI → Import → choose File/Clipboard/URL.”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnPostman'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…”
Insomnia supports mock servers (including AI-generated ones from a prompt/OpenAPI spec) and environment variables that can separate dev/staging/production configs, letting users test flows without hitting real production endpoints. However, there is no explicit 'sandbox environment' feature or documented guarantee of production-data isolation — it relies on users manually configuring mock servers/environments rather than a dedicated sandboxed testing mode. Missing for 10: an explicit sandbox/staging isolation feature, documentation guaranteeing no production data exposure, and independent evidence of AI agents using this for safe testing.
- [claimed-docs] “The Insomnia Cloud mock servers allow you to create a mock endpoint in a few steps.”
- [claimed-docs] “Creates a mock server from a prompt, OpenAPI definition, or live URL response. Automatically scaffolds routes, responses, and configurations…”
- [claimed-docs] “Dynamic mocking renders Liquid templates so responses can include: - Data from the request (headers, query parameters, path, or body). - Ran…”
- [claimed-docs] “Auto-generate a mock server from a natural language prompt and one of the following input types: URL, OpenAPI, or JSON.”
- [claimed-docs] “Use environments to define groups of variables that Insomnia applies across your requests.”
- [claimed-docs] “Use environments to define groups of variables that Insomnia applies across your requests. For example, you could create variables for base …”
- [claimed-docs] “Global environments, which can be accessed by all collections in a project * Collection environments, which can be accessed by all requests …”
- [claimed-docs] “AI-assisted mock server generation, which transforms prompts or API definitions into mock APIs.”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnPostmannone0/10The 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”
Insomnianone0/10The evidence pack shows Insomnia has versioned file/import formats (e.g., Insomnia JSON v4/YAML v5, OpenAPI 3.0/3.1) but there is no documentation of a formal versioning scheme or deprecation policy for any Insomnia-exposed API, plugin API, or CLI interface that an AI agent would rely on for stability guarantees.
- [claimed-docs] “Import formats: Insomnia JSON (v4), Insomnia YAML (v5), Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to PostmanPostman 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.”
Insomnia's Collection Runner and unlimited collection runs let users execute many requests/tests in bulk, and the Inso CLI automates this across CI pipelines, giving solid bulk-execution support (insomnia-docs-4, insomnia-docs-20, insomnia-docs-39, insomnia-docs-53, insomnia-docs-55). However, evidence is limited to running/testing many requests together—there's no documented bulk editing, bulk tagging, or bulk deletion of items, and no independent/hands-on confirmation of this specific bulk workflow. Missing for 10: evidence of bulk editing/management of many items beyond execution, and independent corroboration of the Collection Runner/Inso CLI bulk workflow.
- [claimed-docs] “Automatically test multiple requests in your collections, with unlimited collection runs.”
- [claimed-docs] “Use the Collection Runner to send multiple requests in a specific order”
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “Unlimited collection runs * Unlimited environments”
- [claimed-docs] “Test complex workflows by chaining the responses from requests together”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to InsomniaPostman 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.”
Insomnia supports pre-request and after-response scripts that automatically execute logic tied to request lifecycle events, plus chained requests and CI-triggered automation via the Inso CLI, which constitutes a form of automatic action-on-event behavior. However, there is no evidence of a general-purpose rule/trigger system for arbitrary events (e.g., webhooks, scheduled triggers, or cross-tool event listeners) beyond the request-send/response lifecycle. missing for 10: evidence of a broader event-trigger/rule engine beyond request scripting, and independent confirmation of automation reliability.
- [claimed-docs] “Pre-request scripts allow you to execute tasks before a request is sent.”
- [claimed-docs] “Pre-request scripts allow you to execute tasks before a request is sent. They can be used to: * Manipulate environment variables or authenti…”
- [claimed-docs] “Pre-request and after-response scripting to add logic to your requests”
- [claimed-docs] “Test complex workflows by chaining the responses from requests together”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnPostmannone0/10The 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.”
Insomnianone0/10Insomnia offers Inso CLI for CI-triggered test runs and collection runners, but there is no evidence of any built-in scheduler or recurring-job feature (e.g., cron-like monitors) comparable to what competitors offer; scheduling would have to be bolted on via external CI cron jobs, which isn't documented as part of Insomnia itself.
ai-native userVersion, review, and roll back my automations
weight 1 · round to InsomniaPostman 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…”
Insomnia's Git Sync connects collections/environments directly to a Git repo, offers a merge view to review and resolve conflicts, and lets you convert projects between Local Vault, Cloud Sync, and Git Sync — giving version history and review workflows for automations (collections, scripts, environments). Rollback is implied via standard Git history rather than a dedicated in-app rollback UI. Missing for 10: explicit in-app rollback/versioned-restore feature beyond relying on external Git tooling, and independent hands-on confirmation of the merge/review workflow in practice.
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “Insomnia opens a merge view so you can review and resolve conflicts without leaving the app.”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository. Insomnia does not host or manage it.”
- [claimed-docs] “Collaboratively create APIs with an unlimited number of contributors (free accounts allow unlimited contributors on one project) and git ver…”
- [claimed-docs] “You can convert a project to: - Local Vault - Cloud Sync - Git Sync”
- [claimed-docs] “You can convert a project to: Local Vault, Cloud Sync, Git Sync”
- [github] “Git Sync: for Git storage using any 3rd party Git repository, without going through the cloud.”
Ci scripting — stories about ci scripting in this arenaCi scripting
Stories about ci scripting in this arena
Ci
developerRun my API test collections in CI with a CLI and fail the build on regressions
weight 3 · round drawnPostman 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/”
Insomnia's docs explicitly describe the Inso CLI as designed for CI environments with disabled prompts and pass/fail exit codes, plus commands like 'inso lint spec' to fail builds on errors, and general CLI automation of test collections tied to Git workflows. missing for 10: independent/hands-on confirmation of CI CLI reliability, real-world CI pipeline examples beyond vendor docs
- [claimed-docs] “Use the Insomnia CLI to automate the execution of your API tests using your existing Git workflows.”
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [probe] “official CLI documented at https://developer.konghq.com/inso-cli/”
Monitors
developerSchedule collection runs as monitors that alert me when an API breaks
weight 2 · round to InsomniaPostmannone0/10The 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.
Insomnia's Inso CLI can run collection tests in CI with exit codes to pass/fail builds, and can lint OpenAPI specs to fail builds on errors, which developers could wire into a scheduled CI job to approximate a monitor. However, there is no evidence of a native scheduling feature or built-in alerting mechanism (email/Slack/webhook) for failed runs, unlike a dedicated Monitors product — the burden of scheduling and alerting falls on external CI tooling. missing for 10: native monitor scheduling UI, built-in alert/notification channel on failure, and any hands-on confirmation this workflow is used for uptime-style monitoring.
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
- [claimed-docs] “Use the Collection Runner to send multiple requests in a specific order”
- [claimed-docs] “Unlimited collection runs * Unlimited environments”
Scripting
developerScript pre-request and post-response logic to chain requests and massage data
weight 2 · round to PostmanPostman 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…”
Insomniadisputedcontradicted6/10Docs clearly document pre-request and after-response scripting, chaining responses across requests, environment variables, and CI automation via Inso CLI (insomnia-docs-2, -21, -37, -38, -39, -53), which directly matches the story. However, a hands-on community comment contradicts this, calling Insomnia's scripting/glue-code support 'garbage-tier' compared to Postman (insomnia-comm-15), indicating the scripting capability may be weaker or less mature in practice than the docs suggest. Missing for 10: independent verification of scripting robustness/parity with competitors, and more recent hands-on confirmation resolving the community critique.
- [claimed-docs] “Pre-request scripts allow you to execute tasks before a request is sent.”
- [claimed-docs] “Pre-request scripts allow you to execute tasks before a request is sent. They can be used to: * Manipulate environment variables or authenti…”
- [claimed-docs] “Pre-request and after-response scripting to add logic to your requests”
- [claimed-docs] “Test complex workflows by chaining the responses from requests together”
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [community] “'Even insomnia had garbage-tier glue code support, something that was very much missing coming from Postman,' notes a user comparing scripti…”
Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaboration
Working as a team — sharing, comments, roles, simultaneous editing
Access control
platform-engineerControl who can view or edit APIs and collections with roles and permissions
weight 2 · round to PostmanPostman 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.”
Insomnia documents RBAC for fine-grained control over Insomnia resources and organizations for secure collaboration/sharing, plus SAML 2.0 SSO for identity, directly matching the platform-engineer's need to control who can view/edit APIs and collections. However, there's no detail on granularity (e.g., per-collection vs per-project roles), no independent/hands-on validation of RBAC in practice, and it's gated behind paid tiers per pricing page rather than shown in a workflow. Missing for 10: detailed documentation on role granularity/permission scopes for collections specifically, independent or community validation that RBAC works as described, and any hands-on walkthrough of setting collection-level permissions.
- [claimed-docs] “Use Role-based access control (RBAC) for fine-grain control over who can access which Insomnia resources.”
- [claimed-docs] “Role-based access control (RBAC)”
- [claimed-docs] “Insomnia organizations allows users to share collections and environments safely and securely with their colleagues.”
- [claimed-docs] “You can use any identity provider (IdP) that supports SAML 2.0.”
Api catalog
platform-engineerPublish an internal catalog or portal where teams discover and consume our APIs
weight 2 · round to PostmanPostman 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…”
Insomnianone0/10Insomnia's evidence covers request collaboration, organizations, Git sync, and RBAC for sharing collections among teammates inside the app, but nothing describes a published catalog or developer portal for broader API discovery/consumption by other teams. missing for 10: any mention of a public/internal API catalog, developer portal, or discovery UI outside the Insomnia app itself.
- [claimed-docs] “Insomnia organizations allows users to share collections and environments safely and securely with their colleagues.”
- [claimed-docs] “Use Role-based access control (RBAC) for fine-grain control over who can access which Insomnia resources.”
- [claimed-docs] “Collaboratively create APIs with an unlimited number of contributors (free accounts allow unlimited contributors on one project) and git ver…”
Team workspaces
developerShare collections with my team in a synced shared workspace
weight 3 · round to InsomniaFirst-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…”
Insomnia organizations support sharing collections/environments securely with colleagues, with RBAC, Cloud Sync, and Git Sync as alternate sync backends, plus merge conflict resolution for team workflows. missing for 10: independent/hands-on evidence of team sync experience (community comments focus on rug-pull login requirement and lightweight vs bloat, not team sync workflow specifics), and no detail on real-time collaboration limits or seat/team size constraints.
- [claimed-docs] “Insomnia organizations allows users to share collections and environments safely and securely with their colleagues.”
- [claimed-docs] “Use Role-based access control (RBAC) for fine-grain control over who can access which Insomnia resources.”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “Insomnia opens a merge view so you can review and resolve conflicts without leaving the app.”
- [claimed-docs] “You can convert a project to: - Local Vault - Cloud Sync - Git Sync”
- [claimed-docs] “Collaboratively create APIs with an unlimited number of contributors (free accounts allow unlimited contributors on one project) and git ver…”
- [claimed-docs] “At no point in the sync process can the Insomnia servers read or access sensitive application project data.”
Collections workspaces — stories about collections workspaces in this arenaCollections workspaces
Stories about collections workspaces in this arena
Collections
developerStore collections as plain text files in my repo and version them with git
weight 3 · round to InsomniaPostmannone0/10Postman'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…”
Insomnia's Git Sync feature explicitly stores project/collection data directly in a user's own Git repository as files (not on Insomnia's servers), supports merge conflict resolution, and can be toggled per-project alongside Cloud/Local storage — directly matching the story. Documentation also confirms this is a longstanding, git-native workflow (git version control mentioned for collaborative API design) and the GitHub README corroborates 'Git Sync: for Git storage using any 3rd party Git repository.' Missing for 10: independent hands-on confirmation of the exact plain-text file format on disk and no community verification of git-diff friendliness.
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “Insomnia opens a merge view so you can review and resolve conflicts without leaving the app.”
- [claimed-docs] “You can convert a project to: - Local Vault - Cloud Sync - Git Sync”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository. Insomnia does not host or manage it.”
- [claimed-docs] “You can convert a project to: Local Vault, Cloud Sync, Git Sync”
- [claimed-docs] “Collaboratively create APIs with an unlimited number of contributors (free accounts allow unlimited contributors on one project) and git ver…”
- [github] “Git Sync: for Git storage using any 3rd party Git repository, without going through the cloud.”
developerImport and export collections in portable formats to move between tools
weight 2 · round to InsomniaEvidence 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.”
Docs explicitly detail import/export in multiple portable formats (Insomnia JSON/YAML, Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, cURL) with UI import methods and Inso CLI support for automation/CI, plus Git Sync for version-controlled portability across tools. Missing for 10: no independent hands-on verification of round-trip fidelity between tools beyond vendor docs.
- [claimed-docs] “Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “Import formats: Insomnia JSON (v4), Insomnia YAML (v5), Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “Import a Postman collection or OpenAPI spec into Insomnia Method: UI → Import → choose File/Clipboard/URL.”
- [claimed-docs] “Import your tests from Postman”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
developerOrganize API requests into collections and folders and rerun them anytime
weight 3 · round to InsomniaPostman'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…”
Insomnia's docs clearly show organizing requests into collections/folders, with Collection Runner to rerun multiple requests in order, unlimited collection runs, environments scoped to collections/folders, and persistent storage via Git Sync/Cloud Sync for rerunning anytime. Community evidence corroborates long-term real-world use of saved/frequently-used requests. Missing for 10: independent hands-on verification specifically of folder-nesting UX and rerun reliability at scale beyond vendor docs.
- [claimed-docs] “Use the Collection Runner to send multiple requests in a specific order”
- [claimed-docs] “Automatically test multiple requests in your collections, with unlimited collection runs.”
- [claimed-docs] “Unlimited collection runs * Unlimited environments”
- [claimed-docs] “Use environments to define groups of variables that Insomnia applies across your requests.”
- [claimed-docs] “Global environments, which can be accessed by all collections in a project * Collection environments, which can be accessed by all requests …”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [community] “I've been using [cocoa-rest-client] for a couple of years, I just tried Insomnia and I think I'll be switching: having the ability to call f…”
Offline
developerWork fully offline in a local workspace without a cloud account
weight 2 · round to InsomniaPostmandisputedcontradicted4/10Docs 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…”
Insomniadisputedcontradicted5/10Insomnia's docs describe offline-friendly options — Scratch Pad requires 'No login ever required' (insomnia-docs-31), a 'Local Vault' project-storage mode (insomnia-docs-32/45), and Git Sync that keeps data in the user's own repo without touching Insomnia's cloud (insomnia-gh-1, insomnia-docs-22/44). However, a first-hand community report states the main Insomnia REST client 'now requires an account,' prompting users to call it a 'rug pull' and switch to fully offline-first alternatives like Bruno (insomnia-comm-14), directly contradicting the no-account claim for general (non-Scratch-Pad) usage. missing for 10: clear vendor confirmation that the main workspace (not just Scratch Pad) can be used indefinitely without ever creating a cloud account, and independent hands-on verification resolving the community complaint.
- [claimed-docs] “No login ever required for Scratch Pad”
- [claimed-docs] “You can convert a project to: - Local Vault - Cloud Sync - Git Sync”
- [claimed-docs] “You can convert a project to: Local Vault, Cloud Sync, Git Sync”
- [github] “Git Sync: for Git storage using any 3rd party Git repository, without going through the cloud.”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository. Insomnia does not host or manage it.”
- [community] “Insomnia REST client now requires an account, prompting users to seek alternatives; one commenter says 'Tired of these rug pulls' and lists …”
Protocols
developerSend GraphQL, gRPC, WebSocket, and SSE requests, not just REST
weight 2 · round to InsomniaDocs 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]”
Docs explicitly confirm HTTP, gRPC, GraphQL, and WebSocket request support (insomnia-docs-15, insomnia-docs-7/43, insomnia-docs-26), with GraphQL type-aware autocomplete and gRPC protobuf upload support. SSE is not explicitly named in the docs, though WebSocket/streaming support is documented. missing for 10: explicit SSE (Server-Sent Events) documentation, independent hands-on corroboration of multi-protocol usage.
- [claimed-docs] “With Insomnia, you can send requests via HTTP, gRPC, GraphQL, and WebSockets.”
- [claimed-docs] “Insomnia supports making gRPC requests.”
- [claimed-docs] “Insomnia supports making gRPC requests. You can create one by clicking the + button on the left panel of a collection and selecting gRPC Req…”
- [claimed-docs] “Insomnia uses this type system to provide auto-completion and linting of GraphQL queries.”
- [claimed-docs] “Insomnia allows you to upload Protobuf files to a request. You can upload a single file or a directory containing multiple files.”
- [github] “Debug APIs using the most popular protocols and formats.”
Environments secrets — stories about environments secrets in this arenaEnvironments secrets
Stories about environments secrets in this arena
Environments
developerSwitch requests between dev, staging, and prod using environment variable sets
weight 3 · round to InsomniaPostman 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…”
Insomnia explicitly supports environments as groups of variables (base URLs, tokens, credentials) with global, collection, and folder-level scoping, enabling switching between dev/staging/prod configurations; unlimited environments are confirmed in pricing docs. Missing for 10: no explicit hands-on/community example of a dev/staging/prod switching workflow, only first-party docs.
- [claimed-docs] “Use environments to define groups of variables that Insomnia applies across your requests.”
- [claimed-docs] “Use environments to define groups of variables that Insomnia applies across your requests. For example, you could create variables for base …”
- [claimed-docs] “Global environments, which can be accessed by all collections in a project * Collection environments, which can be accessed by all requests …”
- [claimed-docs] “Unlimited collection runs * Unlimited environments”
Secrets
platform-engineerKeep credentials out of shared files with masked secrets or an external vault integration
weight 2 · round to InsomniaPostmandisputedcontradicted4/10Postman 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.”
Insomnia explicitly documents external vault integration to retrieve secret values automatically when sending requests, and environments are described as a way to store credentials/tokens without hardcoding them in shared collection files. RBAC and organization-level sharing controls further support keeping secrets scoped safely. Missing for 10: explicit documentation of a 'masked' or obfuscated secret display feature in the UI, and independent/hands-on confirmation that vault integration works reliably in practice.
- [claimed-docs] “Insomnia supports integrating with external vault service providers to retrieve secret values automatically when sending requests.”
- [claimed-docs] “Use environments to define groups of variables that Insomnia applies across your requests. For example, you could create variables for base …”
- [claimed-docs] “Use environments to define groups of variables that Insomnia applies across your requests.”
- [claimed-docs] “Use Role-based access control (RBAC) for fine-grain control over who can access which Insomnia resources.”
Gateway traffic — stories about gateway traffic in this arenaGateway traffic
Stories about gateway traffic in this arena
Ai gateway
ai-native userProxy and govern LLM/MCP traffic (token limits, prompt guards, provider routing) through the platform
weight 2 · round to PostmanPostman's Fabric Gateway lets teams register and expose MCP servers (postman-docs-7), which touches the 'govern MCP traffic' idea, but there is no evidence of token limits, prompt/prompt-guard policies, or LLM provider routing/proxying features. missing for 10: token-limit controls, prompt guard/safety policies, LLM provider routing configuration, and any traffic-proxy/rate-limiting documentation for LLM calls.
- [claimed-docs] “This guide walks you through registering a Model Context Protocol (MCP) server with the gateway and making it available to your team.”
Insomnianone0/10Insomnia's MCP support is client-side only (docs-30, docs-46) — it lets users discover and invoke external MCP servers' tools/prompts, and a brief mention of connecting to Konnect for 'protecting requests' (docs-14), but there is no evidence of built-in token-limit enforcement, prompt guards, or LLM provider routing/proxying within Insomnia itself. Missing for 10: any documentation of token/rate limiting, prompt injection guards, or multi-provider routing/proxy governance features.
- [claimed-docs] “Use MCP clients to connect Insomnia to Konnect for mocking, validating, and protecting requests in real time.”
- [claimed-docs] “The Insomnia MCP Client discovers these elements, which enables you to invoke, query, or test them directly in the app.”
- [claimed-docs] “Use Insomnia to connect external Model Context Protocol (MCP) Servers to access AI-ready tools, prompts, and resources.”
Gateway ops
platform-engineerManage API infrastructure as declarative config and sync it from CI (GitOps/APIOps)
weight 2 · round to InsomniaPostman'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.”
Insomnia supports Git Sync so projects/specs/collections live as files in a Git repo, and Inso CLI is explicitly designed to run in CI (disabling prompts, providing exit codes) to lint OpenAPI specs and run tests as part of pipelines. This gives a real GitOps-style workflow for API design/testing artifacts, but Insomnia manages API client/design/test config, not actual gateway infrastructure (routes, plugins, gateway resources) — that lives in Kong Gateway/Konnect, not Insomnia. Missing for 10: evidence of declaratively managing live gateway/infrastructure resources (not just specs/tests) from Insomnia, and independent/hands-on confirmation of CI pipelines using Inso CLI successfully.
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository. Insomnia does not host or manage it.”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “Automate your tests with Inso CLI”
- [github] “Git Sync: for Git storage using any 3rd party Git repository, without going through the cloud.”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to PostmanPostman 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.”
Insomnia ships an official CLI (Inso CLI) that can run collections, lint OpenAPI specs, and automate tests in CI (insomnia-docs-3, -39, -49, -53, insomnia-probe-4), giving CLI/automation parity for a meaningful subset of workflows. However, there's no evidence of a full programmatic/API surface covering all UI capabilities (e.g., AI-assisted mock server creation, GraphQL design/linting, gRPC/Protobuf uploads, environment/Git-sync management, RBAC) — these remain UI-only per the docs. A community comment even flags weak scripting/glue-code support relative to competitors (insomnia-comm-15). missing for 10: CLI/API coverage for mock servers, GraphQL/gRPC workflows, environment & Git sync management, and independent confirmation that Inso CLI matches full UI functionality.
- [claimed-docs] “Use the Insomnia CLI to automate the execution of your API tests using your existing Git workflows.”
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [probe] “official CLI documented at https://developer.konghq.com/inso-cli/”
- [community] “'Even insomnia had garbage-tier glue code support, something that was very much missing coming from Postman,' notes a user comparing scripti…”
ai-native userExport all of my data in open formats and leave
weight 3 · round to InsomniaPostmandisputedcontradicted4/10Postman'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.”
Insomnia supports export in multiple open formats (Postman v2, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, cURL, plus its own JSON/YAML) and Git Sync keeps project data in a user-controlled repository rather than locked in a proprietary cloud, giving strong data portability. However, there's no explicit 'export everything' bulk/full-account export guarantee (e.g., all environments, secrets, RBAC configs, org settings) and no independent verification that exported data is fully lossless/complete outside vendor docs. missing for 10: evidence of a comprehensive full-account/workspace export (not just collections), independent/hands-on confirmation of lossless round-trip export, and documentation on exporting non-collection data like vault secrets or org settings.
- [claimed-docs] “Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “Import formats: Insomnia JSON (v4), Insomnia YAML (v5), Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository. Insomnia does not host or manage it.”
- [github] “Git Sync: for Git storage using any 3rd party Git repository, without going through the cloud.”
- [claimed-docs] “You can convert a project to: - Local Vault - Cloud Sync - Git Sync”
- [claimed-docs] “You can convert a project to: Local Vault, Cloud Sync, Git Sync”
ai-native userRead the product's source under an open license
weight 2 · round to InsomniaPostmannone0/10Postman 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…”
The official GitHub repository explicitly ships an Apache-2.0 LICENSE file, confirming Insomnia's source code is available under a recognized open-source license for anyone (including AI-native users) to read. Missing for 10: independent scrutiny of whether all components (e.g., cloud sync backend) are covered by the same license, and no third-party audit confirming license accuracy beyond the repo itself.
- [github] “Apache License Version 2.0, January 2004 — repository LICENSE file; the README's License section states: [Apache-2.0](LICENSE) (c) Insomnia …”
ai-native userSelf-host the core product
weight 3 · round to InsomniaPostmannone0/10Postman 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…”
Insomnia's core client is Apache-2.0 licensed and open source, and Git Sync explicitly keeps all project data in the user's own Git repo with 'Insomnia does not host or manage it,' letting AI-native users avoid the vendor's cloud entirely. However, there is no documented self-hosted server/backend package (e.g., a self-hosted sync or collaboration server) analogous to on-prem deployments some competitors offer—self-hosting here is effectively 'run the open-source desktop client + your own git remote,' not a full self-hosted service stack. Missing for 10: an official self-hosted server/Docker deployment guide, and independent confirmation that self-built/self-hosted setups work end-to-end.
- [github] “Apache License Version 2.0, January 2004 — repository LICENSE file; the README's License section states: [Apache-2.0](LICENSE) (c) Insomnia …”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository. Insomnia does not host or manage it.”
- [claimed-docs] “At no point in the sync process can the Insomnia servers read or access sensitive application project data.”
- [claimed-docs] “You can convert a project to: - Local Vault - Cloud Sync - Git Sync”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round to InsomniaPostmannone0/10No 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.
Insomnia lets users choose storage mode—Local Vault, Cloud Sync, or Git Sync to a self-hosted/3rd-party repo—giving some control over where data physically resides, and Kong states its cloud servers cannot read synced project data. However there is no evidence of selectable geographic region/data-residency options within Insomnia's cloud offering itself. Missing for 10: explicit region selection for cloud-hosted data, documented data-residency/compliance zones, independent confirmation of storage location guarantees.
- [claimed-docs] “You can convert a project to: - Local Vault - Cloud Sync - Git Sync”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “At no point in the sync process can the Insomnia servers read or access sensitive application project data.”
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnPostmannone0/10No 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.”
Insomnianone0/10Insomnia's docs describe AI features (mock generation, commit suggestions) and data-security claims about sync servers not reading project data, but there is no evidence of any control or policy letting users opt out of their data being used for AI model training.
- [claimed-docs] “At no point in the sync process can the Insomnia servers read or access sensitive application project data.”
- [claimed-docs] “AI-assisted mock server generation, which transforms prompts or API definitions into mock APIs.”
- [claimed-docs] “AI commit message suggestions, which help”
ai-native userControl data retention and deletion
weight 2 · round to InsomniaPostmannone0/10No 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.”
Insomnia lets users choose where data lives (Local Vault, Git Sync, Cloud Sync) and states its servers cannot read synced project data, plus a no-login Scratch Pad mode, which gives meaningful control over data storage/retention posture. However there is no explicit documentation of account/data deletion mechanisms, retention periods, or GDPR-style data export/erasure workflows. Missing for 10: explicit data deletion/retention policy documentation, account/data purge controls, independent confirmation of these claims.
- [claimed-docs] “You can convert a project to: - Local Vault - Cloud Sync - Git Sync”
- [claimed-docs] “You can convert a project to: Local Vault, Cloud Sync, Git Sync”
- [claimed-docs] “At no point in the sync process can the Insomnia servers read or access sensitive application project data.”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository.”
- [claimed-docs] “Git Sync connects Insomnia directly to your Git repository. Your project data stays in your repository. Insomnia does not host or manage it.”
- [claimed-docs] “No login ever required for Scratch Pad”
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnPostmannone0/10No 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.”
Spec design — stories about spec design in this arenaSpec design
Stories about spec design in this arena
Docs generation
developerGenerate and publish API documentation from my collections or specs
weight 2 · round to InsomniaPostmannone0/10The 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.
Insomnia's design mode lets you build/iterate on OpenAPI specs, view a generated preview, get linting and auto-generated code snippets in 12+ languages, which serves as a form of documentation generation from specs (insomnia-docs-5, insomnia-docs-16, insomnia-docs-17, insomnia-docs-18). However, there is no evidence of a dedicated 'publish' feature (e.g., hosting a documentation site or public API reference) — only in-app preview and collaborative editing via Git are documented. Missing for 10: a documented publish/export-to-hosted-docs capability, evidence of turning collections (not just specs) into shareable documentation, and any independent confirmation of a publishing workflow.
- [claimed-docs] “Build and iterate on your OpenAPI specs to design your next API.”
- [claimed-docs] “View a generated preview of your spec in the right pane.”
- [claimed-docs] “Automatically linted. Errors display at the bottom of the center pane and include error type, line number, and error message”
- [claimed-docs] “Generate code snippets automatically in over 12 different programming languages.”
- [claimed-docs] “Collaboratively create APIs with an unlimited number of contributors (free accounts allow unlimited contributors on one project) and git ver…”
Governance
platform-engineerLint API specs against configurable style and governance rules
weight 3 · round to PostmanPostman 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.”
Insomnia's Design view auto-lints OpenAPI specs showing error type/line/message (insomnia-docs-17), and the Inso CLI can run 'inso lint spec' in CI to fail builds on errors (insomnia-docs-49, insomnia-docs-53), giving a platform-engineer a way to gate specs on validation issues. However, there is no evidence of configurable style/governance rulesets (e.g., custom rule files, organization-wide style guides, or Spectral-like rule configuration) — the linting appears to be basic schema/structural validation rather than customizable governance policy enforcement. Missing for 10: evidence of configurable lint rule files or style-guide customization, evidence of org-level governance policy enforcement, and independent confirmation the lint rules can be tailored beyond basic OpenAPI validity checks.
- [claimed-docs] “Automatically linted. Errors display at the bottom of the center pane and include error type, line number, and error message”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “View a generated preview of your spec in the right pane.”
Spec import export
developerDesign an API spec-first and export it as OpenAPI
weight 2 · round to InsomniaPostman'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.”
Insomnia has a dedicated 'Design' feature for building OpenAPI specs with live preview, automatic linting, and code-snippet generation, and it supports full import/export of OpenAPI 3.0/3.1 specs (including via the inso CLI for CI linting), directly matching a spec-first workflow with OpenAPI export. missing for 10: independent hands-on validation of the spec-design workflow specifically (community evidence only discusses general client usage, not OpenAPI spec-first design).
- [claimed-docs] “Build and iterate on your OpenAPI specs to design your next API.”
- [claimed-docs] “View a generated preview of your spec in the right pane.”
- [claimed-docs] “Automatically linted. Errors display at the bottom of the center pane and include error type, line number, and error message”
- [claimed-docs] “Generate code snippets automatically in over 12 different programming languages.”
- [claimed-docs] “Collaboratively create APIs with an unlimited number of contributors (free accounts allow unlimited contributors on one project) and git ver…”
- [claimed-docs] “Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “Import formats: Insomnia JSON (v4), Insomnia YAML (v5), Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
- [probe] “official CLI documented at https://developer.konghq.com/inso-cli/”
developerImport an OpenAPI spec to generate requests and collections
weight 3 · round to InsomniaDocs 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.”
Insomnia's docs explicitly list OpenAPI 3.0/3.1 (and Swagger) as supported import formats and describe the UI flow (Import → File/Clipboard/URL) to bring specs into collections, with CI-side linting via `inso lint spec`. missing for 10: independent/hands-on confirmation that OpenAPI import correctly generates requests/collections without manual fixes.
- [claimed-docs] “Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “Import formats: Insomnia JSON (v4), Insomnia YAML (v5), Postman v2.0/v2.1, HAR, OpenAPI 3.0/3.1, Swagger, WSDL, and cURL”
- [claimed-docs] “Import a Postman collection or OpenAPI spec into Insomnia Method: UI → Import → choose File/Clipboard/URL.”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
Testing mocking — stories about testing mocking in this arenaTesting mocking
Stories about testing mocking in this arena
Ai assist
ai-native userHave AI generate test cases or assertions for an endpoint from its spec or responses
weight 2 · round to PostmanPostman'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.”
Insomnianone0/10Insomnia's AI features documented are limited to mock server generation from prompts/specs and AI commit message suggestions; there is no evidence of AI generating test cases or assertions from an endpoint's spec or responses. Testing capabilities (collection runner, pre-request scripts, chaining) are manual, not AI-driven.
- [claimed-docs] “Creates a mock server from a prompt, OpenAPI definition, or live URL response. Automatically scaffolds routes, responses, and configurations…”
- [claimed-docs] “Auto-generate a mock server from a natural language prompt and one of the following input types: URL, OpenAPI, or JSON.”
- [claimed-docs] “AI-assisted mock server generation, which transforms prompts or API definitions into mock APIs.”
- [claimed-docs] “AI commit message suggestions, which help”
- [claimed-docs] “Automatically test multiple requests in your collections, with unlimited collection runs.”
- [claimed-docs] “Use the Collection Runner to send multiple requests in a specific order”
Contract testing
platform-engineerValidate live responses against the API contract to catch drift
weight 2 · round to PostmanPostman 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.”
Insomnianone0/10Insomnia's docs describe general request/response testing, chaining, and OpenAPI spec linting (via 'inso lint spec') for validating the spec file itself, but there is no evidence of a feature that validates live API responses at runtime against an OpenAPI/schema contract to detect drift.
Mocking
developerSpin up a mock server from saved examples or a spec so consumers can build before the API exists
weight 3 · round to PostmanPostman's docs explicitly document creating mock servers from collections/examples or specs to simulate a real API server that's always available, including dynamic mock responses and deployment guidance. missing for 10: independent hands-on corroboration of mock server reliability/consumer workflows beyond first-party docs.
- [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.”
Insomnia Cloud mock servers can be created directly from OpenAPI definitions, prompts, or live URL responses, auto-scaffolding routes/responses so consumers can build against the API before it's complete, and dynamic mocking supports realistic templated/fake data responses. missing for 10: independent/hands-on verification of mock server reliability and no evidence of generating mocks directly from saved request 'examples' (only prompt/spec/URL inputs documented).
- [claimed-docs] “The Insomnia Cloud mock servers allow you to create a mock endpoint in a few steps.”
- [claimed-docs] “Creates a mock server from a prompt, OpenAPI definition, or live URL response. Automatically scaffolds routes, responses, and configurations…”
- [claimed-docs] “Auto-generate a mock server from a natural language prompt and one of the following input types: URL, OpenAPI, or JSON.”
- [claimed-docs] “Dynamic mocking renders Liquid templates so responses can include: - Data from the request (headers, query parameters, path, or body). - Ran…”
- [claimed-docs] “Dynamic mocking renders Liquid templates so responses can include: Data from the request (headers, query parameters, path, or body).”
- [claimed-docs] “AI-assisted mock server generation, which transforms prompts or API definitions into mock APIs.”
Testing
developerRun an entire collection as an automated test suite with a pass/fail report
weight 3 · round to PostmanPostman 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.”
Insomnia supports collection runs (Collection Runner, unlimited collection runs), chaining requests, pre/post-request scripts, and the Inso CLI which 'disables prompts and provides exit codes to pass or fail the CI workflow,' enabling automated test suites with pass/fail reporting in CI. Docs also show lint commands failing builds on errors, reinforcing pass/fail semantics. missing for 10: no independent/hands-on report confirming the CLI pass/fail report format or reliability in practice, and no detail on report output formatting (e.g., JUnit/HTML report generation).
- [claimed-docs] “Use the Insomnia CLI to automate the execution of your API tests using your existing Git workflows.”
- [claimed-docs] “Automatically test multiple requests in your collections, with unlimited collection runs.”
- [claimed-docs] “Use the Collection Runner to send multiple requests in a specific order”
- [claimed-docs] “Test complex workflows by chaining the responses from requests together”
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “Inso CLI is designed to run in a Continuous Integration (CI) environment. It disables prompts and provides exit codes to pass or fail the CI…”
- [claimed-docs] “In CI, use inso lint spec <identifier> to lint OpenAPI and fail builds on errors.”
developerWrite test assertions against response status, body, and headers
weight 3 · round to PostmanPostman'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.”
Insomnia's docs describe a dedicated testing feature set—chaining requests, pre-/after-response scripting to add logic, automatic cookie handling, and CLI-driven automated test runs across collections—strongly implying support for assertions on response status/body/headers, but no evidence pack item shows explicit assertion syntax or examples asserting on status codes, body content, or headers specifically. Missing for 10: explicit assertion API/examples (e.g., expect(response.status).to.equal), documented header/body matcher functions, and independent hands-on confirmation of assertion authoring.
- [claimed-docs] “Pre-request and after-response scripting to add logic to your requests”
- [claimed-docs] “Test complex workflows by chaining the responses from requests together”
- [claimed-docs] “Automate your tests with Inso CLI”
- [claimed-docs] “Insomnia automatically stores cookies from every response and sends them with future requests”
- [claimed-docs] “Automatically test multiple requests in your collections, with unlimited collection runs.”
- [claimed-docs] “Pre-request scripts allow you to execute tasks before a request is sent. They can be used to: * Manipulate environment variables or authenti…”
Not comparable on these axes
ai-native userSubscribe to events via webhooks
weight 2 · not comparablePostman 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.”
Insomnian/aInsomnia is an API client/design tool for making requests, testing, and mocking; there is no evidence of a webhook subscription/event-notification feature, and 'subscribing to events via webhooks' is not a natural axis for this product category (it's a client, not a service that emits events).
platform-engineerMonitor API traffic with metrics, logging, and tracing integrations
weight 2 · not comparablePostmannone0/10Postman'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.”
platform-engineerEnforce authentication (API keys, OAuth2, JWT, mTLS) on upstream APIs via gateway plugins or policies
weight 3 · not comparablePostmann/aPostman is an API client, testing, collaboration, and design platform, not an API gateway product; the evidence pack shows no gateway plugin/policy engine for enforcing upstream authentication schemes (API keys, OAuth2, JWT, mTLS). The one 'gateway' reference (postman-docs-7) is about registering MCP servers with Postman's Fabric Gateway for AI agent access, not upstream API auth enforcement — a different axis entirely.
- [claimed-docs] “This guide walks you through registering a Model Context Protocol (MCP) server with the gateway and making it available to your team.”
Insomnian/aInsomnia is an API client/testing tool for designing, sending, and debugging requests, not an API gateway that enforces authentication/authorization policies on upstream traffic; that role belongs to products like Kong Gateway. The evidence only shows Insomnia's own auth support for making requests (SAML IdP support, vault integration) and RBAC on its collaboration platform, not gateway-plugin-based enforcement on upstream APIs.
platform-engineerEnforce rate limits on API traffic per consumer or route
weight 3 · not comparablePostmann/aPostman is an API client/testing/collaboration platform, not an API gateway; enforcing consumer/route-based rate limits on live traffic is a gateway/proxy capability outside Postman's product category, and no evidence shows Postman shipping such traffic-control enforcement (mocking/simulating disruptions is not the same as enforcing rate limits).
platform-engineerRoute, load-balance, and transform requests between consumers and upstream services
weight 2 · not comparablePostmann/aPostman is an API client/testing/collaboration platform for designing, testing, mocking, and documenting APIs; it is not an API gateway or traffic-management product. There is no evidence of routing, load-balancing, or request/response transformation between consumers and upstream services — mock servers and Postman Flows are for simulation/prototyping, not production traffic routing. This capability is a category error for this type of product.
Insomnian/aInsomnia is an API client/design/testing tool used by developers to build, test, and mock API requests locally; it does not sit in the request path routing, load-balancing, or transforming live traffic between consumers and upstream production services. That gateway/proxy functionality is a different product category (e.g., Kong Gateway), so this axis is a category error for Insomnia.