Umami vs Fathom Analytics for AI agents
As of 8 Oct 2026, Umami gets an AI agent further: L3 · Does the work against L1 · Needs a person.
- Find: Some docs for agents: llms.txt and an MCP server.
- Access: Signs up in a browser.
- Use: 75% of the work.
- Pay: Payment not tried: robots.txt keeps our agent off the payment page for now.
- Leave: Leaves on its own: Nothing to cancel, deletes its account.
Got in, in a browser; the API is paid. Next: do 80% of the core work (now 75%)
Gets in on its own: L3 · Does the work. Our agent signs up for Umami Cloud without a bot check and reaches the dashboard unaided. It stopped at Settings > API keys, which answers "API access requires a Pro plan." The documented send endpoint took hits with no key, but dropped them as bot traffic, leaving every report empty. In the browser it added a website, set goals and funnels, made shares and links, then deleted the account: login after that returned invalid-credentials, though a short link still redirected minutes later. Upgrading redirects to Stripe's checkout, which robots.txt keeps our agent off, so whether the trial needs a card is unknown.
Gets furtherDriven 8 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.
UmamiGot in, in a browser; the API is paid
Fathom AnalyticsStopped at sign up: blocked
| Checkpoint | Umami | Fathom Analytics |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | In a browser | Blocked |
| Verify | In a browser | Not reached |
| Key | Blocked | Not reached |
| First call | Blocked | Not reached |
| First action | In a browser | Not reached |
| Pay | Not tried | Not reached |
| Cancel | Not needed | Not reached |
| Delete | In a browser | 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
| Umami | Fathom Analytics | |
|---|---|---|
| Headless (checkpoints) | 1 | 1 |
| In a browser (checkpoints) | 4 | 0 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 2 | 1 |
| Not tested (checkpoints) | 1 | 7 |
| Work done | 75% of the core | Not measured |
| API | Yes | Yes |
| OpenAPI | No | Yes |
| MCP server | Yes (official) | Yes (third-party) |
| CLI | No | No |
| SDK | Yes | No |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Umami | Fathom Analytics | |
|---|---|---|
| Bot check | None met | None met |
| Wall type | No bot-check wall | No bot-check wall |
| First wall | Got in, in a browser; the API is paid | Credit card required to sign up |
| A person helped | No | No |
Level and part scores.
| Umami | Fathom Analytics | |
|---|---|---|
| Level | L3 · Does the work | L1 · Needs a person |
| Holds up | 64 of 100, fair | Not measured |
| Agent-ready setup | 75 of 100, fair | 80 of 100, fair |
| Standards | None recorded | OpenAPI 3.1.0 (1 version behind) |
| Security | Reported privately to the owner | No review in this drive |
Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Umami | Fathom Analytics | |
|---|---|---|
| Pay | Payment not tried | Payment not reached |
| Free plan or trial | Free plan | Trial with a card |
| Cancel | Not needed | Not reached |
| Delete the account | In a browser | Not reached |
How each one takes payment
- Umami: Not tried yet: robots.txt keeps our agent off the payment page for now.
- Fathom Analytics: Payment not reached.
Umami vs Fathom Analytics: the short answers.
Which can an AI agent use, Umami or Fathom Analytics?
Umami gets an AI agent further: L3 · Does the work against L1 · Needs a person. With Umami our agent got in, in a browser (the API is paid); with Fathom Analytics it was stopped at sign up (blocked). Driven 8 Oct 2026 (Umami) and 6 Oct 2026 (Fathom Analytics).
Can an AI agent sign up for Umami and Fathom Analytics on its own?
Umami: yes, in a browser. Fathom Analytics: no, blocked.
Do Umami and Fathom Analytics have an MCP server?
Umami: yes (official). Fathom Analytics: yes (third-party).
Can an AI agent delete its Umami or Fathom Analytics account?
Umami: yes, in a browser. 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.