Square: the 360 agent-readiness check

Square scores 57 of 100 on Ora's agent-readiness scan, a C, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 1: OAuth. In the directory, Square sign-in required, tools not seen, not counted. A home page that renders 35 characters without JavaScript.

On 9 November 2026 the public site at squareup.com scored 57 of 100 on Ora's agent-readiness scan, a C, 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. Ora's one-line summary: Square's payments API documentation is reachable, but homepage content requires JavaScript rendering that blocks agent crawling.

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, Square 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 squareup.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 Square, 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.9 points to gain. Ora saw: No OpenAPI/Swagger specification found
• Scoped permissions: fail, 0 of 5, about 3.6 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
• WebMCP support: fail, 0 of 5, about 3.6 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found
• Developer resource discoverability: partial, 1 of 3, about 3.2 points to gain. Ora saw: Agent found 9 pages by name but no recognizable developer-resource type. Found on site but absent from this search sample: MCP server. Not found in this search sample: API docs, OpenAPI spec
• JSON error responses: fail, 0 of 4, about 2.9 points to gain. Ora saw: API does not return JSON error responses (or no API detected)

Our read

Square's home page gives an agent 35 characters of text. Everything else on squareup.com is rendered by JavaScript, so the content check fails outright, no inner page could be sampled and the Discovery layer reads 8 of 14, the lowest share in this batch. Behind that, the act layer is the familiar fintech shape: an MCP server at mcp.squareup.com/mcp that answers and requires authentication, OAuth authorization server metadata on the same host, developer documentation at developer.squareup.com and an llms.txt at the root, but neither an OpenAPI specification nor a CLI, endpoints that do not answer errors as JSON, and SDKs that are mentioned in the documentation and found in no registry. Ora's own search of the site found nine pages by name and no recognisable developer-resource type. The verdict is the one the checklist gives every JavaScript-only home page: render the text on the server, and the rest of the reading rows become possible.

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.