# Pirsch: L1 · Needs a person

As of 12 Oct 2026, an AI agent can't use Pirsch on its own: ALTCHA checkbox on the sign-up form.

Source: https://agentdrives.com/tools/pirsch?via=md · driven 12 Oct 2026 by AgentDrives's agent · Same level in 2 drives in a row · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0

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.

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

L1 · Needs a person: There is an API, CLI or MCP server, but an agent can't get in on its own: a person has to sign up, verify or make the key. What it does once a person sets it up shows next to the level.

- 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
- Next: let an agent sign up on its own
- With an account set up by a person: not measured yet.

## Level history

- 6 Oct 2026: L1 · Needs a person
- 12 Oct 2026: L1 · Needs a person

## Part scores

- Agent-ready setup: llms.txt not found, OpenAPI not found, MCP server found, CLI not found
- Not measured in this drive: Holds up, Docs match

## Who gets in

- Agents on a server: Stopped by a CAPTCHA on the sign-up form.
- Signed agents: The sign-up page opens. The CAPTCHA on the form stops them too.
- Agents in a person's browser: Not measured yet.

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

## Checkpoints

- **Docs**: Headless: Public docs at docs.pirsch.io: API v1 reference (~150 REST endpoints) and API guide, fetched headless. No OpenAPI file, no llms.txt, no Markdown versions of pages.
- **Sign up**: Needs a human: Sign-up is a web form at pirsch.io/signup with an ALTCHA 'I'm not a robot' checkbox. The agent does not tick a bot check itself. No sign-up API is documented.
- **Verify**: Not reached: Not reached: sign-up stopped at the ALTCHA checkbox.
- **Key**: Not reached: Not reached. OAuth clients and access keys are made in the dashboard or with POST /api/v1/client, both need an account.
- **First call**: Not reached: Not reached. Without a client, GET /api/v1/billing answers 401 'the token is not a valid bearer token'.
- **First action**: Not reached: Not reached: no account.
- **Pay**: Not reached: No 402, x402, MPP or registry listing; we paid nothing. docs.pirsch.io/billing: plans are bought on a Stripe checkout page; the 30-day trial needs no card. GET /api/v1/billing only reads usage. Not reached in the drive: no account.
- **Cancel**: Not reached: Not tested: Pirsch has recurring paid plans and none was started (no account reached past the sign-up wall). Docs: change or cancel in the Stripe portal; marking the account for deletion cancels the subscription.
- **Delete**: Not reached: No account to delete. Docs: DELETE /api/v1/user/account deletes the account after a one-week grace period (needs an account-level client).

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

Not an official one. The drive found only third-party MCP servers for Pirsch. The server runs on the agent's own machine and lists 3 tools.

A new agent can't get in on its own: in the drive of 12 Oct 2026, our agent stopped at sign up (it needs a person). Through the MCP server, 1 of our agent's 1 attempt worked.

## How does an AI agent get a Pirsch API key?

Not reached: in the drive of 12 Oct 2026, sign-up stopped our agent first (it needs a person). Not reached. OAuth clients and access keys are made in the dashboard or with POST /api/v1/client, both need an account.

## Paying the agent way

Payment not reached.

No card needed to start.

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 12 Oct 2026.

## What an agent can do

- Read the full API v1 reference and guide without an account
- Install and list the tools of the docs-linked MCP server

## What it cannot do

- Create an account: The sign-up form has an ALTCHA 'I'm not a robot' checkbox and there is no sign-up API
- Get API credentials, send page views or events, read statistics: Every one needs an account and a client made after sign-up

## Tips for the owner

1. Let signed agents past the bot check on sign-up: Skip the CAPTCHA for signed agents (valid Web Bot Auth signature), or offer a documented sign-up API.
2. Add a documented sign-up route for agents
3. Publish an OpenAPI file and llms.txt
4. Serve Markdown docs pages
5. Accept an agent payment rail on the API

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

## Tips for agent builders

- Sign-up needs a person to tick the ALTCHA box; after that everything is in the REST API v1 at api.pirsch.io/api/v1
- Use an oAuth client (POST /api/v1/token) to read statistics; pa_ access keys are write-only (hits, events, sessions)
- Rate limit headers are X-RateLimit-*; login/security endpoints allow 10 requests a minute
- The MCP server @charpeni/pirsch-mcp is third-party, stdio and read-only