Fly.io: the 360 agent-readiness check

Fly.io scores 97 of 100 on Ora's agent-readiness scan, the top grade, 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. The highest mark of the sixty, with three points left in response headers.

On 9 November 2026 the public site at fly.io scored 97 of 100 on Ora's agent-readiness scan, the top grade, 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: The site offers strong discovery and REST API schema quality, and publishing rate-limit response headers would give agents clearer backoff signals.

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, Fly.io 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 fly.io.

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 Fly.io, 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.

• Rate limit response headers: fail, 0 of 2, about 0.7 points to gain. Ora saw: No REST rate-limit headers found on probed endpoints (GraphQL signal: fail 0).
• Content without JavaScript: partial, 2 of 3, about 0.5 points to gain. Ora saw: Homepage: 3329 chars with H1, but 3.0% content ratio is below the 5% target. 5 of 5 sampled inner pages have text without JavaScript.
• Schema type breadth: partial, 1 of 2, about 0.5 points to gain. Ora saw: Some extended schema types found: Service - add 2 more types that match what the homepage shows, for full coverage
• REST async-job pattern: partial, 1 of 2, about 0.4 points to gain. Ora saw: 202 Accepted responses found but no clear polling pattern (Location header, /jobs path, or job_id schema)
• MCP server / manifest: partial, 5 of 6, about 0.4 points to gain. Ora saw: MCP server detected at https://mcp.fly.io; it requires authentication. Presence is verified (5/6), but Ora could not inspect its tools or verify access scopes without credentials.

Our read

Fly.io scores 97 and an A plus, the highest mark in this directory and the closest any company here comes to passing everything. The act layer is whole: an MCP server at mcp.fly.io that answers and requires authentication, its server card listed in /.well-known/ai-catalog.json, OAuth authorization server metadata at fly.io/mcp/oauth, an OpenAPI 3.1.0 specification for the Machines API, a GraphQL endpoint that is reachable, @fly/cli on npm, SDKs in four registries, a WebMCP tool registered in a script bundle, an agent skills index, an llms.txt and markdown twins at /agents.md, /auth.md and /index.md. Seven JSON-LD blocks describe the company. What Ora still marks down is worth about 3 points in all: no rate-limit headers on the REST endpoints it probed, 202 responses without a clear polling pattern, a home page at a 3 percent text ratio and one extended schema type where it would like three. The reference read of the set, from a platform that hosts the agents.

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.