Is FullStory agent-ready?

FullStory 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 MCP and agent posture; its weakest is webhooks and events.

Does FullStory publish an OpenAPI spec?

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

What is FullStory's Headless Index score?

FullStory 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

FullStory

Headless Index

62/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

FullStory earns Band B in the Analytics & Events category of The Headless Index, with a thesis-fit score of 62/100. Its strongest dimension is MCP and agent posture (17/20); its weakest scored dimension is webhooks and events (7/20). No public OpenAPI specification was found when FullStory was scored, which limits how far an agent can go without human integration work.

Editorial verdict

FullStory 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 FullStory lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Server API V2 is a proper product surface: POST /v2/users, /v2/users/batch, /v2/events and /v2/events/batch on api.fullstory.com, with documented idempotency keys and job-polling for asynchronous work. Auth is an API key whose first three characters encode the data region, na1 or eu1. 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: Fullstory does the unglamorous parts well. Data export runs headless through hauser, a scheduled Go fetcher, warehouse output is modelled in dbt (github.com/fullstorydev/dbt_fullstory), and the cloud relay ships as real infrastructure code for both AWS and Google. Segment definitions, funnels and most privacy rules still start in the UI, though Subtext now exposes capture rules to an agent.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: The most agent-native vendor in this batch by some distance. A hosted MCP endpoint answers at api.fullstory.com/mcp/fullstory, a Claude and Cursor plugin ships the wiring plus session-review and general-analysis skills (github.com/fullstorydev/fullstory-skills), and Subtext is a whole second product built for coding agents. The one deduction: the MCP server sits behind a beta programme, so access is not open.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Consumption is pull-based. Export bundles are listed and downloaded on a schedule, which is exactly why hauser (github.com/fullstorydev/hauser) exists as a supported tool. The docs publish no outbound webhook catalogue; /server/v2/webhooks/ returns 404, and there is no signing header, delivery retry or replay window described anywhere. Agents get freshness measured in export intervals, not seconds. Net assessment: FullStory can be operated by agents for the majority of practical workflows. The closest thing to a gap is webhooks and events^[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 intent16/20

scored

Server API V2 is a proper product surface: POST /v2/users, /v2/users/batch, /v2/events and /v2/events/batch on api.fullstory.com, with documented idempotency keys and job-polling for asynchronous work. Auth is an API key whose first three characters encode the data region, na1 or eu1. Clients cover both sides (@fullstory/server-api-client, @fullstory/browser, fullstory-flutter, a Swift package). The crawler found none of this because the org is named fullstorydev.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPI specNot found across 0 probe paths
−GraphQL endpointNot discovered (0 probes; project-scoped endpoints require a real project ID)
−SDKs maintainedNone detected in vendor org

cite (1)

github.sdks@2026-08-19

Headless operation14/20

scored

Fullstory does the unglamorous parts well. Data export runs headless through hauser, a scheduled Go fetcher, warehouse output is modelled in dbt (github.com/fullstorydev/dbt_fullstory), and the cloud relay ships as real infrastructure code for both AWS and Google. Segment definitions, funnels and most privacy rules still start in the UI, though Subtext now exposes capture rules to an agent.

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

scored

The most agent-native vendor in this batch by some distance. A hosted MCP endpoint answers at api.fullstory.com/mcp/fullstory, a Claude and Cursor plugin ships the wiring plus session-review and general-analysis skills (github.com/fullstorydev/fullstory-skills), and Subtext is a whole second product built for coding agents. The one deduction: the MCP server sits behind a beta programme, so access is not open.

signals (2)

+AI review appliedReviewer: Editorial review on 2026-08-19
·MCP detector statusTimed out during collection (likely GitHub search API rate limit without GITHUB_TOKEN). No verified evidence about MCP presence.

cite (1)

ai_review_browser.mcp@2026-08-19

Schema observability8/20

scored

This is the weak seam. No machine-fetchable contract exists; probes for a spec on developer.fullstory.com and api.fullstory.com (openapi.json, openapi.yaml) return 404, there is no GraphQL, and no spec file sits in the public repos. Reference pages give JSON samples and prose, so a client is written by hand or inferred from @fullstory/server-api-client. Odd for a vendor this invested in agents.

signals (2)

+AI review appliedReviewer: Editorial review on 2026-08-19
·Collector statusOpenAPI and GraphQL probes did not record any attempts

cite (1)

ai_review_browser.pages_fetched@2026-08-19

Webhooks & events7/20

scored

Consumption is pull-based. Export bundles are listed and downloaded on a schedule, which is exactly why hauser (github.com/fullstorydev/hauser) exists as a supported tool. The docs publish no outbound webhook catalogue; /server/v2/webhooks/ returns 404, and there is no signing header, delivery retry or replay window described anywhere. Agents get freshness measured in export intervals, not seconds.

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.pages_fetched@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 FullStory'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

Pirsch AnalyticsB

Headless Index 62/100

SnowplowB

Headless Index 64/100

HightouchB

Headless Index 64/100

See full Analytics & Events ranking →

FAQ

FullStory and agent readiness

Is FullStory agent-ready?: FullStory 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 MCP and agent posture; its weakest is webhooks and events.
Does FullStory publish an OpenAPI spec?: No published OpenAPI specification was found when FullStory was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is FullStory's Headless Index score?: FullStory 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.