Heap vs PostHog for AI agents
As of 12 Oct 2026, both reach L1 · Needs a person, and with each our agent was stopped at sign up (needs a human).
- 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 evidence- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Signs up sometimes.
- 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
L1 · Needs a person describes PostHog today: docs are built for an agent to read, but no agent can open an account on its own. Our agent stopped at signup: the documented headless path answered 403, "Account creation is not enabled for this partner," and the web form ends in a visible Cloudflare Turnstile. With no account, the key page, the first call and any real work through the API, CLI or MCP server stayed out of reach. Paying, cancelling and deleting were never reached either, since no plan was ever started.
Driven 3 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.
HeapStopped at sign up: needs a human
PostHogStopped at sign up: needs a human
| Checkpoint | Heap | PostHog |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | 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
| Heap | PostHog | |
|---|---|---|
| Headless (checkpoints) | 1 | 1 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 1 | 1 |
| Blocked (checkpoints) | 0 | 0 |
| Not tested (checkpoints) | 7 | 7 |
| Work done | Not measured | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | – | Yes (official) |
| CLI | No | Yes |
| SDK | – | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Heap | PostHog | |
|---|---|---|
| Bot check | Google reCAPTCHA v2 (image challenge) stopped it at sign up, with a visible challenge | Cloudflare Turnstile (visible 'Verify you are human' on the last sign-up step) stopped it at sign up, with a visible challenge |
| Wall type | A challenge on the form | A check of our network and browser |
| First wall | reCAPTCHA image puzzle on sign-up form | Turnstile on sign-up; wizard sign-up refused (403) |
| A person helped | No | No |
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. 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. Where we drive from.
Level and part scores.
| Heap | PostHog | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 90 of 100, good | 100 of 100, good |
| Standards | OpenAPI 3.1.0 (1 version behind) | MCP client registration (current) · 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.
| Heap | PostHog | |
|---|---|---|
| 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
- Heap: Payment not reached.
- PostHog: Payment not reached.
Heap vs PostHog: the short answers.
Which can an AI agent use, Heap or PostHog?
Both reach L1 · Needs a person, and with each our agent was stopped at sign up (needs a human). Driven 12 Oct 2026 (Heap) and 3 Oct 2026 (PostHog).
Can an AI agent sign up for Heap and PostHog on its own?
Heap: no, needs a human. PostHog: no, needs a human.
Do Heap and PostHog have an MCP server?
Heap: none found. PostHog: yes (official).
Can an AI agent delete its Heap or PostHog account?
Heap: not reached. PostHog: 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.