Stripe: the 360 agent-readiness check

Stripe scores 74 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. A working MCP server and CLI, with the OpenAPI file in the wrong place.

On 9 November 2026 the public site at stripe.com scored 74 of 100 on Ora's agent-readiness scan, a B, in Ora's Payments & Fintech 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: Stripe offers strong developer discovery and SDK packages, but lacks a published OpenAPI specification for agents to parse.

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.

In the directory, Stripe 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 Stripe, 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 4 points to gain. Ora saw: No OpenAPI/Swagger specification found
• WebMCP support: partial, 0 of 5, about 2.6 points to gain. Ora saw: No WebMCP support detected on the homepage. WebMCP is mentioned in the documentation at /docs, but a mention is not an implementation, so it earns no points.
• Brand name discoverability: partial, 1 of 3, about 2.5 points to gain. Ora saw: stripe.com ranks #7 for "Stripe" (searched your brand name alone: no main product term from your homepage qualified)
• REST typed error model: fail, 0 of 3, about 1.6 points to gain. Ora saw: No typed error model found
• Scoped permissions: partial, 2 of 5, about 1.6 points to gain. Ora saw: Scoped permissions described at https://docs.stripe.com, but no machine-readable scope declaration found (OpenAPI oauth2 scopes or RFC 9728 scopes_supported)

Our read

Stripe is the act layer most of this directory is measured against, and Ora reads it as a B. The MCP server at mcp.stripe.com answers and asks for authentication, its OAuth metadata sits at access.stripe.com/mcp, the REST documentation scores 7 of 7, a CLI is on npm and SDKs are in four registries. The one gap that costs real points is the absence of an OpenAPI specification at any path Ora probes, worth about 4 points on its own; Stripe publishes one in a GitHub repository, which the scan does not read, so the fix is a copy at a well-known path. The reading side is in order, with an llms.txt, a complete Organization block and all four agent user agents admitted, though the home page is 2.8 percent text and ranks seventh for its own name. A specification file would make this an A.

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.