PayPal: the 360 agent-readiness check

PayPal scores 70 of 100 on Ora's agent-readiness scan, a B, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 2: a public API, OAuth. The one scored pay layer in the set, beside an API with no specification.

On 9 November 2026 the public site at paypal.com scored 70 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.

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, PayPal 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. 5 checks in this group do not apply to this site and are left out.

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 PayPal, 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.6 points to gain. Ora saw: No OpenAPI/Swagger specification found
• Scoped permissions: fail, 0 of 5, about 2.4 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
• WebMCP support: fail, 0 of 5, about 2.4 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 1 of 1 same-origin script bundle(s) for modelContext registrations)
• JSON error responses: fail, 0 of 4, about 2 points to gain. Ora saw: API does not return JSON error responses (or no API detected)
• Agent instruction / when-to-use: fail, 0 of 3, about 1.5 points to gain. Ora saw: No agent instruction file with when-to-use guidance found

Our read

PayPal is the only company in the directory's first sixty whose Payments layer Ora scored, 3 of 3, because the domain publishes a payment protocol an agent can use; the rest of the act layer is in the same shape as the fintech peers around it. The MCP server at mcp.paypal.com/mcp answers and requires authentication, with OAuth authorization server metadata on the same host, SDKs are in npm and rubygems and developer.paypal.com carries an llms.txt. The API is described in documentation without a machine-verifiable surface or an OpenAPI specification, the endpoints Ora tried did not answer errors as JSON, and it found neither a CLI nor declared scopes. The home page is the best-built in this batch, 9,095 characters at a 9.8 percent text ratio with one H1, twelve H2s and eighteen H3s, and a SoftwareApplication block with offers. The gap between the pay layer and the API layer is the story: an agent can pay PayPal and cannot read its specification.

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.