Postman: the 360 agent-readiness check

Postman scores 80 of 100 on Ora's agent-readiness scan, a B, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 3: a public API, OAuth, a command line. The API specification company, without a specification for its own API.

On 9 November 2026 the public site at postman.com scored 80 of 100 on Ora's agent-readiness scan, a B, in Ora's Developer Tools category. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. This check reads the act layer first, because that is what the directory records, then the door, what an agent can read, and whether the company is found and recommended. Ora's one-line summary: Postman offers strong developer resource discoverability and MCP registry listings, but lacks a published OpenAPI specification for agents to act on.

The score

What an agent can do

The surfaces an agent acts on: an API it can find and call, an MCP server, an agent card, OAuth metadata, a command line. This is the layer the directory records, so it comes first. 2 checks in this group do not apply to this site and are left out.

In the directory, Postman sign-in required, tools not seen, not counted; the connector run of 4 November 2026 is on the entry page. Ora's MCP server check for the same domain reads partial; the two look for different things, the directory for a server that answers a handshake and lists tools, Ora for a server it can find from the site.

At the door

What the site answers when a request arrives with an agent's user agent, and what robots.txt says to agents.

What an agent can read

Whether the text is in the first response, what the site publishes for agents, and how it describes itself to them.

Found and recommended

Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read.

Payments

The agent payment protocols Ora probes for. A site that sells nothing has nothing here, and Ora scores the layer out of zero when none applies.

The fixes worth most points

Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for Postman, with what Ora observed. The wording of each fix is Ora's; the 28 checks it runs on an MCP server are listed with their layer and tier.

• OpenAPI spec published: fail, 0 of 7, about 3.9 points to gain. Ora saw: No OpenAPI/Swagger specification found
• Scoped permissions: fail, 0 of 5, about 3 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
• WebMCP support: fail, 0 of 5, about 3 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 30 of 30 same-origin script bundle(s) for modelContext registrations)
• Agent instruction / when-to-use: fail, 0 of 3, about 1.7 points to gain. Ora saw: No agent instruction file with when-to-use guidance found
• ARD discovery: fail, 0 of 1, about 1.4 points to gain. Ora saw: No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json

Our read

Postman is the company that made the API specification a product, and Ora found no OpenAPI specification for Postman's own API at any path it probes, about 4 points and the largest single deduction on this page. The rest of the act layer is in order: the MCP server at mcp.postman.com/mcp answers and requires authentication, OAuth authorization server metadata is on the same host, the REST documentation scores 7 of 7, postman-cli is on npm and postman.com serves an llms.txt and returns markdown when an agent asks for it with an Accept header. The gaps beyond the specification are the usual newer ones, no declared scopes, no WebMCP registration in 30 script bundles, no agent instruction file and no ARD catalog. The home page gives 3,254 characters at a 1.6 percent text ratio under two Organization blocks. A B at 80 for the API company; the file its users publish for their APIs is the one it has not published for itself.

Test your own surfaces

The scan above is free and needs no account: enter a domain at ora.ai and read the same four layers for your own site. For an MCP server, Ora scans the server URL itself and runs 28 of its 132 public checks on it, which is why it is the check this directory recommends; the reasons, the limits and the alternatives are on their own page. The command below runs the same audit from a terminal and exits with 1 under the score you set, so it can gate a deploy.

npx ax@0.10 audit https://example.com --min-score 70

All 360 checks, one company a day. Corrections to the corrections page.