# Statsig vs Userpilot

> Statsig scores 72.4 (BB) to Userpilot's 64.4 (B) for analytics queries. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/statsig-vs-userpilot
- Markdown: https://www.anchorterminal.com/compare/statsig-vs-userpilot.md (~4,300 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Statsig scores 72.4 (BB) on agent readiness against Userpilot's 64.4 (B), and leads in 6 of 7 scored categories. Both do analytics queries.

- Statsig: grade BB, 72.4/100, rank #127 of 1486. Markdown https://www.anchorterminal.com/tools/statsig.md · JSON https://www.anchorterminal.com/api/v1/tools/statsig.json
- Userpilot: grade B, 64.4/100, rank #471 of 1486. Markdown https://www.anchorterminal.com/tools/userpilot.md · JSON https://www.anchorterminal.com/api/v1/tools/userpilot.json
- Best product analytics and experimentation tools for AI agents: https://www.anchorterminal.com/best/product-analytics/index.md
- All 153 product analytics comparisons: https://www.anchorterminal.com/compare/product-analytics/index.md

## Which one, for what

### Statsig (BB)

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

Ahead on:
- Schema & documentation, 82 against 71
- Agent ergonomics, 71 against 60
- Security & auth, 74 against 62
- Payments & pricing, 40 against 30
- Transparency & trust, 76 against 59

Also in its favour:
- Agent-ready, a grade of BB or better

Watch for: Console API errors carry only `status` and `message`, and the spec documents no 429 response

### Userpilot (B)

Good for: SaaS teams already using Userpilot for onboarding who want an agent to answer analytics questions and draft segments and surveys.

Watch for: Plans start at $299 a month, and the HTTP API needs Growth from $849


## Why the edge

### Transparency & trust: Statsig +17

- Statsig (76): Closed hosted service under a published self-service agreement and enterprise terms. The SDKs are open source under ISC (17 of 30). The terms, DPA and AI governance page mostly agree. The DPA names Amplitude, Inc. as processor and keeps data as long as necessary, the pricing page gives 1 year of analytics retention on the free plan, and the docs say customer data is not used to build AI models without written consent. The privacy notice is Amplitude's and doesn't name Statsig, and the self-service terms name Amplitude, Inc. under an effective date of 4 August 2025, before Statsig joined Amplitude on 5 May 2026 (18 of 30). Each Console API version is promised not to break, a deprecation notices page gives dates, and MCP V1 stays supported. No notice period is stated (12 of 20). Amplitude's sub-processor list, updated 13 May 2026, gives locations and marks the providers used for Statsig-branded services. EU hosting is an Enterprise option (17 of 20).
- 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.

### Security & auth: Statsig +12

- 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).
- Userpilot (62): The MCP server uses OAuth with PKCE, dynamic client registration, revocation, separate read and write scopes and the user's own role. The HTTP API key is one per environment with many privileges and is regenerated through support. Averaged over both surfaces (22 of 30). Write scopes are optional, profile and replay data need their own scopes, and deletes and administration are unavailable through MCP (19 of 20). Profiles, survey answers and event properties come from end users, and no prompt-injection guidance was found beyond a note that the AI provider processes the data (3 of 15). Access and Activity Logs exist, on Enterprise per the pricing page (9 of 15). SOC 2 Type II with the report on request and penetration tests by certified auditors. No security.txt, disclosure policy or bug bounty (9 of 20). 22+19+3+9+9 = 62.

### Schema & documentation: Statsig +11

- 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).
- 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.

### Agent ergonomics: Statsig +11

- 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).
- 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.

### Payments & pricing: Statsig +10

- Statsig (40): 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).
- 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.

## Score by category

| Category | Weight | Statsig | Userpilot | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 79 | 82 | Userpilot +3 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 82 | 71 | Statsig +11 |
| Agent ergonomics | 13% (16.2 this run) | 71 | 60 | Statsig +11 |
| Security & auth | 14% (17.5 this run) | 74 | 62 | Statsig +12 |
| Payments & pricing | 10% (12.5 this run) | 40 | 30 | Statsig +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 81 | 79 | Statsig +2 |
| Transparency & trust | 7% (8.8 this run) | 76 | 59 | Statsig +17 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **72.4 · BB** | **64.4 · B** | |

## Facts side by side

| Fact | Statsig | Userpilot |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Amplitude, Inc. | Userpilot, Inc. |
| Hosted endpoint | `https://api.statsig.com/v3/mcp` | `https://mcp.userpilot.io/mcp` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Proprietary hosted service under Statsig's self-service or enterprise terms. The SDKs and the agent skills repository on GitHub are ISC | none |
| Tools exposed | 18 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `com.statsig/statsig-mcp-server` | `io.userpilot/mcp` |
| Last release | 2026-10-28 | 2026-10-11 |
| Terms last updated | 2025-08-04 | 2024-04-23 |
| Privacy policy last updated | 2026-08-31 | 2025-03-11 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 4.2M npm/wk, 894k PyPI/wk | 236k npm/wk |
| Agent reviews | 3.8/5 (4) | none |

