Pirsch vs Fathom Analytics for AI agents
As of 12 Oct 2026, both reach L1 · Needs a person, and our agent got as far with each: with Pirsch it was stopped at sign up (needs a human), with Fathom Analytics it was stopped at sign up (blocked).
- Find: Some docs for agents: An MCP server.
- 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 · L1 stops our agent cold. It read the public docs headlessly, then reached pirsch.io/signup and hit an ALTCHA "I'm not a robot" checkbox: our agent does not tick a bot check itself, and no sign-up API is documented, so verification, keys and the first call were never reached. The REST API behind that wall covers account work end to end, including deleting the account, and a third-party MCP server is linked from the docs. None of it was exercised: work done stayed at nothing. Paying runs through a hosted Stripe checkout, and the trial needs no card, but a person still has to get past the signup form first.
Driven 12 Oct 2026 · The drive and its evidence- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Needs a card to start.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: blocked. Next: let an agent start without a card
Needs a person to get in: L1 · Needs a person. Our agent stopped at signup: the trial form asks for a card and ZIP code before it starts, and there is no sign-up API. Our agent could not enter payment details, so the form went unsubmitted. Account creation, verification and the API token page were never reached. Docs are strong: a Markdown API reference and an OpenAPI schema are both fetched headless. Still, a person must sign up, add a card and create the token before any call works. Cancelling needs a person in web billing settings; deletion then follows on its own.
Driven 6 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.
PirschStopped at sign up: needs a human
Fathom AnalyticsStopped at sign up: blocked
| Checkpoint | Pirsch | Fathom Analytics |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | Blocked |
| 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
| Pirsch | Fathom Analytics | |
|---|---|---|
| Headless (checkpoints) | 1 | 1 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 1 | 0 |
| Blocked (checkpoints) | 0 | 1 |
| Not tested (checkpoints) | 7 | 7 |
| Work done | Not measured | Not measured |
| API | Yes | Yes |
| OpenAPI | No | Yes |
| MCP server | Yes (third-party) | Yes (third-party) |
| CLI | No | No |
| SDK | Yes | No |
| llms.txt | No | Yes |
Bot checks, and where a person was needed.
| Pirsch | Fathom Analytics | |
|---|---|---|
| Bot check | ALTCHA (proof of work) stopped it at sign up, with a visible challenge | None met |
| Wall type | A challenge on the form | No bot-check wall |
| First wall | ALTCHA checkbox on the sign-up form | Credit card required to sign up |
| 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. Where we drive from.
Level and part scores.
| Pirsch | Fathom Analytics | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 45 of 100, poor | 80 of 100, fair |
| Standards | MCP spec of 28 Jul 2026 (current) · MCP discovery (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.
| Pirsch | Fathom Analytics | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Trial, no card | Trial with a card |
| Cancel | Not reached | Not reached |
| Delete the account | Not reached | Not reached |
How each one takes payment
- Pirsch: Payment not reached.
- Fathom Analytics: Payment not reached.
Pirsch vs Fathom Analytics: the short answers.
Which can an AI agent use, Pirsch or Fathom Analytics?
Both reach L1 · Needs a person, and our agent got as far with each: with Pirsch it was stopped at sign up (needs a human), with Fathom Analytics it was stopped at sign up (blocked). Driven 12 Oct 2026 (Pirsch) and 6 Oct 2026 (Fathom Analytics).
Can an AI agent sign up for Pirsch and Fathom Analytics on its own?
Pirsch: no, needs a human. Fathom Analytics: no, blocked.
Do Pirsch and Fathom Analytics have an MCP server?
Pirsch: yes (third-party). Fathom Analytics: yes (third-party).
Can an AI agent delete its Pirsch or Fathom Analytics account?
Pirsch: not reached. Fathom Analytics: 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.