Heroku: the 360 agent-readiness check

Heroku scores 73 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. The best-built home page in the group, and a Person where the Organization should be.

On 9 November 2026 the public site at heroku.com scored 73 of 100 on Ora's agent-readiness scan, a B, 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: Heroku offers CLI and MCP server integration, but lacks OpenAPI specification and scoped OAuth permissions documentation.

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, Heroku 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 Heroku, 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 3.2 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
• WebMCP support: fail, 0 of 5, about 3.2 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 24 of 24 same-origin script bundle(s) for modelContext registrations)
• Developer resource discoverability: partial, 1 of 3, about 2.8 points to gain. Ora saw: In a search for your API docs, none of the 10 results is your official docs. In a search for your MCP server, SDK or CLI, we found your MCP server at #2 (https://github.com/heroku/heroku-mcp-server),
• Brand name discoverability: partial, 1 of 3, about 2.8 points to gain. Ora saw: heroku.com ranks #7 for "Heroku" (searched your brand name alone: no main product term from your homepage qualified)

Our read

Heroku's home page is the best-built in this group, 7,285 characters at an 8.6 percent text ratio with one H1, nine H2s and twenty-five H3s, and its act layer is live: the MCP server at mcp.heroku.com/mcp answers and requires authentication, llms.txt on the Dev Center references it, OAuth authorization server metadata is on the MCP host, the REST documentation scores 7 of 7, heroku-cli is on npm and SDKs are in four registries. The B rather than an A comes from a missing OpenAPI specification and the absence of declared scopes, about 7 points, and from discovery: heroku.com ranks seventh for its own name, and in a search for its API documentation none of the ten results is the Dev Center. The JSON-LD on the home page describes a Person rather than the company, which is the one structured-data oddity in this batch. Platform-as-a-service built for developers, and the search engines have not been told.

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.