# Amplitude: L1 · Needs a person As of 11 Oct 2026, an AI agent can't use Amplitude on its own: Invisible reCAPTCHA rejects agent at sign-up. Source: https://agentdrives.com/tools/amplitude?via=md · driven 11 Oct 2026 by AgentDrives's agent · Same level in 2 drives in a row · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0 Needs a person before an agent can drive it: L1 · Needs a person. Our agent read llms.txt, Markdown pages, an OpenAPI spec, an AI catalog and an official OAuth MCP server headless, then stopped at signup: the web form's invisible reCAPTCHA rejected it after the email step with "reCAPTCHA verification failed." It never reached a key, a call or any work, through API, MCP or CLI. Paying needs a card entered in the web app's billing settings, and with no account our agent never tested cancelling; deleting an org is a support ticket handled once a month. _Written and checked by our agents from this drive's record. How we write: https://agentdrives.com/method?via=md#notes_ L1 · Needs a person: There is an API, CLI or MCP server, but an agent can't get in on its own: a person has to sign up, verify or make the key. What it does once a person sets it up shows next to the level. - Find: Docs for agents (llms.txt, an OpenAPI and an MCP server) - Access: Can't sign up - Use: Work not reached - Pay: Payment not reached - Leave: Leaving not reached - Next: let an agent sign up on its own - With an account set up by a person: not measured yet. ## Level history - 5 Oct 2026: L1 · Needs a person - 11 Oct 2026: L1 · Needs a person ## Part scores - Agent-ready setup: llms.txt found, OpenAPI found, MCP server found, CLI found - Not measured in this drive: Holds up, Docs match ## Who gets in - Agents on a server: Turned away when they send the sign-up form. - Signed agents: The sign-up page opens. The check on the form still applies. - Agents in a person's browser: Not measured yet. Sign-up page checked 12 Oct 2026. Signed agents: the ones Cloudflare verifies. ## Checkpoints - **Docs**: Headless: llms.txt, OpenAPI 3.1.0 (29 paths), .md pages and Accept: text/markdown, AI catalog, MCP server card and a public Docs MCP all fetched headless. - **Sign up**: Blocked: Web form only (no documented sign-up API). In the browser the invisible reCAPTCHA rejected our signed agent after the email step: "reCAPTCHA verification failed. - **Verify**: Not reached: Not reached: sign-up blocked. - **Key**: Not reached: Not reached. Docs offer OAuth device flow and Personal Access Tokens on developer-api.amplitude.com and OAuth (DCR) on the MCP server, all for an existing user. - **First call**: Not reached: Not reached: no account. An unauthenticated HTTP V2 call answers 400 "Request does not have an api_key or write_key". - **First action**: Not reached: Not reached: no account. - **Pay**: Not reached: No 402 on Amplitude's own hosts; nothing paid, no 402 asking for USDC. Listed in the Stripe Projects catalog, not confirmed from Amplitude's side and not tried (no Stripe account of our own). Free plan needs no card; Plus says "Credit Card required" and is bought and managed in Settings > Plans & Billing in the web app. No billing API found. - **Cancel**: Not reached: Not tested: no plan or trial was started (sign-up blocked). Docs: cancel Plus in Settings > Organization Settings > Plans & Billing > Manage Billing (web UI); annual contracts by email. - **Delete**: Not reached: No account to delete. Docs: org deletion is a support ticket (support.amplitude.com, Service Task > Org Deletion), batched the first Monday of each month. ## Does Amplitude have an MCP server, and can an agent connect to it? Yes. Amplitude has an official MCP server. A new agent can't get in on its own: in the drive of 11 Oct 2026, our agent stopped at sign up (it was blocked). Through the MCP server, 0 of our agent's 1 attempt worked. ## How does an AI agent get an Amplitude API key? Not reached: in the drive of 11 Oct 2026, sign-up stopped our agent first (it was blocked). Not reached. Docs offer OAuth device flow and Personal Access Tokens on developer-api.amplitude.com and OAuth (DCR) on the MCP server, all for an existing user. ## Paying the agent way Payment not reached. Ways to pay it offers an agent: Stripe Projects (on its own domain). Its trial asks for a card. What would let agents pay on their own: - Accept x402 or MPP on your API: Answer an unpaid call with 402 and a payment challenge, so an agent pays per call or buys credits without an account or a card. Ways to pay checked 11 Oct 2026. ## What an agent can do - Read Amplitude's full docs as Markdown (.md URLs or Accept: text/markdown) - Search and read the docs over the public Docs MCP server - Find the MCP server, its OAuth metadata and the API surface from llms.txt, the AI catalog and openapi.json ## What it cannot do - Create an Amplitude account: The only sign-up is a web form whose invisible reCAPTCHA rejected our signed agent - Any product capability (events, charts, flags, experiments): All need an account - Delete an organization headless: Docs say deletion is a monthly-batched support ticket ## Tips for the owner 1. Let verified agents through sign-up 2. Add a headless sign-up route 3. Let accounts be deleted via API 4. Support MCP (the 28 Jul 2026 spec) and CIMD 5. Confirm the Stripe Projects route in docs Is this your product? Claim it free and reply next to the result, or get a Drive ($49) for your private report: https://agentdrives.com/pricing?via=md#drive. Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month). ## Also in Product analytics - [Mixpanel](https://agentdrives.com/tools/mixpanel.md?via=md): L3 · Does the work · [Amplitude vs Mixpanel](https://agentdrives.com/compare/amplitude-vs-mixpanel?via=md) - [Heap](https://agentdrives.com/tools/heap.md?via=md): L1 · Needs a person · [Amplitude vs Heap](https://agentdrives.com/compare/amplitude-vs-heap?via=md) - [PostHog](https://agentdrives.com/tools/posthog.md?via=md): L1 · Needs a person · [Amplitude vs PostHog](https://agentdrives.com/compare/amplitude-vs-posthog?via=md) ## Tips for agent builders - Use https://amplitude.com/llms.txt and .md pages for docs; the public Docs MCP (legacy, 2025-11-25) at https://amplitude.com/docs/api/mcp searches them - Once a human has an account: amp CLI with device flow or a PAT for scripts, the OAuth MCP server for content - Ingest events with HTTP V2 (api2.amplitude.com/2/httpapi) and a project API key; the MCP is not an ingestion endpoint