Install
npm install -g postman-cliShowcase


Products
Postman, product by product →Postman 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 |
|---|---|---|---|---|
| API Client & Collectionsthis page | API platforms | #1/5 | 40/100 | 53/100 |
| Fernacquired | Developer Docs Platforms | #1/5 | 43/100 | 56/100 |
Not yet judged (12 — no arena where they compete): Flows · Mock Servers · Monitors · Postman CLI & newman · API Network & MCP Catalog · Agent Mode · Insights · API Catalog & Governance · SDK Generator · AI Engineer · Fabric Gateway · Passport
Try itExperimental
See what an agent can do with Postman before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; the live MCP handshake runs real requests from our edge, right now — including, where the server allows it, one real read-only tool call (bring your own key for auth-gated servers); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$mcp-probe → https://mcp.postman.com/mcplive — run just now from our edge$ press ▶ run to send one JSON-RPC initialize from our edge
Verified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
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
What’s free: 0 free · 1 paid · 0 enterprise · 32 not stated in evidence
Follow the green: where the map greys out is where Postman 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
✓9/10
unlocks → Official SDKs · Scoped API keys · Versioning policy · Full data export
Subscribe to events via webhooks
~6/10
Build against official SDKs
—0/10
Issue scoped/least-privilege API credentials for an agent
—–
Connect an agent via an official MCP server
✓8/10
Download a machine-readable API spec (OpenAPI or equivalent)
✓8/10
unlocks → Official SDKs
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
~6/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓9/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
✓8/10
unlocks → MCP client
Operate the product with natural-language commands
✓8/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
✓7/10
Set up automations that run autonomously in the background
~4/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
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 | full | 9/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 | full | 8/10 | Tprobed | |
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 | full | 8/10 | Cclaimed | |
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 | none± | 0/10 | ||
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 | full | 9/10 | Tprobed | |
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 | 9/10 | Tprobed | |
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 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Cclaimed | |
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 | |
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 | full | 7/10 | Cclaimed | |
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 | 6/10 | Cclaimed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial± | 6/10 | Cclaimed | |
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 | 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 | ||
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 | ||
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 | 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 | |
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 | 9/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 | 9/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 | full | 8/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 | 8/10 | Xcommunity | |
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 | |
Write test assertions against response status, body, and headers C Testing | developer | Testing mocking — stories about testing mocking in this arenaTesting mocking | 3 | full | 8/10 | Cclaimed | |
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 | partialpaid | 6/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 | 6/10 | Xcommunity | |
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 | 4/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 | disputed | 4/10 | Dcontradicted | |
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 | partial | 4/10 | Cclaimed | |
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 | 0/10 | ||
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 | ||
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ||
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 | none | 0/10 | ||
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 | |
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 | full | 9/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 | full | 8/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 | full | 7/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 | full | 7/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 | 6/10 | Tprobed | |
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 | partial | 6/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 | partial | 6/10 | Cclaimed | |
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 | partial | 6/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 | partial | 5/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 | 5/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 | disputed | 4/10 | Dcontradicted | |
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 | 4/10 | Dcontradicted | |
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 | partial | 3/10 | Xcommunity | |
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 | partial | 3/10 | Cclaimed | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 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 | none | 0/10 | ||
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | 0/10 | ||
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | 0/10 | ||
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
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 | 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 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 | 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 | partial | 4/10 | Xcommunity |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 31 stories with headroom
What would move Postman’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 productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
Missing: 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.
Collections workspaces — stories about collections workspaces in this arenaStore collections as plain text files in my repo and version them with git
nonemoves PA Scoreimpact 30
Postman's docs describe collections living in cloud workspaces with sharing/versioning via Postman's own platform, but there is no documentation of a native git-friendly, plain-text file storage workflow for collections.
Openness — open source, data portability, and self-hosting storiesSelf-host the core product
nonemoves PA Scoreimpact 30
Postman is a cloud-based SaaS product with a desktop client that syncs to Postman's servers; there is no evidence of a self-hostable core product (e.g., on-prem/enterprise server package).
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
Missing: 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.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
Evidence shows Postman has team/workspace role permissions and a Vault for secrets, but nothing documents issuing scoped or least-privilege API credentials specifically for an AI agent's use (e.g., agent-specific API keys, granular scopes, or token restrictions tied to Agent Mode or MCP usage).
Agenticness — how well agents can access and operate the productBuild against official SDKs
nonemoves agent-readyimpact 30
Evidence shows Postman's own API (postman-docs-5, postman-docs-41) and a CLI (postman-probe-5) for programmatic access, and a feature to generate SDKs *from* user collections (postman-docs-4), but there is no evidence of officially maintained Postman SDKs (e.g., Node/Python/Go client libraries) that an AI-native developer could build against to integrate with Postman itself.
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 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.
Gateway traffic — stories about gateway traffic in this arenaMonitor API traffic with metrics, logging, and tracing integrations
nonemoves PA Scoreimpact 20
Missing: any documented observability/tracing integration, gateway traffic metrics dashboard, or logging pipeline connecting Postman to APM/observability tools.
Showing the top 8 of 31 — 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 map10 surfaces · 39 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs34 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Use an official CLI
- Drive the product through a documented public API
- Subscribe to events via webhooks
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- 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
- 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
- Publish an internal catalog or portal where teams discover and consume our APIs
- Share collections with my team in a synced shared workspace
- Import and export collections in portable formats to move between tools
- Organize API requests into collections and folders and rerun them anytime
- 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
- 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
- Have AI generate test cases or assertions for an endpoint from its spec or responses
- Validate live responses against the API contract to catch drift
- 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
Latest v 12 docs14 stories
- 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)
- Publish an internal catalog or portal where teams discover and consume our APIs
- Import and export collections in portable formats to move between tools
- Work fully offline in a local workspace without a cloud account
- Send GraphQL, gRPC, WebSocket, and SSE requests, not just REST
- Design an API spec-first and export it as OpenAPI
- Import an OpenAPI spec to generate requests and collections
- Have AI generate test cases or assertions for an endpoint from its spec or responses
- Validate live responses against the API contract to catch drift
- Write test assertions against response status, body, and headers
Release notes docs14 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Subscribe to events via webhooks
- Set up automations that run autonomously in the background
- Perform bulk operations across many items at once
- Run my API test collections in CI with a CLI and fail the build on regressions
- Script pre-request and post-response logic to chain requests and massage data
- Organize API requests into collections and folders and rerun them anytime
- 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
- Write test assertions against response status, body, and headers
Hacker News8 stories
- Version, review, and roll back my automations
- Share collections with my team in a synced shared workspace
- 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
- 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
- Export all of my data in open formats and leave
Help docs4 stories
Templates docs4 stories
OpenAPI spec3 stories
Fabric gateway docs2 stories
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
5 of 15 testable claims verified · 2 contradicted → integrity 7/100
19 distinct capability claims found in Postman’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
5
Verified
8
Unverified
2
Contradicted
23
Undersold
Verified (9)
“Postman CLI can feed coding agents context for API discovery, code generation, and maintenance tasks”
“Postman API lets you programmatically manage Postman assets and integrate into your dev toolchain”
Drive the product through a documented public APIfullproof ↗
“Combine the Postman API and CLI to integrate Postman into CI/CD pipelines”
Run my API test collections in CI with a CLI and fail the build on regressionsfullproof ↗
“Register an MCP server with a gateway to make it available to your team”
“MCP Generator lets you create your own MCP server from public APIs in the Postman API Network”
“Start a live session within an HTTP request to collaborate with your team in real time”
Share collections with my team in a synced shared workspacepartialproof ↗
“Create internal workspaces where teams can share, version, and discuss API projects”
Share collections with my team in a synced shared workspacepartialproof ↗
“Use the Postman CLI to run test collections as part of a CI/CD pipeline”
Run my API test collections in CI with a CLI and fail the build on regressionsfullproof ↗
“Workspaces enable collaboration with teammates or the wider Postman community”
Share collections with my team in a synced shared workspacepartialproof ↗
Unverified (9)
“Run and manage collections with configurable options and built-in test reporters”
Run an entire collection as an automated test suite with a pass/fail reportfullproof ↗
“Spin up mock servers that simulate a live, always-available API for testing and development”
Spin up a mock server from saved examples or a spec so consumers can build before the API existsfullproof ↗
“Agent Mode lets you send requests, fix errors, and update tests using natural language”
Operate the product with natural-language commandsfullproof ↗
“Agent Mode lets you send requests, fix errors, and update tests using natural language”
Delegate tasks to a built-in AI assistant inside the productfullproof ↗
“Run scripts before a request is sent (pre-request) or after (post-response)”
Script pre-request and post-response logic to chain requests and massage datafullproof ↗
“Define roles and permissions for team members at team, workspace, and element levels”
Control who can view or edit APIs and collections with roles and permissionsfullproof ↗
“Design an API's structure using Spec Hub or types in collections via the Postman Collection format”
Design an API spec-first and export it as OpenAPIpartialproof ↗
“Write scripts to add dynamic behavior, run tests, and pass data between requests”
Script pre-request and post-response logic to chain requests and massage datafullproof ↗
“Write scripts to add dynamic behavior, run tests, and pass data between requests”
Write test assertions against response status, body, and headersfullproof ↗
Contradicted (2)
“Generate and manage client SDKs from collections and API specifications”
“Send API requests, group them into collections, and secure data with Postman Vault”
Keep credentials out of shared files with masked secrets or an external vault integrationdisputedproof ↗
Undersold (23)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationfullproof ↗
Get AI-generated insights and suggestions from my data inside the productfullproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
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 oncefullproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Publish an internal catalog or portal where teams discover and consume our APIspartialproof ↗
Import and export collections in portable formats to move between toolspartialproof ↗
Organize API requests into collections and folders and rerun them anytimefullproof ↗
Send GraphQL, gRPC, WebSocket, and SSE requests, not just RESTpartialproof ↗
Switch requests between dev, staging, and prod using environment variable setsfullproof ↗
Proxy and govern LLM/MCP traffic (token limits, prompt guards, provider routing) through the platformpartialproof ↗
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 ↗
Lint API specs against configurable style and governance rulesfullproof ↗
Import an OpenAPI spec to generate requests and collectionspartialproof ↗
Have AI generate test cases or assertions for an endpoint from its spec or responsesfullproof ↗
Validate live responses against the API contract to catch driftpartialproof ↗
Claims outside our story set (1)
Real capability claims found in Postman’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.
“Application Inventory integrates with UI test suites to validate API interactions and auto-discover dependencies”
source ↗
Business model
Free plan for individuals and small teams; paid Basic/Professional per-user plans add collaboration and API Builder limits, with custom Enterprise plans for governance and support.
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
Agent surface uptime MCP 100% · llms.txt 100% · openapi.json 100% (30d, checked every 6h since Sep 8 '26)
