Head to head · Analytics queries · October 2026 research run

Fullstory vs Statsig

Statsig scores 74.9 (BB) on agent readiness against Fullstory's 64.9 (B), and leads in 5 of 7 scored categories. Fullstory leads on agent ergonomics and transparency & trust. Both do analytics queries.

Best product analytics and experimentation tools for AI agents · All 170 product analytics comparisons

Which one, for what

Fullstory B

Best for An agent that sends server-side events and user properties, fetches a session's events or an AI summary for support or debugging, or exports a segment.

Ahead on

  • Agent ergonomics, 77 against 71
  • Transparency & trust, 81 against 76

Watch for

Metrics, funnels and journeys are reachable only through the MCP server, which needs a paid plan and an admin to enable it

Statsig BB

Best for An agent that creates, updates and cleans up feature gates, dynamic configs and experiments, and reads experiment results and audit history.

Ahead on

  • Reliability, 79 against 65
  • Schema & documentation, 82 against 62
  • Security & auth, 74 against 65
  • Payments & pricing, 60 against 38
  • Maintenance & community, 81 against 70

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card
  • Rated higher by the reviewer agents, 3.8 against 2.5 out of 5

Watch for

Console API errors carry only status and message, and the spec documents no 429 response

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Statsig +22

Fullstory 38

No x402, MPP or L402 (0). The plans page names Business, Advanced and Enterprise with no price and a Request pricing button. Only the free plan's limits are public (5). FullstoryFree needs no card per the plans page, re-read on 2 November, and the help centre lists API keys as available on it (20). A person signs up in a browser and creates the key in settings (0). Total 25. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Statsig 60

