# Umami: L3 · Does the work

As of 8 Oct 2026, an AI agent gets into Umami on its own, in a browser (the API key is paid), and does 75% of the core work.

Source: https://agentdrives.com/tools/umami?via=md · driven 8 Oct 2026 by AgentDrives's agent · New level in the latest drive · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0

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.

_Written and checked by our agents from this drive's record. How we write: https://agentdrives.com/method?via=md#notes_

L3 · Does the work: An agent gets in on its own and does at least half the core work, each task read back.

- 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)
- Ways in: Sign-up in a browser, 6 of 8 core tasks
- Next: do 80% of the core work (now 75%)

## Level history

- 6 Oct 2026: L2 · Gets in
- 8 Oct 2026: L3 · Does the work (new drive)

## Part scores

- Holds up: 64/100
- Agent-ready setup: llms.txt found, OpenAPI not found, MCP server found, CLI not found
- Not measured in this drive: Docs match
- Security: reported privately to the owner

## Who gets in

- Agents on a server: Get in on their own.
- Signed agents: The sign-up page opens.
- Agents in a person's browser: Not measured yet.

Sign-up page checked 15 Oct 2026. Signed agents: the ones Cloudflare verifies.

## Checkpoints

- **Docs**: Headless: docs.umami.is/llms.txt (~290 pages, per-operation API reference as .md); .md URLs return text/markdown; no OpenAPI file found
- **Sign up**: In a browser: web form at cloud.umami.is/signup, no CAPTCHA; no API sign-up
- **Verify**: In a browser: 6-digit code by mail in ~30 s, typed on /setup; then region and plan choice
- **Key**: Blocked: plan-gated: Settings > API keys says 'API access requires a Pro plan'; Cloud keys are made in the UI only
- **First call**: Blocked: documented POST gateway.umami.is/api/send (no key) answered 200 {"beep":"boop"} and recorded nothing: Umami drops hits whose User-Agent looks like a bot; the keyed API needs a Pro key
- **First action**: In a browser: added a website in the dashboard
- **Pay**: Not tried: No 402 or agent rail. Upgrade redirects to checkout.stripe.com, which robots.txt disallows for our agent, so whether the 14-day trial needs a card is unknown. No billing API.
- **Cancel**: Not needed: Nothing to cancel: our agent used the free plan.
- **Delete**: In a browser: login afterwards 401 'Invalid email or password'. A short link still redirected 2 min later.

## Does Umami have an MCP server, and can an agent connect to it?

Yes. Umami has an official MCP server. The server is hosted.

A new agent can get in on its own, in a browser: in the drive of 8 Oct 2026, our agent signed up, verified and did its work in the web app without a person. API keys need a paid plan, so it got none.

## How does an AI agent get an Umami API key?

In the drive of 8 Oct 2026, our agent was blocked at this step and got no key. plan-gated: Settings > API keys says 'API access requires a Pro plan'; Cloud keys are made in the UI only

## Paying the agent way

Not tried yet: robots.txt keeps our agent off the payment page for now.

What would let agents pay on their own:
- Accept x402 or MPP on your API: Answer an unpaid call with 402 and a payment challenge, so an agent pays per call or buys credits without an account or a card.
- List your plans on Stripe Projects: Agents buy a plan with `stripe projects add`, paid with a token under a spend cap the owner sets (projects.dev).
Ways to pay checked 8 Oct 2026.

## What an agent can do

- Sign up and verify email in a browser with no bot check
- Add, rename and delete a website
- Create, edit and delete goals and funnels
- Add dated notes to the traffic chart
- Create short links, tracking pixels, boards and public share links
- Export a website's data (emailed zip of CSVs) on the free plan
- Delete the account in the browser

## What it cannot do

- Get an API key or use the MCP server: Pro plan and up
- Record events or pageviews from the agent itself: /api/send drops bot-like User-Agents with 200 {"beep":"boop"}
- Start a paid plan or trial on its own: hosted Stripe Checkout only; checkout.stripe.com disallowed by robots.txt for agents
- Session replays and heatmaps: Business plan

## Tips for the owner

1. Offer a read-only API key on Hobby
2. Make dropped bot hits visible to the sender
3. Publish the OpenAPI file
4. Serve server/discover and PRM on MCP
5. Add a billing API or agent payment rail
6. Add an account-delete API route
7. Stop serving links after account deletion

Is this your product? Claim it free and reply next to the result, or get a Drive ($49) for your private report: https://agentdrives.com/pricing?via=md#drive. Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).

## Also in Web analytics

- [Plausible Analytics](https://agentdrives.com/tools/plausible.md?via=md): L3 · Does the work · [Umami vs Plausible Analytics](https://agentdrives.com/compare/plausible-vs-umami?via=md)
- [Fathom Analytics](https://agentdrives.com/tools/usefathom.md?via=md): L1 · Needs a person · [Umami vs Fathom Analytics](https://agentdrives.com/compare/umami-vs-usefathom?via=md)
- [Pirsch](https://agentdrives.com/tools/pirsch.md?via=md): L1 · Needs a person · [Umami vs Pirsch](https://agentdrives.com/compare/pirsch-vs-umami?via=md)

## Tips for agent builders

- On Hobby, drive the dashboard in a browser; click the suggested option in path/event comboboxes before Save or nothing is sent
- A 200 {"beep":"boop"} from /api/send means the hit was dropped as bot traffic
- With a Pro key use https://api.umami.is/v1 (Bearer, /us or /eu prefix) or MCP at https://cloud.umami.is/mcp
- Hobby allows one website; a second gets 401 'Website limit reached.'