Amplitude vs Heap for AI agents
As of 12 Oct 2026, both reach L1 · Needs a person, and our agent got as far with each: with Amplitude it was stopped at sign up (blocked), with Heap it was stopped at sign up (needs a human).
- 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.
Stopped at sign up: blocked. Next: let an agent sign up on its own
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.
Driven 11 Oct 2026 · The drive and its evidence- Find: Some docs for agents: llms.txt and an OpenAPI.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: needs a human. Next: let an agent sign up on its own
Needs a person to get in: L1 · Needs a person. Our agent read Heap's docs, which already suit an agent well: an llms.txt, Markdown pages, and an OpenAPI definition on every reference page. Sign-up only runs through a web form, and submitting it showed a reCAPTCHA image puzzle our agent couldn't get past. No account was made, so verifying, getting a key and calling the API were never reached. Paying wasn't tested either: checkout sits behind the same sign-up, and Heap's Growth pricing asks a person to sign up for an estimate. With no account, there was nothing to cancel or delete.
Driven 12 Oct 2026 · The drive and its evidenceThe two summaries: written and checked by our agents from each product's drive. How we write.
Where each one stops.
AmplitudeStopped at sign up: blocked
HeapStopped at sign up: needs a human
| Checkpoint | Amplitude | Heap |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Blocked | Needs a human |
| Verify | Not reached | Not reached |
| Key | Not reached | Not reached |
| First call | Not reached | Not reached |
| First action | Not reached | Not reached |
| Pay | Not reached | Not reached |
| Cancel | Not reached | Not reached |
| Delete | Not reached | Not reached |
Headless or in a browser.
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| Amplitude | Heap | |
|---|---|---|
| Headless (checkpoints) | 1 | 1 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 0 | 1 |
| Blocked (checkpoints) | 1 | 0 |
| Not tested (checkpoints) | 7 | 7 |
| Work done | Not measured | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | – |
| CLI | Yes | No |
| SDK | Yes | – |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Amplitude | Heap | |
|---|---|---|
| Bot check | reCAPTCHA (invisible) stopped it at sign up, without a visible challenge | Google reCAPTCHA v2 (image challenge) stopped it at sign up, with a visible challenge |
| Wall type | A check of our network and browser | A challenge on the form |
| First wall | Invisible reCAPTCHA rejects agent at sign-up | reCAPTCHA image puzzle on sign-up form |
| A person helped | No | No |
A check of our network and browser: It judged where our agent connects from and its browser, not a person. An agent that works on its own from a data center doesn't get through unless the owner lets signed agents in. How agents in a person's own browser fare isn't measured yet. A challenge on the form: It asks every visitor to prove they are human. It stops every agent on any network, and a signature doesn't help: a person does this step, or the owner opens it for agents. Where we drive from.
Level and part scores.
| Amplitude | Heap | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 100 of 100, good | 90 of 100, good |
| Standards | MCP client registration (behind) · OpenAPI 3.1.0 (1 version behind) | OpenAPI 3.1.0 (1 version behind) |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Amplitude | Heap | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not reached | Not reached |
| Delete the account | Not reached | Not reached |
How each one takes payment
- Amplitude: Payment not reached.
- Heap: Payment not reached.
Amplitude vs Heap: the short answers.
Which can an AI agent use, Amplitude or Heap?
Both reach L1 · Needs a person, and our agent got as far with each: with Amplitude it was stopped at sign up (blocked), with Heap it was stopped at sign up (needs a human). Driven 11 Oct 2026 (Amplitude) and 12 Oct 2026 (Heap).
Can an AI agent sign up for Amplitude and Heap on its own?
Amplitude: no, blocked. Heap: no, needs a human.
Do Amplitude and Heap have an MCP server?
Amplitude: yes (official). Heap: none found.
Can an AI agent delete its Amplitude or Heap account?
Amplitude: not reached. Heap: not reached.
The drives and the category.
Put your own shortlist side by side.
A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.