Access
Install
npm install -g insomnia-insoProducts
Kong, product by product →Kong ships more than one product — each judged line competes in its own arena on the same stories as everyone else.
| Line | Arena | Rank | PA Score | Agent-ready |
|---|---|---|---|---|
| Kong Gateway & Konnect | API platforms | #2/5 | 36/100 | 48/100 |
| AI Gateway | Model Gateways & Routers | #6/7 | 19/100 | 47/100 |
| Insomniathis pageacquired | API platforms | #4/5 | 34/100 | 37/100 |
Not yet judged (9 — no arena where they compete): Kong Mesh · Event Gateway · Ingress Controller & Operator · Dev Portal · Service Catalog & MCP Registry · Kong Identity · decK & kongctl · Metering & Billing · Volcano SDK
Try itExperimental
See what an agent can do with Insomnia before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -s https://developer.konghq.com/insomnia.md | head -8recorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Ci scripting — stories about ci scripting in this arenaCi scriptingevidence →
Stories about ci scripting in this arena
Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaborationevidence →
Working as a team — sharing, comments, roles, simultaneous editing
Collections workspaces — stories about collections workspaces in this arenaCollections workspacesevidence →
Stories about collections workspaces in this arena
Environments secrets — stories about environments secrets in this arenaEnvironments secretsevidence →
Stories about environments secrets in this arena
Gateway traffic — stories about gateway traffic in this arenaGateway trafficevidence →
Stories about gateway traffic in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Spec design — stories about spec design in this arenaSpec designevidence →
Stories about spec design in this arena
Testing mocking — stories about testing mocking in this arenaTesting mockingevidence →
Stories about testing mocking in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Insomnia stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
~4/10
unlocks → Official SDKs · Scoped API keys · MCP server · Versioning policy
Subscribe to events via webhooks
n/an/a
Build against official SDKs
—0/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
—0/10
Download a machine-readable API spec (OpenAPI or equivalent)
✓8/10
unlocks → Official SDKs · MCP server
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
~6/10
Explore an interactive API reference with runnable examples
~5/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
~6/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
~4/10
Operate the product with natural-language commands
~4/10
unlocks → Autonomous automations
Plug MCP servers into this product so it can use their tools
✓8/10
Get AI-generated insights and suggestions from my data inside the product
~4/10
Set up automations that run autonomously in the background
—0/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Ci scripting — stories about ci scripting in this arenaCi scripting
Stories about ci scripting in this arena
Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaboration
Working as a team — sharing, comments, roles, simultaneous editing
Collections workspaces — stories about collections workspaces in this arenaCollections workspaces
Stories about collections workspaces in this arena
Environments secrets — stories about environments secrets in this arenaEnvironments secrets
Stories about environments secrets in this arena
Gateway traffic — stories about gateway traffic in this arenaGateway traffic
Stories about gateway traffic in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Spec design — stories about spec design in this arenaSpec design
Stories about spec design in this arena
Testing mocking — stories about testing mocking in this arenaTesting mocking
Stories about testing mocking in this arena
Sorted by importance (agentic first) (high → low) · 57/57 stories · click a row’s chevron for the rationale and evidence
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Cclaimed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 4/10 | Cclaimed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 4/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Cclaimed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 6/10 | Cclaimed | |
Organize API requests into collections and folders and rerun them anytime C Collections | developer | Collections workspaces — stories about collections workspaces in this arenaCollections workspaces | 3 | full | 9/10 | Xcommunity | |
Switch requests between dev, staging, and prod using environment variable sets C Environments | developer | Environments secrets — stories about environments secrets in this arenaEnvironments secrets | 3 | full | 9/10 | Cclaimed | |
Import an OpenAPI spec to generate requests and collections C Spec import export | developer | Spec design — stories about spec design in this arenaSpec design | 3 | full | 8/10 | Cclaimed | |
Run an entire collection as an automated test suite with a pass/fail report C Testing | developer | Testing mocking — stories about testing mocking in this arenaTesting mocking | 3 | full | 8/10 | Cclaimed | |
Run my API test collections in CI with a CLI and fail the build on regressions C Ci | developer | Ci scripting — stories about ci scripting in this arenaCi scripting | 3 | full | 8/10 | Tprobed | |
Share collections with my team in a synced shared workspace C Team workspaces | developer | Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaboration | 3 | full | 8/10 | Cclaimed | |
Spin up a mock server from saved examples or a spec so consumers can build before the API exists C Mocking | developer | Testing mocking — stories about testing mocking in this arenaTesting mocking | 3 | full | 8/10 | Cclaimed | |
Store collections as plain text files in my repo and version them with git C Collections | developer | Collections workspaces — stories about collections workspaces in this arenaCollections workspaces | 3 | full | 8/10 | Cclaimed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partial | 7/10 | Cclaimed | |
Write test assertions against response status, body, and headers C Testing | developer | Testing mocking — stories about testing mocking in this arenaTesting mocking | 3 | partial | 6/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 5/10 | Cclaimed | |
Lint API specs against configurable style and governance rules C Governance | platform-engineer | Spec design — stories about spec design in this arenaSpec design | 3 | partial | 5/10 | Cclaimed | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partial | 5/10 | Cclaimed | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | 0/10 | ||
Enforce authentication (API keys, OAuth2, JWT, mTLS) on upstream APIs via gateway plugins or policies C Traffic management | platform-engineer | Gateway traffic — stories about gateway traffic in this arenaGateway traffic | 3 | n/a | untested | none yet | |
Enforce rate limits on API traffic per consumer or route C Traffic management | platform-engineer | Gateway traffic — stories about gateway traffic in this arenaGateway traffic | 3 | n/a | untested | none yet | |
Import and export collections in portable formats to move between tools C Collections | developer | Collections workspaces — stories about collections workspaces in this arenaCollections workspaces | 2 | full | 9/10 | Cclaimed | |
Design an API spec-first and export it as OpenAPI C Spec import export | developer | Spec design — stories about spec design in this arenaSpec design | 2 | full | 8/10 | Tprobed | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | full | 8/10 | Cclaimed | |
Send GraphQL, gRPC, WebSocket, and SSE requests, not just REST C Protocols | developer | Collections workspaces — stories about collections workspaces in this arenaCollections workspaces | 2 | full | 8/10 | Cclaimed | |
Keep credentials out of shared files with masked secrets or an external vault integration C Secrets | platform-engineer | Environments secrets — stories about environments secrets in this arenaEnvironments secrets | 2 | full | 7/10 | Cclaimed | |
Control who can view or edit APIs and collections with roles and permissions G Access control | platform-engineer | Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaboration | 2 | partial | 6/10 | Cclaimed | |
Manage API infrastructure as declarative config and sync it from CI (GitOps/APIOps) C Gateway ops | platform-engineer | Gateway traffic — stories about gateway traffic in this arenaGateway traffic | 2 | partial | 6/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 6/10 | Cclaimed | |
Script pre-request and post-response logic to chain requests and massage data C Scripting | developer | Ci scripting — stories about ci scripting in this arenaCi scripting | 2 | disputed | 6/10 | Dcontradicted | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 5/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 5/10 | Tprobed | |
Work fully offline in a local workspace without a cloud account G Offline | developer | Collections workspaces — stories about collections workspaces in this arenaCollections workspaces | 2 | disputed | 5/10 | Dcontradicted | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 4/10 | Cclaimed | |
Generate and publish API documentation from my collections or specs C Docs generation | developer | Spec design — stories about spec design in this arenaSpec design | 2 | partial | 4/10 | Cclaimed | |
Schedule collection runs as monitors that alert me when an API breaks C Monitors | developer | Ci scripting — stories about ci scripting in this arenaCi scripting | 2 | partial | 4/10 | Cclaimed | |
Have AI generate test cases or assertions for an endpoint from its spec or responses C Ai assist | ai-native user | Testing mocking — stories about testing mocking in this arenaTesting mocking | 2 | none | 0/10 | ||
Proxy and govern LLM/MCP traffic (token limits, prompt guards, provider routing) through the platform C Ai gateway | ai-native user | Gateway traffic — stories about gateway traffic in this arenaGateway traffic | 2 | none | 0/10 | ||
Publish an internal catalog or portal where teams discover and consume our APIs C Api catalog | platform-engineer | Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaboration | 2 | none | 0/10 | ||
Monitor API traffic with metrics, logging, and tracing integrations C Monitoring | platform-engineer | Gateway traffic — stories about gateway traffic in this arenaGateway traffic | 2 | n/a | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Route, load-balance, and transform requests between consumers and upstream services C Traffic management | platform-engineer | Gateway traffic — stories about gateway traffic in this arenaGateway traffic | 2 | n/a | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
Validate live responses against the API contract to catch drift C Contract testing | platform-engineer | Testing mocking — stories about testing mocking in this arenaTesting mocking | 2 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | full | 7/10 | Cclaimed |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 32 stories with headroom
What would move Insomnia’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productConnect an agent via an official MCP server
nonemoves agent-readyimpact 45
Evidence 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.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
Insomnia'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.
Agenticness — how well agents can access and operate the productSet up automations that run autonomously in the background
nonemoves Built-in AIimpact 30
Insomnia 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.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
Insomnia 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.
Agenticness — how well agents can access and operate the productBuild against official SDKs
nonemoves agent-readyimpact 30
Evidence 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.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
The 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.
Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product
partialq4/10moves Built-in AIimpact 27
Missing: 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.
Agenticness — how well agents can access and operate the productDrive the product through a documented public API
partialq4/10moves agent-readyimpact 27
Missing: a documented HTTP/SDK-style public API for controlling Insomnia, independent confirmation the Inso CLI/plugin surface is used for AI-agent automation.
Showing the top 8 of 32 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map8 surfaces · 40 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Insomnia docs39 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Plug MCP servers into this product so it can use their tools
- Use an official CLI
- Drive the product through a documented public API
- Get AI-generated insights and suggestions from my data inside the product
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Explore an interactive API reference with runnable examples
- Download a machine-readable API spec (OpenAPI or equivalent)
- Test against a sandbox environment without touching production data
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Version, review, and roll back my automations
- Run my API test collections in CI with a CLI and fail the build on regressions
- Schedule collection runs as monitors that alert me when an API breaks
- Script pre-request and post-response logic to chain requests and massage data
- Control who can view or edit APIs and collections with roles and permissions
- Share collections with my team in a synced shared workspace
- Store collections as plain text files in my repo and version them with git
- Import and export collections in portable formats to move between tools
- Organize API requests into collections and folders and rerun them anytime
- Work fully offline in a local workspace without a cloud account
- Send GraphQL, gRPC, WebSocket, and SSE requests, not just REST
- Switch requests between dev, staging, and prod using environment variable sets
- Keep credentials out of shared files with masked secrets or an external vault integration
- Manage API infrastructure as declarative config and sync it from CI (GitOps/APIOps)
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Self-host the core product
- Choose where my data is stored (region/residency)
- Control data retention and deletion
- Generate and publish API documentation from my collections or specs
- Lint API specs against configurable style and governance rules
- Design an API spec-first and export it as OpenAPI
- Import an OpenAPI spec to generate requests and collections
- Spin up a mock server from saved examples or a spec so consumers can build before the API exists
- Run an entire collection as an automated test suite with a pass/fail report
- Write test assertions against response status, body, and headers
Inso CLI docs14 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Run my API test collections in CI with a CLI and fail the build on regressions
- Schedule collection runs as monitors that alert me when an API breaks
- Script pre-request and post-response logic to chain requests and massage data
- Import and export collections in portable formats to move between tools
- Manage API infrastructure as declarative config and sync it from CI (GitOps/APIOps)
- Do everything through the API that I can do in the UI
- Lint API specs against configurable style and governance rules
- Design an API spec-first and export it as OpenAPI
- Run an entire collection as an automated test suite with a pass/fail report
GitHub README8 stories
- Version, review, and roll back my automations
- Store collections as plain text files in my repo and version them with git
- Work fully offline in a local workspace without a cloud account
- Send GraphQL, gRPC, WebSocket, and SSE requests, not just REST
- Manage API infrastructure as declarative config and sync it from CI (GitOps/APIOps)
- Export all of my data in open formats and leave
- Read the product's source under an open license
- Self-host the core product
Pricing docs6 stories
- Drive the product through a documented public API
- Perform bulk operations across many items at once
- Schedule collection runs as monitors that alert me when an API breaks
- Control who can view or edit APIs and collections with roles and permissions
- Organize API requests into collections and folders and rerun them anytime
- Switch requests between dev, staging, and prod using environment variable sets
Hacker News4 stories
insomnia.rest2 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -s https://developer.konghq.com/insomnia.md | head -8reproduced$ curl -s https://developer.konghq.com/insomnia.md | head -8 --- title: Insomnia description: Introduction to Insomnia, the open source desktop application that simplifies designing, debugging, and testing APIs. url: "/insomnia/" canonical_url: "/insomnia/" content_type: landing_page products:
$curl -s https://developer.konghq.com/llms.txt | grep -A 4 '## Insomnia'reproduced$ curl -s https://developer.konghq.com/llms.txt | grep -A 4 '## Insomnia' ## Insomnia - [Inso CLI](https://developer.konghq.com/inso-cli.md): This page is an introduction to Inso CLI, a command line tool for Insomnia. - [Inso CLI configuration](https://developer.konghq.com/inso-cli/configuration.md): Inso CLI can be configured with a configuration file, allowing you to specify options and scripts. - [Continuous Integration with Inso CLI](https://developer.konghq.com/inso-cli/continuous-integration.md): Inso CLI is designed to run in a Continuous Integration (CI) environment.
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
3 of 20 testable claims verified · 2 contradicted → integrity 0/100
31 distinct capability claims found in Insomnia’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
3
Verified
15
Unverified
2
Contradicted
20
Undersold
Verified (3)
“Official CLI can automate running API tests as part of existing Git-based CI workflows”
“Official CLI can automate running API tests as part of existing Git-based CI workflows”
Run my API test collections in CI with a CLI and fail the build on regressionsfullproof ↗
“Build and iterate on OpenAPI specs directly in the app to design APIs”
Design an API spec-first and export it as OpenAPIfullproof ↗
Unverified (21)
“Collection Runner can automatically run multiple requests/tests in a collection with unlimited runs”
Run an entire collection as an automated test suite with a pass/fail reportfullproof ↗
“Cloud mock servers let you create a mock endpoint in a few steps”
Spin up a mock server from saved examples or a spec so consumers can build before the API existsfullproof ↗
“Supports making gRPC requests”
Send GraphQL, gRPC, WebSocket, and SSE requests, not just RESTfullproof ↗
“Import and export collections in formats like Postman, HAR, OpenAPI, Swagger, WSDL, and cURL”
Import and export collections in portable formats to move between toolsfullproof ↗
“Import and export collections in formats like Postman, HAR, OpenAPI, Swagger, WSDL, and cURL”
Import an OpenAPI spec to generate requests and collectionsfullproof ↗
“Environments group variables (base URLs, tokens, credentials) applied across requests”
Switch requests between dev, staging, and prod using environment variable setsfullproof ↗
“Can auto-generate a mock server from a natural-language prompt, OpenAPI definition, or live URL response, scaffolding routes and responses”
Spin up a mock server from saved examples or a spec so consumers can build before the API existsfullproof ↗
“Git Sync stores project data via any third-party Git repository without going through the cloud”
Store collections as plain text files in my repo and version them with gitfullproof ↗
“Role-based access control gives fine-grained control over who can access which resources”
Control who can view or edit APIs and collections with roles and permissionspartialproof ↗
“Organizations let users securely share collections and environments with colleagues”
Share collections with my team in a synced shared workspacefullproof ↗
“MCP clients can connect Insomnia to Konnect for real-time mocking, validating, and protecting requests”
Plug MCP servers into this product so it can use their toolsfullproof ↗
“Can send requests via HTTP, gRPC, GraphQL, and WebSockets”
Send GraphQL, gRPC, WebSocket, and SSE requests, not just RESTfullproof ↗
“Spec editor automatically lints and displays errors with type, line number, and message”
Lint API specs against configurable style and governance rulespartialproof ↗
“Git Sync connects directly to your Git repository so project data stays in your own repo”
Choose where my data is stored (region/residency)partialproof ↗
“Provides an in-app merge view to review and resolve Git sync conflicts without leaving Insomnia”
Store collections as plain text files in my repo and version them with gitfullproof ↗
“Integrates with external vault service providers to automatically retrieve secret values when sending requests”
Keep credentials out of shared files with masked secrets or an external vault integrationfullproof ↗
“Allows uploading Protobuf files (single file or directory) for gRPC requests”
Send GraphQL, gRPC, WebSocket, and SSE requests, not just RESTfullproof ↗
“Dynamic mocking uses Liquid templates so mock responses can include request data or randomly generated fake data”
Spin up a mock server from saved examples or a spec so consumers can build before the API existsfullproof ↗
“MCP Client discovers server elements, enabling you to invoke, query, or test them directly in the app”
Plug MCP servers into this product so it can use their toolsfullproof ↗
“AI can suggest commit messages to help keep Git history clear and atomic”
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
“Source code is released under the Apache-2.0 open source license”
Contradicted (4)
“Chain requests together, extracting values from responses and sharing state across requests”
Script pre-request and post-response logic to chain requests and massage datadisputedproof ↗
“Pre-request scripts can manipulate environment variables, auth, or request contents before sending”
Script pre-request and post-response logic to chain requests and massage datadisputedproof ↗
“Scratch Pad workspace requires no login at all”
Work fully offline in a local workspace without a cloud accountdisputedproof ↗
“Projects can be converted between storage backends: Local Vault, Cloud Sync, or Git Sync”
Work fully offline in a local workspace without a cloud accountdisputedproof ↗
Undersold (20)
Point an agent at llms.txt or agent-oriented docspartialproof ↗
Run the product headlessly / in CI for automationfullproof ↗
Drive the product through a documented public APIpartialproof ↗
Delegate tasks to a built-in AI assistant inside the productpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Explore an interactive API reference with runnable examplespartialproof ↗
Download a machine-readable API spec (OpenAPI or equivalent)fullproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Schedule collection runs as monitors that alert me when an API breakspartialproof ↗
Organize API requests into collections and folders and rerun them anytimefullproof ↗
Manage API infrastructure as declarative config and sync it from CI (GitOps/APIOps)partialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Export all of my data in open formats and leavepartialproof ↗
Generate and publish API documentation from my collections or specspartialproof ↗
Write test assertions against response status, body, and headerspartialproof ↗
Claims outside our story set (5)
Real capability claims found in Insomnia’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Automatically stores and resends cookies from responses like a web browser”
source ↗“Can generate code snippets automatically in over 12 programming languages”
source ↗“Uses a GraphQL type system to provide auto-completion and linting of GraphQL queries”
source ↗“Insomnia's own servers cannot read or access sensitive project data during the sync process”
source ↗“Unlimited access to plugins, or ability to build your own”
source ↗
Business model
The desktop app is open source (Apache-2.0); free Essentials covers up to 3 users with Git Sync, and paid Pro and Enterprise per-user plans add cloud sync, larger orgs, SSO/SCIM, and Konnect integration.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