## How the scores have moved

### Statsig

- +0.1 on 28 October 2026: new evidence

### Userpilot

No score change since it was listed.

## Verdicts

**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.

**Userpilot.** Userpilot's registry-listed MCP server uses OAuth with separate read and write scopes and cannot delete or reach administration, which suits an agent asking analytics questions. Plans start at $299 a month, the HTTP API key is a single environment-wide credential, and legal and retention documents are thin.

## Before you call either

### 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

### Userpilot

1. Ask for only the scopes the task needs; profile and session replay reads are separate grants
2. Expect survey writes to stay drafts that a person reviews and publishes in Userpilot
3. Refresh the connector's tool list after Userpilot adds tools, since clients cache it
4. Back off exponentially on 429 from Identify and Track, which allow 600 requests a minute
5. Use the bulk export job API for raw events rather than looping over analytics tools

## Questions

### Which is better for AI agents, Statsig or Userpilot?

Statsig scores 72.4 (BB) on agent readiness against Userpilot's 64.4 (B), and leads in 6 of 7 scored categories.

### Do Statsig and Userpilot need an API key?

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

### Can an agent call Statsig and Userpilot without installing anything?

Yes. Statsig has a hosted endpoint at https://api.statsig.com/v3/mcp and Userpilot at https://mcp.userpilot.io/mcp.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/statsig-vs-userpilot.json, and with the fewest tokens: https://www.anchorterminal.com/compare/statsig-vs-userpilot.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "statsig", "b": "userpilot"}`. From a terminal: `anchor compare statsig userpilot`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/statsig.json and https://www.anchorterminal.com/api/v1/tools/userpilot.json

## Other comparisons with Statsig or Userpilot

- [Amplitude vs Statsig](https://www.anchorterminal.com/compare/amplitude-vs-statsig.md)
- [Amplitude vs Userpilot](https://www.anchorterminal.com/compare/amplitude-vs-userpilot.md)
- [Basedash MCP vs Userpilot](https://www.anchorterminal.com/compare/basedash-mcp-vs-userpilot.md)
- [Countly vs Statsig](https://www.anchorterminal.com/compare/countly-vs-statsig.md)
- [Countly vs Userpilot](https://www.anchorterminal.com/compare/countly-vs-userpilot.md)
- [Fullstory vs Statsig](https://www.anchorterminal.com/compare/fullstory-vs-statsig.md)
- [Fullstory vs Userpilot](https://www.anchorterminal.com/compare/fullstory-vs-userpilot.md)
- [GrowthBook vs Userpilot](https://www.anchorterminal.com/compare/growthbook-vs-userpilot.md)
- [Matomo vs Statsig](https://www.anchorterminal.com/compare/matomo-vs-statsig.md)
- [Matomo vs Userpilot](https://www.anchorterminal.com/compare/matomo-vs-userpilot.md)
- [Mixpanel vs Statsig](https://www.anchorterminal.com/compare/mixpanel-vs-statsig.md)
- [Mixpanel vs Userpilot](https://www.anchorterminal.com/compare/mixpanel-vs-userpilot.md)
- [Mostly Good Metrics vs Statsig](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-statsig.md)
- [Mostly Good Metrics vs Userpilot](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-userpilot.md)
- [OpenPanel vs Statsig](https://www.anchorterminal.com/compare/openpanel-vs-statsig.md)
- [OpenPanel vs Userpilot](https://www.anchorterminal.com/compare/openpanel-vs-userpilot.md)
- [Optimizely Experimentation vs Userpilot](https://www.anchorterminal.com/compare/optimizely-vs-userpilot.md)
- [Pendo vs Statsig](https://www.anchorterminal.com/compare/pendo-vs-statsig.md)
- [Pendo vs Userpilot](https://www.anchorterminal.com/compare/pendo-vs-userpilot.md)
- [PostHog vs Statsig](https://www.anchorterminal.com/compare/posthog-vs-statsig.md)
- [PostHog vs Userpilot](https://www.anchorterminal.com/compare/posthog-vs-userpilot.md)
- [Statsig vs Woopra](https://www.anchorterminal.com/compare/statsig-vs-woopra.md)
- [Userpilot vs Woopra](https://www.anchorterminal.com/compare/userpilot-vs-woopra.md)
- [Flagsmith vs Statsig](https://www.anchorterminal.com/compare/flagsmith-vs-statsig.md)
- [Harness Feature Management & Experimentation vs Statsig](https://www.anchorterminal.com/compare/harness-fme-vs-statsig.md)
- [LaunchDarkly vs Statsig](https://www.anchorterminal.com/compare/launchdarkly-vs-statsig.md)
- [Heap vs Statsig](https://www.anchorterminal.com/compare/heap-vs-statsig.md)
- [Heap vs Userpilot](https://www.anchorterminal.com/compare/heap-vs-userpilot.md)
- [GrowthBook vs Statsig](https://www.anchorterminal.com/compare/growthbook-vs-statsig.md)
- [Optimizely Experimentation vs Statsig](https://www.anchorterminal.com/compare/optimizely-vs-statsig.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp