Can an AI agent sign up for Amplitude on its own?

No. 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.

Amplitudeamplitude.com

Can an AI agent use Amplitude?

Q: Can an AI agent pay for Amplitude?

Payment 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.

As of 11 Oct 2026, an AI agent can't use Amplitude on its own: Invisible reCAPTCHA rejects agent at sign-up.

Level 1 · Needs a personAgents can't get in on their own.

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.

To reach L2 · Gets in: let an agent sign up on its own.

With an account set up by a person: not measured yet.

What the levels mean

Visit Amplitude Follow changes

Driven 11 Oct 2026Same level in 2 drives in a rowRules of 15 Oct 2026Claim this page

Written and checked by our agents from this drive's record. How we write.

Who gets in

Agents on a serverTurned away when they send the sign-up form.
Signed agentsThe sign-up page opens. The check on the form still applies.
Agents in a person's browserNot measured yet.

Sign-up page checked 12 Oct 2026. Signed agents: the ones Cloudflare verifies. Where agents come from

What an agent can do in Amplitude.

On its own

Read all of Amplitude's documentation in agent-friendly formats
Find the technical details of how to connect to Amplitude's AI assistant

What it can't, and why

Create an Amplitude accountAn invisible bot check on the sign-up form rejected the agent with no visible puzzle to solve
Use any Amplitude feature (charts, events, experiments, etc.)Every feature requires a signed-in account, which could not be created
Cancel a subscriptionNo plan was ever started, so this was never tried

1 more

Delete an accountNo account existed to delete, and Amplitude only deletes accounts through a manual support ticket

Official server · no call worked

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.

What the drive found

APIOpenAPIMCP · officialCLISDKllms.txtWebhooks–Sandbox

Payment not reached

Can an AI agent pay for Amplitude?

Payment not reached.

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.Step-by-step guide

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.

Ways to pay checked 11 Oct 2026.

Not reached in this drive: the API key and deleting the account. Every checkpoint, in detail

For the team behind Amplitude.

Where agents stop in Amplitude today, and the fixes that get them further, highest impact first.

Stops at sign up

The fixes, highest impact first

Let verified agents through sign-upStep-by-step guide
Add a headless sign-up routeStep-by-step guide
Let accounts be deleted via API

2 more fixes

Support MCP (the 28 Jul 2026 spec) and CIMD Step-by-step guide
Confirm the Stripe Projects route in docs Step-by-step guide

Claim it free and reply next to the result.
A Drive, $49: your private report, with where agents stop, the evidence and the fixes that move your level.
Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).

Get a Drive Claim it free

See the example report

Details

Your API, MCP server or CLI is the product? An Audit ($299) also checks every documented route, MCP tool and CLI command against your docs. Compare plans.

Already claimed it? Open it in your dashboard.

Rather not be driven? Block AgentDrivesAgent in robots.txt or write to us. We stop driving it ourselves; this page stays, with its date.

Embed the badge on your site

<a href="https://agentdrives.com/tools/amplitude" rel="nofollow"><img src="https://agentdrives.com/badge/amplitude.svg" alt="AgentDrives · Driven · L1 · Needs a person" height="24"></a>

Behind the level.

Our agent couldn't get into Amplitude, so the work, its reliability and the crash test aren't measured. The part scores are what it could judge from the outside.

Part scores · level history

Part scores

Agent-ready setup

llms.txt: found
OpenAPI: found
MCP server: found
CLI: found

Not measured in this drive: Holds up, Docs match (part of an Audit).

Level history

5 Oct 2026L1Needs a person
11 Oct 2026L1Needs a person

For agents and builders.

The drive as data, every checkpoint and all 10 attempts.

How an agent connects · 3 tips

/api/tools/amplitude.json /tools/amplitude.mdMCP get_tool {"slug":"amplitude"}

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

Every checkpoint, in detail · 9 checkpoints

DocsHeadlessllms.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 upBlockedWeb form only (no documented sign-up API). In the browser the invisible reCAPTCHA rejected our signed agent after the email step: "reCAPTCHA verification failed.
VerifyNot reachedNot reached: sign-up blocked.
KeyNot reachedNot 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 callNot reachedNot reached: no account. An unauthenticated HTTP V2 call answers 400 "Request does not have an api_key or write_key".
First actionNot reachedNot reached: no account.
PayNot reachedNo 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.
CancelNot reachedNot tested: no plan or trial was started (sign-up blocked). Amplitude has a paid Plus plan that could recur, so cancelling is untested. Docs: cancel Plus in Settings > Organization Settings > Plans & Billing > Manage Billing (web UI); annual contracts by email.
DeleteNot reachedNo account to delete. Docs: org deletion is a support ticket (support.amplitude.com, Service Task > Org Deletion), batched the first Monday of each month.

The attempt log · 10 attempts

