Fullstory vs Userpilot

Fullstory 81

Closed service under a published master services agreement (20 May 2026), with the skills repository and Node SDK under MIT (15). The DPA gives 30 days to retrieve data after termination and deletion within six months. The free plan keeps 12 months of data. The MSA lets Fullstory use data that doesn't identify the customer to improve the service, and the free plan terms add model training on de-identified data (24). A breaking-changes page says such changes ship as a new major version. No notice period or end date for v1 was found (8). Sub-processor list updated 2 June 2026 with locations, Google in the United States and Germany, and no location given for OpenAI, which is marked optional (18). Total 65.

Userpilot 59

A closed service with terms dated 23 April 2024 (15 of 30). The privacy policy of 11 March 2025 names a DPO and two sub-processors (AWS and Cloudflare), while the security page names AWS, Google Cloud and Stripe. The DPA is on request and no customer-data retention period is stated (14 of 30). No deprecation policy or dated API notices found (3 of 20). Sub-processors are named with addresses but not data locations, though an EU ingestion endpoint exists (10 of 20). 15+14+3+10 = 42.

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.

Userpilot 82

Graded on the hosted service with the hosted lines. Better Stack status page at status.userpilot.io with components for ingestion in three regions, the SDKs, the web application APIs and the website (20). From August to November 2026 the page shows only scheduled maintenance windows of two to four hours, with no incidents; the MCP server isn't a component (30). 600 requests a minute per token for the real-time APIs, but no numbers for MCP or export (12 of 15). 429 documented with exponential backoff guidance; no Retry-After or idempotency guidance (10 of 15). The SLA is a custom Enterprise contract term, not published (0). The MCP server is 1.0.0 in the registry with no beta label (10). 20+30+12+10+0+10 = 82.

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.

Userpilot 60

The tool count isn't published; the docs say the assistant can search hundreds of extra read-only operations on demand, which reads as dynamic loading. Without the list we give the middle band (15 of 25). Export jobs filter by date range, users, events and segments, and job lists paginate (14 of 20). A documented error reference (13 of 20). No deletes or admin through MCP by design; annotations weren't readable and no idempotency keys were found (10 of 20). The HTTP APIs have no official server-side SDK; client SDKs for web and six mobile frameworks (8 of 15). 15+14+13+10+8 = 60.

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.

Userpilot 71

Every API reference page embeds an OpenAPI 3.0 definition, though no standalone spec file was found (20 of 25). llms.txt and Markdown versions of every page (10). Endpoint pages state their purpose and the MCP docs say what each permission allows; the MCP tool definitions weren't read because that needs a session (12 of 20). Request bodies are typed, mostly as strings and string arrays with few enums (9 of 15). An error reference covers 400, 401, 422 and 429 with causes, and pages carry examples (12 of 15). /v1 paths and dated SDK release notes; no API changelog was found (8 of 15). 20+10+12+9+12+8 = 71.

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.

Userpilot 79

io.userpilot/mcp 1.0.0 was published to the registry on 11 October 2026 (30). The iOS SDK alone has dated releases on 6 August, 2 September, 27 September and 2 October 2026 (20). A closed service with no public API changelog, support by email and chat (8 of 25). Verified io.userpilot namespace in the official MCP registry (15). Client SDKs are current; there is nothing else public to inspect (6 of 10). 30+20+8+15+6 = 79.

Fullstory 25

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.

Userpilot 30

No x402, MPP or L402 (0). Plan prices are public ($299 and from $849 a month), with no per-unit prices (10). 14-day free trial with no card required (20). Signup and OAuth approval happen in a browser (0). 0+10+20+0 = 30.