# Fathom Analytics: L1 · Needs a person As of 6 Oct 2026, an AI agent can't use Fathom Analytics on its own: Credit card required to sign up. Source: https://agentdrives.com/tools/usefathom?via=md · driven 6 Oct 2026 by AgentDrives's agent · 1 drive so far · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0 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. _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: 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 - Next: let an agent start without a card - With an account set up by a person: not measured yet. ## Part scores - Agent-ready setup: llms.txt found, OpenAPI found, MCP server found, CLI not found - Not measured in this drive: Holds up, Docs match ## Who gets in - Agents on a server: Can't 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 13 Oct 2026. Signed agents: the ones Cloudflare verifies. ## Checkpoints - **Docs**: Headless: llms.txt links a full Markdown API reference (/api/llms.txt) and an OpenAPI 3.1.0 schema (/api/openapi.json), all fetched headless. - **Sign up**: Blocked: app.usefathom.com/register is a browser-only form that requires a credit card (Stripe card field) and a ZIP code to start the 7-day trial; there is no free plan and no sign-up API. We may not enter a card, so the form could not be submitted. - **Verify**: Not reached: Not reached: sign-up could not be submitted without a card. - **Key**: Not reached: API tokens are created only in the web app (app.usefathom.com/api, 'Create new') after login; no OAuth, device flow or agent registration. - **First call**: Not reached: Without a token the API answers 401 {"message":"Unauthenticated."}. - **First action**: Not reached: No token, so no site could be created (POST /v1/sites). - **Pay**: Not reached: No 402 on the API (401 without token), no x402./mpp./agents. subdomains, no /.well-known/ucp, no x-payment-info in the OpenAPI, not listed in x402 Bazaar or mpp.dev. The trial and every plan start with a card on the sign-up form ('Choose a plan and add your card to start a 7-day free trial'), so a human must supply the card. API tier upgrades are self-serve in web billing settings, not by API. - **Cancel**: Not reached: No plan was started. Docs (/docs/account/close): cancel via Settings > Billing > Cancel in the web UI; no billing API. - **Delete**: Not reached: No account was created. Docs (/docs/account/close): after cancellation ends, sites and data are queued for deletion (up to 60 days); no account-delete API. DELETE /v1/sites/{id} exists for sites. ## Does Fathom Analytics have an MCP server, and can an agent connect to it? Not an official one. The drive found only third-party MCP servers for Fathom Analytics. The server runs on the agent's own machine. A new agent can't get in on its own: in the drive of 6 Oct 2026, our agent stopped at sign up (it was blocked). ## How does an AI agent get a Fathom Analytics API key? Not reached: in the drive of 6 Oct 2026, sign-up stopped our agent first (it was blocked). API tokens are created only in the web app (app.usefathom.com/api, 'Create new') after login; no OAuth, device flow or agent registration. ## Paying the agent way Payment not reached. Ways to pay it offers an agent: Card checkout. Its trial asks for a card. 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). - Let a trial start without a card: An agent can try the product before anyone hands it a card; take the card when it buys. From the drive of 6 Oct 2026. ## What an agent can do - Read the full API reference as Markdown (/api/llms.txt) and as OpenAPI 3.1.0 - Build a UTM-tagged campaign link with the free UTM builder (browser) - View Fathom's public demo dashboard (browser) ## What it cannot do - Create an account or start the trial: The sign-up form requires a credit card and ZIP code; no free plan - Get an API token and use the API (sites, events, milestones, reports): Tokens are made in the web app after sign-up - Any of the 9 core capabilities on our own site: No account ## Tips for the owner 1. Offer a no-card trial or free tier 2. Let agents get API tokens headlessly 3. Add an agent payment path 4. Publish an official remote MCP server 5. Match the 401 body to the docs 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 · [Fathom Analytics vs Plausible Analytics](https://agentdrives.com/compare/plausible-vs-usefathom?via=md) - [Umami](https://agentdrives.com/tools/umami.md?via=md): L3 · Does the work · [Fathom Analytics vs Umami](https://agentdrives.com/compare/umami-vs-usefathom?via=md) - [Pirsch](https://agentdrives.com/tools/pirsch.md?via=md): L1 · Needs a person · [Fathom Analytics vs Pirsch](https://agentdrives.com/compare/pirsch-vs-usefathom?via=md) ## Tips for agent builders - Read https://usefathom.com/api/llms.txt: the whole API in one Markdown file; OpenAPI 3.1.0 at /api/openapi.json - A human must sign up with a card and create a token at app.usefathom.com/api; then everything core (sites, events, milestones, aggregations) is plain REST with a Bearer token - Send Accept: application/json or errors come back as HTML; each API request counts toward the monthly pageview quota; 600 req/hour and 5 concurrent on the included tier - Branch on status codes: the 401 body differs from the docs ({"message":"Unauthenticated."})