Vercel: the 360 agent-readiness check

Vercel scores 91 of 100 on Ora's agent-readiness scan, an A, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 4: an OpenAPI specification, a public API, OAuth, a command line. A 91 whose remaining points are scope names and rate-limit headers.

On 9 November 2026 the public site at vercel.com scored 91 of 100 on Ora's agent-readiness scan, an A, in Ora's Infrastructure 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: Vercel offers strong discovery and access with a verified zero-auth API, and WebMCP support plus named OAuth scopes would round out agent readiness.

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, Vercel 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. None of the 6 payment checks applied to vercel.com.

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 Vercel, 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: fail, 0 of 5, about 2.5 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 43 of 43 same-origin script bundle(s) for modelContext registrations)
• Idempotency-Key support: fail, 0 of 3, about 1.5 points to gain. Ora saw: No REST Idempotency-Key support detected
• Scoped permissions: partial, 2 of 5, about 1.5 points to gain. Ora saw: OpenAPI declares security schemes but no named OAuth scopes - agents get all-or-nothing access. Declare per-scope grants (e.g. read:*, write:*) in the spec.
• Rate limit response headers: fail, 0 of 2, about 1 points to gain. Ora saw: No REST rate-limit headers found on probed endpoints
• Content without JavaScript: partial, 2 of 3, about 0.5 points to gain. Ora saw: Homepage: 1009 chars with H1, but 1.0% content ratio is below the 5% target. 4 of 4 sampled inner pages have text without JavaScript (1 skipped).

Our read

Vercel scores 91 and a perfect Discovery layer, 21 of 21, and the act layer is nearly as complete: an MCP server at mcp.vercel.com that requires authentication, an OpenAPI 3.0.3 specification at vercel.com/openapi.json, OAuth authorization server metadata on the main domain, the vercel CLI on npm, an agent skills index with nine skills, an llms.txt and an agents.md served as text/markdown. What Ora marks down is finer than any of that: the specification declares security schemes but names no OAuth scopes, so an agent gets all-or-nothing access; the REST endpoints answer without rate-limit headers or an Idempotency-Key; and none of the 43 script bundles registers a WebMCP tool. The home page is 1,009 characters at a 1 percent text ratio, which is the one reading-side mark against it. This is the second-highest score in the directory's first sixty, and the fixes left are specification details.

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.