Is Pirsch Analytics agent-ready?

Pirsch Analytics scores Band B on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is headless operation; its weakest is schema observability.

Does Pirsch Analytics publish an OpenAPI spec?

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

What is Pirsch Analytics's Headless Index score?

Pirsch Analytics scores 62/100 on the Headless Index thesis-fit rubric and sits in Band B 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

Pirsch Analytics

Headless Index

62/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

Pirsch Analytics earns Band B in the Analytics & Events category of The Headless Index, with a thesis-fit score of 62/100. Its strongest dimension is headless operation (16/20); its weakest scored dimension is schema observability (9/20). No public OpenAPI specification was found when Pirsch Analytics was scored, which limits how far an agent can go without human integration work.

Editorial verdict

Pirsch Analytics is solidly built for programmatic consumption. The Headless Index thesis-fit score of 62/100 lands it in the upper-middle of 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 ship most of the primitives agents need, with one or two surfaces still leaning on documentation rather than discovery, and the rest of this verdict explains where Pirsch Analytics lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Pirsch treats the API as the product surface rather than an export hatch. Auth is OAuth2 client credentials against POST https://api.pirsch.io/api/v1/token, with write-only access keys prefixed pa_ for tracking. An agent can drive this product across most practical workflows, with a handful of edges where documentation reading still beats schema discovery. On headless operability: The v1 endpoint list reads like the dashboard sitemap: domains, members and permissions, custom domains, access links, clients, email reports, webhooks, traffic filters, conversion goals, funnels, short links, views, organizations, themes, billing. Very little is UI-only. What is missing is the layer above: no CLI, no Terraform provider, and no self-hosted dashboard (pirsch-analytics/pirsch is a Go library, not the product).^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Pirsch documents an MCP server it did not write and says so plainly: @charpeni/pirsch-mcp is community-maintained and unsupported (docs.pirsch.io/integrations/mcp). Three tools, read-only, statistics only: pirsch_list_domains, pirsch_get_domain, pirsch_query_statistics. Write-only pa_ keys are explicitly rejected, so an OAuth client is required. Documenting a third-party server beats ignoring the protocol; it is still not a first-party one. The management half of the API stays out of agent reach.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Webhooks are real and, better, manageable over the API itself: GET and POST /api/v1/webhook with domain_id, description, event, endpoint and active fields. Delivery posts the custom event JSON on save, skipping bot-filtered hits. The semantics stop short though; there is no signature header to verify, no replay endpoint, and a webhook auto-disables after 100 failures (docs.pirsch.io/advanced/webhooks). Event names are yours, not a vendor catalogue. Net assessment: Pirsch Analytics can be operated by agents for the majority of practical workflows. The closest thing to a gap is schema observability^[3], which integrators should sanity-check against their own use case before committing. Strong fit for agent-driven use cases.

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

Pirsch treats the API as the product surface rather than an export hatch. Auth is OAuth2 client credentials against POST https://api.pirsch.io/api/v1/token, with write-only access keys prefixed pa_ for tracking. Official clients cover Go, PHP, Java and JavaScript (pirsch-sdk on npm, roughly 3.5k weekly downloads). The wobble is versioning: API v2 has been documented as unreleased work in progress.

signals (6)

+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 maintained4 (go, java, javascript, php); top by stars: pirsch-analytics/pirsch-js-sdk (27 stars)
+SDK recency1 of 4 SDK repos pushed within 30 days (most recent SDK commit: 2026-08-02)
·npm weekly downloads3.5k across published packages; top: pirsch-sdk @ 3.5k/week

cite (1)

ai_review_browser.auth@2026-08-19

Headless operation16/20

scored

The v1 endpoint list reads like the dashboard sitemap: domains, members and permissions, custom domains, access links, clients, email reports, webhooks, traffic filters, conversion goals, funnels, short links, views, organizations, themes, billing. Very little is UI-only. What is missing is the layer above: no CLI, no Terraform provider, and no self-hosted dashboard (pirsch-analytics/pirsch is a Go library, not the product).

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 posture10/20

scored

Pirsch documents an MCP server it did not write and says so plainly: @charpeni/pirsch-mcp is community-maintained and unsupported (docs.pirsch.io/integrations/mcp). Three tools, read-only, statistics only: pirsch_list_domains, pirsch_get_domain, pirsch_query_statistics. Write-only pa_ keys are explicitly rejected, so an OAuth client is required. Documenting a third-party server beats ignoring the protocol; it is still not a first-party one. The management half of the API stays out of agent reach.

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 SDKs1 TS/JS SDKs available; top: pirsch-sdk (3.5k/week downloads)

cite (1)

ai_review_browser.mcp@2026-08-19

Schema observability9/20

scored

No machine-readable spec exists; api.pirsch.io/openapi.json returns 404 and there is no GraphQL. The API v1 page gives a JSON request and response example for every endpoint, which is honest documentation and useless to a generator. The Go SDK types are the closest thing to a contract (pirsch-analytics/pirsch-go-sdk). An agent has to read prose first. Nothing here is fetchable cold.

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)

ai_review_browser.pages_fetched@2026-08-19

Webhooks & events12/20

scored

Webhooks are real and, better, manageable over the API itself: GET and POST /api/v1/webhook with domain_id, description, event, endpoint and active fields. Delivery posts the custom event JSON on save, skipping bot-filtered hits. The semantics stop short though; there is no signature header to verify, no replay endpoint, and a webhook auto-disables after 100 failures (docs.pirsch.io/advanced/webhooks). Event names are yours, not a vendor catalogue.

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)

ai_review_browser.webhooks@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:B band: JAIRF=N/A HeadlessIndex=62

04 / Embed

Show Pirsch Analytics'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

SnowplowB

Headless Index 64/100

HightouchB

Headless Index 64/100

TealiumC

Headless Index 58/100

See full Analytics & Events ranking →

FAQ

Pirsch Analytics and agent readiness

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