# Mixpanel: L3 · Does the work As of 6 Oct 2026, an AI agent gets into Mixpanel on its own and does 50% of the core work. Source: https://agentdrives.com/tools/mixpanel?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 Gets in on its own: L3 · Does the work. Sign-up is a browser form with no CAPTCHA, but the first credential, a service account, only exists in the web UI, and so does the key for the project token. From there our agent ran ingestion, raw export, feature flags, experiments, Lexicon and boards headless through the official MCP server, with each task read back. Every analysis query returned a payment-required response on the free plan, and upgrading asked for a card in a checkout form. Deleting the organization is a web button, and the confirmation mail says data clears after a wait, so our agent could not confirm the account was gone before the drive ended. _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: Docs for agents (llms.txt, an OpenAPI and an MCP server) - Access: Sign-up in a browser - Use: 50% of the work - Pay: Reaches the checkout (Stopped at the card form) - Leave: Nothing to cancel (Can't delete its account) - Ways in: Sign-up in a browser, 2 of 4 core tasks - Next: do 80% of the core work (now 50%) ## 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: 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 12 Oct 2026. Signed agents: the ones Cloudflare verifies. ## Checkpoints - **Docs**: Headless: docs.mixpanel.com/llms.txt (65 KB) lists every page as .md and 14 OpenAPI specs; Accept: text/markdown returns markdown; docs MCP at docs.mixpanel.com/mcp speaks 28 Jul 2026. - **Sign up**: In a browser: No sign-up API or agent registration. Web form at /register/ (email + terms), then a 3-question onboarding and an organization form; no CAPTCHA met. - **Verify**: In a browser: Magic-link mail arrived within a minute; the link opens a 'Log in to Mixpanel' page with a Log In button. - **Key**: In a browser: First credential needs the web UI: service account (secret shown once) in Project Settings > Service Accounts, project token in Project Settings. MCP OAuth needs a browser consent page (DCR only, no device flow). The GDPR API needs a separate personal token generated in the UI. - **First call**: Headless: GET /api/app/me with service-account basic auth -> 200. - **First action**: Headless: POST api.mixpanel.com/import -> num_records_imported 6, read back by the export API. - **Pay**: In a browser: No x402/MPP/L402 (subdomains do not resolve, Query API 402 carries no payment header, not in Bazaar or mpp.dev). Growth costs $0.00 for the first 1M events but asks for a card ('Why is a credit card required if my plan costs $0?'). No billing API or MCP billing tool. Stopped at the card form. - **Cancel**: Not needed: Nothing to cancel: our agent used the free plan. - **Delete**: Blocked: No delete API exists (14 OpenAPI specs and docs MCP search confirm this is UI-only). Settings > Org > Delete Organization > Submit queues deletion, with a confirmation mail saying data is deleted after 90 days. Right after submitting, the service account still got 200 from /api/app/me and the export API still returned the ingested events: login/API access was not rejected during the drive, so deletion cannot be confirmed as done. ## Does Mixpanel have an MCP server, and can an agent connect to it? Yes. Mixpanel has an official MCP server. The server lists 66 tools and speaks the older 25 Nov 2025 MCP spec. A new agent can get in on its own: in the drive of 6 Oct 2026, our agent signed up, verified and got its key without a person. Through the MCP server, 2 of our agent's 5 attempts worked. ## How does an AI agent get a Mixpanel API key? In the drive of 6 Oct 2026, our agent got its Mixpanel API key in a browser, without a person. First credential needs the web UI: service account (secret shown once) in Project Settings > Service Accounts, project token in Project Settings. MCP OAuth needs a browser consent page (DCR only, no device flow). The GDPR API needs a separate personal token generated in the UI. ## Paying the agent way Reaches the checkout: stopped at the card form. Ways to pay it offers an agent: Stripe card form (card checkout); Card checkout. It has a free plan. 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). From the drive of 6 Oct 2026. ## What an agent can do - Send events and user profiles with the Ingestion API and read them back with the raw export API - Create, enable, target by user property, evaluate and delete feature flags over the documented API - Create, launch and delete an experiment over the API (results need variants, metrics and exposure data) - Document events and properties in Lexicon over the Schemas API and read them back via MCP - Create, read and delete a board via the MCP server with a service account - File a GDPR deletion request over the API with a GDPR token it generated in the web UI ## What it cannot do - Sign up, verify or get a first API credential headless: Web form + magic link; service accounts and tokens are created in the web UI only - Run Insights, Funnels, Retention or any Query API call on the free plan: HTTP 402 'Your plan does not allow API calls'; MCP query tools return the same - Save a cohort on the free plan: 'plan does not allow saving cohorts' - Upgrade without a human card: Stripe card form required even for the $0 Growth plan; no agent payment rail - Delete the account headless: Delete Organization is a web UI button; deletion runs 90 days later ## Tips for the owner 1. Allow a small Query API quota on free 2. Let an agent get its first credential headless 3. Move the MCP server to the 28 Jul 2026 spec 4. Add CIMD or device flow to MCP OAuth 5. Document cohort_definition and validate experiment launch 6. Offer an API to delete an organization 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 Product analytics - [Amplitude](https://agentdrives.com/tools/amplitude.md?via=md): L1 · Needs a person · [Mixpanel vs Amplitude](https://agentdrives.com/compare/amplitude-vs-mixpanel?via=md) - [Heap](https://agentdrives.com/tools/heap.md?via=md): L1 · Needs a person · [Mixpanel vs Heap](https://agentdrives.com/compare/heap-vs-mixpanel?via=md) - [PostHog](https://agentdrives.com/tools/posthog.md?via=md): L1 · Needs a person · [Mixpanel vs PostHog](https://agentdrives.com/compare/mixpanel-vs-posthog?via=md) ## Tips for agent builders - Create a service account in the web UI (Project Settings > Service Accounts, role Admin); it works for REST (basic auth) and for MCP as 'Authorization: Bearer Basic '. - Ingestion /import needs time, distinct_id and $insert_id; with strict=1 errors name the failing field. - On the free plan every Query API and MCP query tool returns 402: ingest, export, flags, experiments, lexicon and boards still work. - MCP tool schemas are opaque objects: call Get-Query-Schema / Describe-Cohort-Schema first and expect to learn field names from validation errors. - Flag evaluation (api.mixpanel.com/flags) needs the project token as basic auth and can take 1-2 minutes to reflect a change; disable a flag before deleting it. - The GDPR API takes only a personal GDPR token from Profile > Data & Privacy, not a service account.