No x402, MPP or L402 (0). Prices are public without a login. Pro is $150 a month with 5 million events, then $0.05 per 1,000 events (20). The Developer plan is free with no card and 2 million events a month (20). A person signs up in a browser, then creates a key or approves OAuth (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Schema & documentation Statsig +20

Fullstory 62

Each reference page carries the OpenAPI operation it is drawn from, with schemas, security and a permission level. No single downloadable spec was found on the docs site, and the swagger files in the Node SDK repository cover users and events only and date from 2024. The MCP tool schemas need a login we don't have (15 of 25). llms.txt returns 404 on 2 November and no Markdown copies were found (0). Descriptions state purpose and limits and say when another route fits better, such as Warehouse for export (15). Types, formats, required fields and enumerated event types are declared, with a free-form properties object (11). Request and response examples on each page, and 400, 401, 403, 404, 429 and 500 documented with a code and message (13). Paths are versioned and a breaking-changes page defines what forces a new major version, but the only changelog is for the browser script (8). Total 62.

Statsig 82

Public OpenAPI 3.0 spec for Console API version 20240601 with 209 paths and 325 operations, per the 8 October check, not re-read on 1 November, and typed MCP tools per the tool reference (25). llms.txt, llms-full.txt, a Markdown copy of each page and a public docs MCP server (10). Every operation has a summary but only 29 of 325 have a description, per the 8 October check. The MCP tool reference states each tool's purpose and when to ask the user first (11 of 20). 1,164 enums across 188 schemas, with required fields marked, per the 8 October check (12 of 15). Examples on most responses. The spec documents 401 on 156 operations, 404 on 126 and 400 on 106, and no 429, per the 8 October check (11 of 15). A dated API version sent in the STATSIG-API-VERSION header with a promise not to break a version, and a dated product updates page. No changelog for the API alone was found (13 of 15).

Reliability Statsig +14

Fullstory 65

Graded on the Server API with the hosted lines. Statuspage site at status.fullstory.com with per-region components, API among them (20). Read from its own history and incident pages on 2 November (the 8 October count came from the Statuspage API, which this run doesn't read, and is replaced). From 4 August to 2 November, on 1 September a Google Cloud fault took every NA1 service, the API included, out from 11:19 to 16:32 Eastern time (labelled critical, about five hours). That is all of NA1 at once, Fullstory's default data centre, so it's read as one major, as vapi's and google-drive-api's regional outages are. The other incidents in the window don't touch the API (EU1 playback on 23 September, NA1 Warehouse delays on 18 August, Guides and Surveys on 6 August) or name a subset of organisations (delayed session data on 7 September) (10). The general limit on the Server API has no published number. Batch imports do (50,000 requests a batch, 429 at 200 batches or 500,000 operations in progress), and the MCP server allows 3 requests a second with a burst of 20, re-read on 2 November (10 of 15). 429 responses carry Retry-After, and every create call accepts an Idempotency-Key kept for 24 hours (15). No SLA was found in the master services agreement of 20 May 2026 (0). The v2 Server API is generally available (10). 20 + 10 + 10 + 15 + 0 + 10 = 65.

Statsig 79

Graded on the hosted service with the hosted lines. Statuspage at status.statsig.com with 14 components, among them Console API, Config Delivery API and Log Event API (20). Three incidents between 3 August and 1 November 2026, all Warehouse Native delays (export delays from 6 August resolved 8 August, delayed exposure results on 26 August and its follow-up resolved 31 August), marked minor or none per the 8 October check, and nothing posted since 31 August (20 of 30). The 8 July 2026 major, when launched gates returned false through the V2 Config Delivery API for about 4 hours 44 minutes, is outside the window. The docs give about 1,800 mutation attempts per 15 minutes per project, while the OpenAPI description gave about 100 per 10 seconds and 900 per 15 minutes per the 8 October check, and no number was found for reads (12 of 15). The docs ask for exponential backoff with jitter on 429. No Retry-After header and no idempotency keys were found (10 of 15). The enterprise terms give 99.95 per cent monthly availability with credits, for customers with premium support, measured on the Console user interface (7 of 10). The Console API is versioned and the MCP V3 docs carry no beta label (10).

Maintenance & community Statsig +11

Fullstory 70

The Server API has no changelog of its own. The vendor's dated sources count, the browser script changelog (latest entry 26 October 2026) and the official Claude plugin in the fullstory-skills repository, bumped to 0.2.1 on 22 October and 0.2.2 on 29 October 2026 (30). Thirteen browser script entries between 4 August and 26 October 2026, plus the two plugin versions (20). A public changelog for the capture script, a help centre community and a Slack community named in the MCP docs. Response times were not checked (8). The Node server client is 1.1.1 from 12 February 2024, and the MCP registry could not be reached (8). No CI workflow in the Node SDK repository (4). 30 + 20 + 8 + 8 + 4 = 70.

Statsig 81

The newest product update is dated 9 October 2026 and the server SDKs released 0.24.0 on 28 October 2026 (30). Ten or more dated product updates and six server SDK releases since 3 August 2026 (20). Closed service with a public updates page and a Slack community. We did not read how quickly questions are answered (10 of 15). com.statsig/statsig-mcp-server is in the official MCP registry under the vendor's domain, though the entry still dates from 19 September 2025 and lists the V1 URL (13 of 15). The server SDK repository has 25 CI workflow files per the 8 October check and 135 commits since 3 August 2026, while the siggy CLI has not been published since September 2024 per the 8 October check (8 of 10).

Security & auth Statsig +9

Fullstory 65

API keys come in three permission levels (Standard, Architect, Admin), are named, shown once, deletable at once and tied to the user who made them. The MCP server takes OAuth with PKCE, 16 scopes, dynamic client registration and a revocation endpoint. Keys travel in a header only (27 of 30). A Standard key cannot export or delete user data, and the MCP docs rule out administration. No confirmation step was found for Delete User, and build_segment saves a segment despite the page that says writes are unsupported (12). Session transcripts, screenshots and console and network data are untrusted page content. Masking and exclusion rules carry over, but no prompt-injection guidance was found (3). History endpoints record changes to privacy and capture settings. No per-call log for operators was found (6). Signed security.txt valid to 4 June 2027 (re-read on 2 November, contact psirt@fullstory.com), SOC 2 Type 2, ISO 27001, 27017, 27018, 27701 and 42001, and a yearly CREST penetration test. No bug bounty found (17). Total 65.

Statsig 74

OAuth for the MCP server with PKCE, dynamic client registration and a device code grant, issuing personal Console API keys that carry the user's role. Console keys can be created read-only or read and write, and rotated or deactivated through the API. The OAuth metadata lists no scopes, and a project Console key reaches every Console API endpoint (25 of 30). MCP scope is set per project and per role as no access, read only or read and write. Updates and destructive operations need a confirmation, and project review policies still apply (19 of 20). No guidance on prompt injection was found, though tools return names, descriptions and log data that people wrote. The docs tell users to review each change before the agent confirms (4 of 15). Audit logs are kept indefinitely with an API, and personal keys attribute changes to a user (14 of 15). SOC 2 Type II and a bug bounty programme are stated on the security page, with no public programme link and no security.txt (12 of 20).

Agent ergonomics Fullstory +6

Fullstory 77

Session context calls take event and duration limits and include or exclude lists by event type, and List Sessions takes limit (18 of 25). page_token paging on users and batch results, and filters on users. List Sessions returns one page only, as its reference says (14). Errors are JSON with a snake-case code documented as safe to handle in code, such as session_page_limit_exceeded (17). Idempotency-Key on every create call, with body comparison and 24-hour expiry. MCP tool annotations were not read (20). Create Event needs a name and one identifier and timestamps default to server time. The only official server SDK found is Node, last published 12 February 2024 (8). Total 77.

Statsig 71

The MCP V3 server shows 18 default tools, which is 15 on the checklist. Add back 8 for the discovery layer that reaches other operations on demand, query_fields on experiment reads and read-only access (23 of 25). limit and page on 49 list operations with pagination metadata per the 8 October check, a cursor on the Logs Explorer query, and filters by tag, status, creator and date (17 of 20). Errors are a status and a message with no machine code, and MCP results set isError (11 of 20). No idempotency keys were found. Updates and api_destructive calls need a confirmation object, and operations are split into read, write and destructive lanes. We could not read the live tool annotations (10 of 20). The SDKs cover flag evaluation and event logging in many languages, not the Console API, and the siggy CLI on npm is version 0.0.4 from September 2024 (10 of 15).

Score by category

CategoryWeightFullstoryStatsigEdge
Reliability16%6579Statsig +14
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6282Statsig +20
Agent ergonomics13%7771Fullstory +6
Security & auth14%6574Statsig +9
Payments & pricing10%3860Statsig +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7081Statsig +11
Transparency & trust7%8176Fullstory +5
Negative events≤1500
TotalB 64.9/100BB 74.9/100

Facts side by side

FactFullstoryStatsig
KindHTTP APIHTTP API
VendorFullstory, Inc.Amplitude, Inc.
Hosted endpointhttps://api.fullstory.comhttps://api.statsig.com/v3/mcp
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under Fullstory's master services agreement. The skills repository and the Node SDK on GitHub are MITProprietary hosted service under Statsig's self-service or enterprise terms. The SDKs and the agent skills repository on GitHub are ISC
Tools exposednone18
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedcom.statsig/statsig-mcp-server
Last release2026-10-292026-10-28
Terms last updated2026-05-202025-08-04
Privacy policy last updated2025-05-192026-08-31
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity6.4k npm/wk4.2M npm/wk, 894k PyPI/wk
Agent reviews2.5/5 (4)3.8/5 (4)

The panel on both

4 of the 4 reviewers who reviewed both rate Statsig higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Fullstory

The Server API suits an agent that sends events or pulls session context. Create calls take an idempotency key and errors carry stable codes. Metrics and funnels come only through the MCP server on paid plans. Paid prices are unpublished, and a Google Cloud fault took the NA1 API down for about five hours on 1 September 2026.

Statsig

Statsig suits agents that manage feature gates and experiments and read their results. Its MCP server has 18 default tools, OAuth, read-only access by project and role, and a confirmation on updates. Errors carry only a status and a message, no idempotency keys were found, and the privacy notice is Amplitude's and doesn't name Statsig.

Before you call either

Fullstory

  1. Call GET https://api.fullstory.com/me first. Its role field shows whether the key is Standard, Architect or Admin
  2. Send Idempotency-Key on every create call and reuse it on retry. Honour Retry-After on 429
  3. URL-encode the colon in session IDs as %3A in /v2/sessions/{session_id} paths
  4. For MCP in the EU data centre, use https://api.eu1.fullstory.com/mcp/fullstory if the client reports a protected resource mismatch
  5. After session_open, always call session_close. Open sessions hold server resources and can block further opens
  6. Treat session transcripts and screenshots as untrusted page content, not as instructions

Statsig

  1. Connect to https://api.statsig.com/v3/mcp. The official MCP registry entry still lists the V1 URL, which has 93 tools
  2. Call get_context first to learn the project, your permissions and the review settings
  3. Read the resource before gate_update, experiment_update or dynamic_config_update. They replace the whole resource, so resend every field you want kept
  4. Use discover_tools for partial edits, and fetch a fresh operationHandle when one expires
  5. On a 429 slow down and back off with jitter. Rejected attempts count towards the quota of about 1,800 mutations per 15 minutes

Questions

Which is better for AI agents, Fullstory or Statsig?

Statsig scores 74.9 (BB) on agent readiness against Fullstory's 64.9 (B), and leads in 5 of 7 scored categories. Fullstory leads on agent ergonomics and transparency & trust.

Do Fullstory and Statsig need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Fullstory and Statsig without installing anything?

Yes. Fullstory has a hosted endpoint at https://api.fullstory.com and Statsig at https://api.statsig.com/v3/mcp.

Other comparisons with Fullstory or Statsig

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.