◎ Discry Score
mixpanel.com
analytics · API
C
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 92 (A)
Discry your API →
ANALYTICS · RANK #15 OF 29

Mixpanel is Needs Work to agents.

Discry independently scored how well an AI agent can discover and understand the Mixpanel API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.

Discry your API — freeView the docs ↗

SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.

Discovery

45% of score · 52/100
OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Fail
llms.txtAn llms.txt index that points agents to the docs that matter.Pass
llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Partial
llms-full.txtA full-text bundle agents can load in one request.Fail
AGENTS.mdAn AGENTS.md that tells coding agents how to build on the API.Pass
.well-known/mcp.jsonA discoverable MCP manifest at a well-known path.Fail
MCP registryThe API is listed in a public MCP registry.Pass
robots.txt AI directivesrobots.txt allows (or explicitly guides) AI crawlers.Pass
SitemapA sitemap so agents can enumerate the docs surface.Fail

Comprehension

55% of score · 85/100
Task-oriented descriptionsEndpoints described by what they accomplish, not just their shape.Pass
Realistic examplesRunnable, real-world request/response examples.Pass
Multi-step workflowsDocs that chain calls into complete jobs an agent can follow.Partial
Error-recovery guidanceDocumented failure modes and how to recover from them.Pass
Answer-first formatThe answer leads; preamble does not bury it.Pass
Capability boundariesClear limits — what the API can and cannot do.Pass
Naming consistencyConsistent, predictable naming across endpoints.Partial
Heading hierarchyClean heading structure agents can navigate.Pass
Markdown docsDocs available as clean markdown, not JS-rendered HTML only.Pass
Token efficiencyDocs are concise enough to fit an agent context window.Partial

What we found

  • An agent searching MCP registries would find Mixpanel immediately — it has an official MCP server on PulseMCP and multiple community servers on Glama and Smithery.
  • An agent encountering import errors would get exceptionally detailed recovery guidance including per-field validation errors, explicit backoff strategies with timing, and clear 'do not retry 400s' instructions.
  • An agent using the llms.txt would find a well-organized API reference index with .md-linked endpoint descriptions, though it lacks deeper contextual sections beyond the link list.
  • An agent looking for the OpenAPI spec would fail — despite ReadMe-hosted docs (which typically support OpenAPI), no public spec URL is accessible.
  • Mixpanel has invested in AI-agent infrastructure with AGENTS.md files in multiple SDK repos (Flutter, Android), signaling awareness of agentic development patterns.

What to change

Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.

  1. 01Publish the OpenAPI spec at a stable public URL (e.g., developer.mixpanel.com/openapi.json) — this would add 5 weight points to discovery score immediately.
  2. 02Add llms-full.txt with comprehensive API usage patterns covering the track/import/export/query workflow end-to-end.
  3. 03Expand llms.txt from a link list into structured sections with descriptions of API capabilities, authentication patterns, and common workflows.
  4. 04Create a sitemap.xml at developer.mixpanel.com listing all API reference pages for better crawler coverage.
  5. 05Add multi-step workflow guides in docs showing complete integration patterns: setup project -> configure auth -> import historical data -> query results -> set up live tracking.

Execution coverage · INFORMATIONAL, UNSCORED

Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.

Project TokenService Account (Basic Auth)OAuth✓ Error format documented✓ Rate limits documented✓ Pagination documented✓ Idempotency documented

Strong execution documentation. Rate limits documented (2GB/min, ~30k events/s). Error responses include field-level validation details with $insert_id references. Idempotency via $insert_id deduplication. Multiple auth methods with clear role requirements.

See your own Discry Score.

Drop your API docs URL. See what an agent sees — in 60 seconds, free.

Discry your API — free