Is Umami agent-ready?

Umami scores Band C on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is API-first design intent; its weakest is MCP and agent posture.

Does Umami publish an OpenAPI spec?

No published OpenAPI specification was found when Umami was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.

What is Umami's Headless Index score?

Umami scores 49/100 on the Headless Index thesis-fit rubric and sits in Band C in the Analytics & Events category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / Analytics & Events

Umami

Headless Index

49/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

Umami earns Band C in the Analytics & Events category of The Headless Index, with a thesis-fit score of 49/100. Its strongest dimension is API-first design intent (15/20); its weakest scored dimension is MCP and agent posture (5/20). No public OpenAPI specification was found when Umami was scored, which limits how far an agent can go without human integration work.

Editorial verdict

Umami is partially headless and partly UI-led. The Headless Index thesis-fit score of 49/100 puts it mid-table on the index, and JAIRF is recorded as N/A for this vendor because no public OpenAPI specification was reachable for the open-source scorer. In practice, vendors at this tier are partly machine-consumable: the core flows are reachable through code but several adjacent surfaces still expect a human at a dashboard, and the rest of this verdict explains where Umami lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. The docs make an unusually strong claim and mostly keep it: any operation available in the application is available in the API. Cloud calls go to api.umami.is with an x-umami-api-key header; self-hosted instances mint a JWT at POST /api/auth/login. An agent can drive parts of this product, but not all of it: integrators should plan for human-in-the-loop checkpoints where the headless surface stops short. On headless operability: Self-hosting is the default posture and it is genuinely configuration-free: a Docker image, a Postgres or MySQL URL, an APP_SECRET. Websites, teams, users and share links are all CRUD over the API. The weak points are tooling maturity; @umami/cli sits at 0.2.0 with a two-line README (umami-software/cli), there is no Terraform provider, and board design is UI work.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Nothing. No MCP server under umami-software, no entry in the MCP registry, no mention of the protocol anywhere in the v3 docs sidebar. For a product whose entire value is answering questions about a dataset an agent already wants to query (umami-software/umami, 38k stars), that absence is the single largest gap on this scorecard. Shipping one would be straightforward.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Umami has no outbound webhooks at all. The v3 API reference lists admin, events, links, me, pixels, websites, statistics, realtime, reports, sessions, share, teams and users; nothing emits. /api/send is inbound collection only. An agent that needs to know a goal converted must poll the realtime group in the reference and diff results itself (umami.is/docs/api). That is a real cost for event-driven automation. Net assessment: integrators can build agent flows against Umami, but the rough edge to plan around is MCP posture^[3]. Expect to wrap missing pieces in bespoke glue or accept human-in-the-loop checkpoints. Workable but requires scaffolding.

Verdict by Headless Index pipeline (auto)

// AI-drafted from the evidence layer. Editorial review pending.

Scores

Scorecard detail

Headless Index · 5 sub-criteria

API-first design intent15/20

scored

The docs make an unusually strong claim and mostly keep it: any operation available in the application is available in the API. Cloud calls go to api.umami.is with an x-umami-api-key header; self-hosted instances mint a JWT at POST /api/auth/login. Two maintained clients exist (@umami/api-client 0.80.0, @umami/node 0.4.0), both thin and typed. Endpoint groups run from websites and sessions to reports, teams and pixels.

signals (5)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPI specNot found across 34 probe paths
−GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
+SDKs maintained3 (typescript); top by stars: umami-software/api-client (45 stars)
·npm weekly downloads1.1k across published packages; top: prisma-client @ 726/week

cite (1)

ai_review_browser.auth@2026-08-19

Headless operation14/20

scored

Self-hosting is the default posture and it is genuinely configuration-free: a Docker image, a Postgres or MySQL URL, an APP_SECRET. Websites, teams, users and share links are all CRUD over the API. The weak points are tooling maturity; @umami/cli sits at 0.2.0 with a two-line README (umami-software/cli), there is no Terraform provider, and board design is UI work.

signals (9)

+AI review appliedReviewer: Editorial review on 2026-08-19
−API operations exposedNo OpenAPI spec; operations count unknown
·Docs pages crawled0 pages (crawler: none)
·Auth schemes documentedAuth documentation page not reached by crawler
·Setup / quickstart docsNot reached by crawler
·Billing docsNot reached by crawler
·Teams / org docsNot reached by crawler
·CLI docsNot reached by crawler
·Schema / data model docsNot reached by crawler

cite (1)

ai_review_browser.topics_found@2026-08-19

MCP & agent posture5/20

scored

Nothing. No MCP server under umami-software, no entry in the MCP registry, no mention of the protocol anywhere in the v3 docs sidebar. For a product whose entire value is answering questions about a dataset an agent already wants to query (umami-software/umami, 38k stars), that absence is the single largest gap on this scorecard. Shipping one would be straightforward.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
−Official MCP serverNone found in vendor's GitHub org or the official MCP registry
−Community MCP serversNone found
+Agent-friendly SDKs3 TS/JS SDKs available; top: api-client (334/week downloads)

cite (1)

github.sdks@2026-08-19

Schema observability10/20

scored

No OpenAPI document is served (umami.is/docs/api/openapi.json redirects rather than resolving) and there is no GraphQL. An agent's real path is source: umami-software/types publishes the shared type definitions and @umami/api-client is typed end to end, so TypeScript users get a contract and everyone else reads the reference by hand. For an open source codebase this is a solved problem left unsolved.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPINot discovered across 34 standard probe paths
−GraphQL introspectionNo GraphQL endpoint discovered (5 probes; some vendors use project-scoped endpoints that require a real project handle)

cite (1)

github.sdks@2026-08-19

Webhooks & events5/20

scored

Umami has no outbound webhooks at all. The v3 API reference lists admin, events, links, me, pixels, websites, statistics, realtime, reports, sessions, share, teams and users; nothing emits. /api/send is inbound collection only. An agent that needs to know a goal converted must poll the realtime group in the reference and diff results itself (umami.is/docs/api). That is a real cost for event-driven automation.

signals (2)

+AI review appliedReviewer: Editorial review on 2026-08-19
·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.

cite (1)

github.sdks@2026-08-19

JAIRF · 6 dimensions

JAIRF · N/A

This vendor does not publish a public OpenAPI specification. JAIRF cannot be computed. The Headless Index score and editorial verdict carry the readiness assessment.

No public OpenAPI specification discovered during collection

Band rationale:C band: scores 40-75 range

04 / Embed

Show Umami's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Get embed code

Peers in Analytics & Events

RudderStackC

Headless Index 52/100

Plausible AnalyticsC

Headless Index 44/100

MixpanelC

Headless Index 56/100

See full Analytics & Events ranking →

FAQ

Umami and agent readiness

Is Umami agent-ready?: Umami scores Band C on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is API-first design intent; its weakest is MCP and agent posture.
Does Umami publish an OpenAPI spec?: No published OpenAPI specification was found when Umami was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is Umami's Headless Index score?: Umami scores 49/100 on the Headless Index thesis-fit rubric and sits in Band C in the Analytics & Events category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.