Amplitude: the 360 agent-readiness check

Amplitude scores 91 of 100 on Ora's agent-readiness scan, an A, 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. A 91 with every act-layer surface in place and only response headers left.

On 9 November 2026 the public site at amplitude.com scored 91 of 100 on Ora's agent-readiness scan, an A, in Ora's Data & Analytics 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: Amplitude offers strong discovery and zero-auth llms.txt access, and returning JSON error responses from its API would round out agent support.

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, Amplitude 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 Amplitude, 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.

• JSON error responses: fail, 0 of 4, about 1.7 points to gain. Ora saw: API does not return JSON error responses (or no API detected)
• Idempotency-Key support: fail, 0 of 3, about 1.3 points to gain. Ora saw: No REST Idempotency-Key support detected
• JSON-LD entity linking (sameAs): fail, 0 of 2, about 1 points to gain. Ora saw: No sameAs entity linking in JSON-LD - agents cannot disambiguate your brand
• REST versioning / deprecation policy: partial, 1 of 3, about 0.9 points to gain. Ora saw: Deprecation or versioning policy mentioned in prose at https://amplitude.com/docs/llms.txt - formalize in OpenAPI spec for full credit
• Rate limit response headers: fail, 0 of 2, about 0.9 points to gain. Ora saw: No REST rate-limit headers found on probed endpoints

Our read

Amplitude scores 91 with a perfect Discovery layer and an act layer that passes every surface Ora tests: an MCP server at mcp.amplitude.com/mcp that answers and requires authentication, a server card at /.well-known/mcp/, OAuth authorization server metadata on the MCP host, an OpenAPI 3.1.0 specification at amplitude.com/openapi.json, @amplitude/ampli on npm, SDKs in npm, Go and rubygems, a WebMCP tool registered in a script bundle, an agent skills index, an llms.txt and markdown twins at /mcp.md and /index.md with the right content type. The 9 points left are the smallest kind: endpoints that do not answer errors as JSON, no Idempotency-Key, no rate-limit headers, a versioning policy stated in prose rather than in the specification, and an Organization block without sameAs links. The home page is 4.9 percent text, a tenth of a point under the target. An A in the analytics category, with nothing structural left to build.

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.