Zapier: the 360 agent-readiness check

Zapier scores 84 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 perfect Discovery layer and a specification with no error model or versioning.

On 9 November 2026 the public site at zapier.com scored 84 of 100 on Ora's agent-readiness scan, a B, in Ora's Productivity 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: Zapier offers broad discovery and a published OpenAPI spec, but lacks WebMCP support and machine-readable scope declarations.

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, Zapier 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 Zapier, 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.

• WebMCP support: partial, 0 of 5, about 1.8 points to gain. Ora saw: No WebMCP support detected on the homepage. WebMCP is mentioned in the documentation at /developers, but a mention is not an implementation, so it earns no points.
• REST typed error model: fail, 0 of 3, about 1.1 points to gain. Ora saw: No typed error model found
• REST versioning / deprecation policy: fail, 0 of 3, about 1.1 points to gain. Ora saw: No API versioning strategy found - add URL path versioning (/v1/, /v2/) or a versioned header parameter in your OpenAPI spec
• GraphQL typed error model: fail, 0 of 3, about 1.1 points to gain. Ora saw: GraphQL introspection auth-gated and no typed graphql error model documentation found on GraphQL-tagged pages
• Idempotency-Key support: fail, 0 of 3, about 1.1 points to gain. Ora saw: No REST Idempotency-Key support detected (GraphQL signal: fail 0).

Our read

Zapier has a perfect Discovery layer, 19 of 19, and an act layer that is complete in kind. The MCP server at mcp.zapier.com/api/v1/connect answers and requires authentication, the server card is at /.well-known/mcp/, OAuth authorization server metadata is on the MCP host, an OpenAPI specification in YAML is published for the Actions API, an agent skills index lists four skills, zapier.com serves an llms.txt and markdown twins at /mcp.md and /auth.md, and the home page reads as prose at a 6.4 percent text ratio with one H1, nine H2s and eleven H3s. What keeps it a B is the specification's content rather than its presence: it has neither a typed error model nor a versioning strategy, REST answers without an Idempotency-Key, and the GraphQL endpoint keeps introspection gated. WebMCP is mentioned in the developer documentation and not registered on the page. The company that connects everything else has connected itself; the specification needs a second pass.

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.