Wix: the 360 agent-readiness check

Wix scores 65 of 100 on Ora's agent-readiness scan, a C, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 2: OAuth, a command line. An MCP server behind a login, and 56 characters of home page without JavaScript.

On 9 November 2026 the public site at wix.com scored 65 of 100 on Ora's agent-readiness scan, a C, 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: Wix offers strong discoverability and a published SDK and registry presence, but lacks a public OpenAPI spec and a reachable public API surface 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. 2 checks in this group do not apply to this site and are left out.

In the directory, Wix 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 Wix, 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.

• Public API with reachable endpoints: fail, 0 of 7, about 5.4 points to gain. Ora saw: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated)
• OpenAPI spec published: fail, 0 of 7, about 3.9 points to gain. Ora saw: No OpenAPI/Swagger specification found
• Scoped permissions: fail, 0 of 5, about 3.8 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
• WebMCP support: fail, 0 of 5, about 3.8 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found
• JSON error responses: fail, 0 of 4, about 3.1 points to gain. Ora saw: API does not return JSON error responses (or no API detected)

Our read

Wix has an MCP server and no public API an agent can reach without a key. The server at mcp.wix.com/mcp answers and requires authentication, OAuth authorization server metadata is on the same host, @wix/cli is on npm, SDKs are in npm and rubygems and wix.com serves an llms.txt. The public API check scored 0 of 7 because neither REST nor GraphQL answered anonymously, no documentation page is linked from the home page, the developer portal Ora found at /dashboard is a login, and there is no OpenAPI specification and no declared scopes. The home page gives an agent 56 characters of text without JavaScript, which is the content row failed outright, under an Organization block missing its description. For a platform that hosts millions of small-business sites, the act layer is a server behind a login and a home page that needs a browser; the checklist asks for a documentation page an agent can reach first.

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.