Plausible Analytics vs Umami for AI agents
As of 11 Oct 2026, both reach L3 · Does the work. Our agent got further with Plausible Analytics: with Plausible Analytics it got in on its own and did 75% of the work, with Umami it got in, in a browser (the API is paid).
- Find: No docs for agents.
- Access: Sign-up in a browser.
- Use: 75% of the work.
- Pay: Payment not reached.
- Leave: Leaves on its own: Nothing to cancel, deletes its account.
In on its own; 75% of the work done. Next: do 80% of the core work (now 75%)
Gets in on its own: L3 · Does the work. No stop: an invisible challenge at signup let our agent through, and it reached every checkpoint through account deletion. Once in, it added a site through the web and read stats headless over the Stats API. Creating sites or goals through the API answered 401 on the trial key. Events API calls came back dropped. The funnel report timed out and was never confirmed. No card is asked to start, upgrading runs through a payment processor the docs name, and deleting the account is a single confirm with no API route.
Gets furtherDriven 11 Oct 2026 · The drive and its evidence- 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.
Driven 8 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.
Plausible AnalyticsIn on its own; 75% of the work done
UmamiGot in, in a browser; the API is paid
| Checkpoint | Plausible Analytics | Umami |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | In a browser | In a browser |
| Verify | In a browser | In a browser |
| Key | In a browser | Blocked |
| First call | Headless | Blocked |
| First action | In a browser | In a browser |
| Pay | In a browser | Not tried |
| Cancel | Not needed | Not needed |
| Delete | In a browser | In a browser |
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
| Plausible Analytics | Umami | |
|---|---|---|
| Headless (checkpoints) | 2 | 1 |
| In a browser (checkpoints) | 6 | 4 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 0 | 2 |
| Not tested (checkpoints) | 0 | 1 |
| Work done | 75% of the core | 75% of the core |
| API | Yes | Yes |
| OpenAPI | No | No |
| MCP server | No | Yes (official) |
| CLI | No | No |
| SDK | No | Yes |
| llms.txt | No | Yes |
Bot checks, and where a person was needed.
| Plausible Analytics | Umami | |
|---|---|---|
| Bot check | Friendly Captcha let it through at sign up | None met |
| Wall type | No bot-check wall | No bot-check wall |
| First wall | None | Got in, in a browser; the API is paid |
| A person helped | No | No |
Level and part scores.
| Plausible Analytics | Umami | |
|---|---|---|
| Level | L3 · Does the work | L3 · Does the work |
| Holds up | Not measured | 64 of 100, fair |
| Agent-ready setup | 30 of 100, poor | 75 of 100, fair |
| Standards | MCP client registration (current) | None recorded |
| Security | No review in this drive | Reported privately to the owner |
Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Plausible Analytics | Umami | |
|---|---|---|
| Pay | Payment not reached | Payment not tried |
| Free plan or trial | Trial, no card | Free plan |
| Cancel | Not needed | Not needed |
| Delete the account | In a browser | In a browser |
How each one takes payment
- Plausible Analytics: Payment not reached.
- Umami: Not tried yet: robots.txt keeps our agent off the payment page for now.
Plausible Analytics vs Umami: the short answers.
Which can an AI agent use, Plausible Analytics or Umami?
Both reach L3 · Does the work. Our agent got further with Plausible Analytics: with Plausible Analytics it got in on its own and did 75% of the work, with Umami it got in, in a browser (the API is paid). Driven 11 Oct 2026 (Plausible Analytics) and 8 Oct 2026 (Umami).
Can an AI agent sign up for Plausible Analytics and Umami on its own?
Plausible Analytics: yes, in a browser. Umami: yes, in a browser.
Do Plausible Analytics and Umami have an MCP server?
Plausible Analytics: none found. Umami: yes (official).
Can an AI agent delete its Plausible Analytics or Umami account?
Plausible Analytics: yes, in a browser. Umami: yes, in a browser.
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.