Amplitude vs Heap
Amplitude scores higher on the AgentReady, 83/100 against 42/100. They differ on 24 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Amplitude. Amplitude is a product analytics platform that helps teams understand user behavior, run experiments, and build better products.
Heap. Heap is a digital analytics platform that automatically captures every user interaction to help companies understand customers' end-to-end journeys, improve conversion and activation, increase retention, and deliver great user experiences.
Where Amplitude is ahead
Amplitude passes public docs discoverable, llms.txt published, llms-full.txt / full agent docs and mcp discoverable, and Heap does not. That is discover, whether an agent can find the product at all without being told it exists.
It also holds understand: structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented and limits / constraints documented. Heap misses those.
And on adopt, agent-compatible signup flow, programmatic credential creation, cli available and mcp integration available. Heap misses those.
Finally, on operate, structured, predictable output, machine-readable errors, rate-limit behavior predictable and agent compatibility verified. Heap misses those.
Where Heap is ahead
Heap passes search discoverable, and Amplitude does not. That is discover, whether an agent can find the product at all without being told it exists.
It also holds understand: pricing understandable. Amplitude misses it.
And on adopt, self-service signup, free trial or free allowance and fast time to first request. Amplitude misses those.
What neither does
Both fail no mandatory sales call, retry behavior documented, idempotency support. If your agent needs any of those, you will be building it yourself either way.
Score, pillar by pillar
The AgentReady splits into four pillars, scored separately, because a product can be easy to find and still impossible to adopt.
Discover. Amplitude leads 87 to 60. Amplitude misses search discoverable; Heap misses public docs discoverable, llms.txt published, llms-full.txt / full agent docs, mcp discoverable.
Understand is whether an agent can read the docs and work out how the API behaves before calling it. Amplitude leads 92 to 23. Amplitude misses pricing understandable; Heap misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.
Adopt. Amplitude leads 65 to 50. Amplitude misses self-service signup, no mandatory sales call, free trial or free allowance, fast time to first request; Heap misses no mandatory sales call, agent-compatible signup flow, programmatic credential creation, cli available, mcp integration available.
Operate. Amplitude leads 88 to 35. Amplitude misses retry behavior documented, idempotency support; Heap misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.
Pricing
Amplitude does not publish a machine-readable starting price. Heap does not publish one and has a free tier.
| Amplitude plans | Heap plans |
|---|---|
| - | Free $0 |
| - | Growth Custom |
| - | Pro Custom Session Pricing |
| - | Premier Custom Session Pricing |
Signal by signal
| Signal | Amplitude | Heap |
|---|---|---|
| AgentReady | 83 | 42 |
| Discovery | 87 | 60 |
| Understanding | 92 | 23 |
| Adoption | 65 | 50 |
| Operability | 88 | 35 |
| Public API | Yes | Yes |
| MCP server | Yes | No |
| OpenAPI spec | Yes | Unknown |
| CLI | Yes | Unknown |
| llms.txt | Yes | Unknown |
| Self-serve signup | Unknown | Yes |
| Free tier | Unknown | Yes |
Which to pick
Amplitude clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Amplitude and Heap. Alternatives to each: Amplitude, Heap.
An agent can fetch this as data: POST /v1/compare {"slugs": ["amplitude", "heap"]}