Attempt log
Capability	Route	Result	Evidence
docs: robots.txt, llms.txt, openapi	api	done ✓	robots.txt 200: User-agent * Allow / with Content-Signal: search=yes, ai-input=yes, ai-train=yes (Cloudflare Content Signals syntax, parses); no Content-Usage aipref line. /llms.txt 200 text/plain with agent install guide. /openapi.json 200, openapi 3.1.0, Amplitude Public APIs, 29 paths (HTTP V2, batch, dashboard REST, export, cohorts, taxonomy)
mcp: server/discover on https://mcp.amplitude.com/mcp	mcp	blocked ✓	POST server/discover with MCP-Protocol-Version 2026-07-28 -> 401, WWW-Authenticate Bearer resource_metadata=https://mcp.amplitude.com/.well-known/oauth-protected-resource; PRM 200 (root), path-suffixed /mcp 404; AS metadata: authorization_code+PKCE S256, refresh, jwt-bearer, token-exchange, registration_endpoint (DCR), no client_id_metadata_document_supported, no device flow; exposes Mcp-Session-Id header
cards: AI catalog, server card, A2A card, markdown	api	done ✓	/.well-known/ai-catalog.json 200 JSON (specVersion 1.0, entry Amplitude MCP Server); /.well-known/mcp/server-card.json 200 JSON (com.amplitude/amplitude-mcp 0.4.0, streamable-http); <mcp>/server-card 404; /.well-known/agent-card.json and agent.json 404; Accept text/markdown on docs page -> text/markdown, Vary: Accept, x-markdown-tokens 17088; .md URLs 200 text/markdown; /auth.md 404; /.well-known/ucp 404
docs mcp: server/discover then initialize on public Docs MCP https://amplitude.com/docs/api/mcp	mcp	done ✓	server/discover 2026-07-28 -> HTTP 400 JSON-RPC -32000 "Unsupported protocol version: 2026-07-28 (supported versions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)"; initialize offering 2026-07-28 -> protocolVersion 2025-11-25, serverInfo amplitude-docs 1.1.0, stateless (no Mcp-Session-Id returned); tools/list: get_page, list_pages, search_docs, amplitude_implementation_planner, send_docs_mcp_feedback
cli/device flow: read CLI auth docs	api	done ✓	https://amplitude.com/docs/developers/cli/authentication.md: amp CLI over Developer API (developer-api.amplitude.com); OAuth device flow POST /v1/auth/device-authorization + grant urn:ietf:params:oauth:grant-type:device_code; Personal Access Tokens. Both need an existing Amplitude user; no documented sign-up API.
sign up: Sign up headless	none	blocked ✓	No documented API/CLI/MCP sign-up: llms.txt, CLI auth docs and MCP docs all assume an existing Amplitude user (device flow, PAT, OAuth). Stripe Projects lists Amplitude as a provider (pay_probe registry), but we have no Stripe account/CLI of our own to try it.
sign up: Sign up in browser at app.amplitude.com/signup with the agent's inbox	browser	blocked ✓	Form: Work Email + Continue, invisible reCAPTCHA ("This site is protected by reCAPTCHA"). After Continue the page moved to /login and showed "reCAPTCHA verification failed. Please try again." visible_challenge false, no puzzle shown.
pay step public probes: Find an agent way to pay: 402s, registries, billing API, checkout	api	done ✓	pay_probe.json: no 402 challenge on amplitude.com, api.amplitude.com, x402./mpp. subdomains; not in mpp.dev or x402 Bazaar; listed in the Stripe Projects catalog (Amplitude: Analytics, feature flags; docs.stripe.com/projects); openapi.json has no x-payment-info; /.well-known/ucp 404. pay_tx.json: refused, no 402 asking for USDC. Pricing page: Free plan $0 no credit card, not a trial; Plus "Credit Card required". Billing FAQ: Plus managed in Settings > Organization Settings > Plans & Billing > Manage Billing (web UI); no billing API in the Developer API docs found.
cancel plan: Cancel a started plan	none	skipped	Not tested: no plan or trial was started (sign-up blocked). docs/faq/billing-and-plans: "Go to Settings > Organization Settings > Plans & Billing > Manage Billing to cancel your subscription" (web UI); annual Plus/Growth contracts via scholarship@amplitude.com email.
delete account: Delete the account	none	blocked	No account was created (sign-up blocked by reCAPTCHA). Docs (admin/account-management/manage-orgs-projects): org deletion is a support ticket at support.amplitude.com (Service Task > Org Deletion), handled the first Monday of each month; Growth/Enterprise via CSM. No API/CLI delete documented.

Also in Product analytics.

All of Product analytics, by level

MixpanelL3Gets in on its ownAmplitude vs Mixpanel
HeapL1Can't sign up on its ownAmplitude vs Heap
PostHogL1Can't sign up on its ownAmplitude vs PostHog