Agent readiness · Product analytics
amplitude.com
10 of 14 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with. 2 of them could not be measured from where we ask, and those are left out of the denominator rather than counted as failures.
A · Discovery
- PASSAnswers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
- PASSllms.txt publishedllms.txt and llms-full.txt present at https://amplitude.com/llms.txt and https://amplitude.com/llms-full.txt and https://amplitude.com/docs/llms.txt, and the 12 links we sampled across both files all answer
- PASSDocs readable without JavaScript5,809 characters of text without JS, on https://amplitude.com/docs/apis/keys-and-tokens rather than on https://amplitude.com/docs
- PASSOn-demand agents not blockedExplicitly allowed: ChatGPT-User, Perplexity-User
- N/APaths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
- PASSNo punishing crawl delayNo Crawl-delay applies to the agents we check
B · Agent entry
- FAILAgent entry pointNone of the 9 known agent entry paths returns a file rather than your page shell
- PASSOAuth dynamic client registrationregistration_endpoint published, but none of the 4 advertised grants (authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:jwt-bearer) finishes without a person at a browser
- PASSMCP surfaceLive MCP endpoint at https://mcp.amplitude.com/mcp, answered 401 with an auth challenge
C · Registration
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://app.amplitude.com/signup?siteLocation=nav is not in the server HTML, so its gates are not eitherServer-render the form, or tell us the endpoint it posts to, and the gates become visible to us and to an agent.
- FAILSignup reachable without a browserhttps://app.amplitude.com/signup?siteLocation=nav is reachable, but its form needs JavaScript
D · Provisioning
- PARTProgrammatic key provisioning1 of 7 provisioning phrases across the 7 documents we read: "management api"
- UNMEASUREDFree tier or no-card trial stated in textUnmeasurable: https://amplitude.com/pricing?siteLocation=nav is larger than we read, so anything we did not find in it is a fact about our cap and not about your tiersNothing for you to do. A smaller pricing page, or one that states its tiers early, makes this measurable.
E · Integration
- PASSTyped SDK on the registry@amplitude/analytics-browser@2.45.5 ships types
- PASSMachine-readable API descriptionDocs serve markdown to machines, at https://amplitude.com/docs.md
Tell me when this changes
The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.
This page is the newest scan we hold for amplitude.com and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.