Webflow: the 360 agent-readiness check

Webflow scores 78 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. Twenty-four skills and a server card, and no specification to describe the API.

On 9 November 2026 the public site at webflow.com scored 78 of 100 on Ora's agent-readiness scan, a B, in Ora's Commerce 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: Webflow offers a published SDK and MCP registry presence, but lacks a published OpenAPI specification and declared scoped permissions for agents.

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. One check in this group does not apply to this site and is left out.

In the directory, Webflow 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 webflow.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 Webflow, 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.8 points to gain. Ora saw: No OpenAPI/Swagger specification found
• Scoped permissions: fail, 0 of 5, about 2.7 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
• Brand name discoverability: partial, 1 of 3, about 2.5 points to gain. Ora saw: webflow.com ranks #7 for "Webflow" (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
• REST versioning / deprecation policy: fail, 0 of 3, about 1.6 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

Our read

Webflow passes the rows that need infrastructure and fails the rows that need a file. The MCP server at mcp.webflow.com/mcp answers and requires authentication, its server card sits at /.well-known/mcp/, OAuth metadata is on the MCP host, the REST documentation scores 7 of 7, @webflow/webflow-cli is on npm, SDKs are in npm and PyPI, an agent skills index lists 24 skills, webflow.com serves an llms.txt and returns markdown when asked for it with an Accept header. The home page is 15,370 characters at a 7.8 percent text ratio, though with two H1s and thirty-eight H2s. What is missing is an OpenAPI specification, declared scopes, a typed error model and a versioning strategy, about 10 points of specification work. The WebMCP check could read none of the two script bundles, so that row is unverified. The domain ranks seventh for its own name. The specification is the one file between this B and 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.