Head to head · Analytics events · October 2026 research run
Heap vs Statsig
Statsig scores 72.3 (BB) on agent readiness against Heap's 53 (D), and leads in every scored category. Both do analytics events.
Which one, for what
Heap D
Good for An agent that records backend events or enriches user and account properties in a company's existing Heap project, or that files privacy deletions.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No query, export or definitions endpoint in the developer reference. Reading results needs the app, Heap Connect or the MCP server we couldn't read
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
- Reliability, 79 against 72
- Schema & documentation, 82 against 57
- Agent ergonomics, 71 against 49
- Security & auth, 74 against 41
- Payments & pricing, 40 against 25
- Maintenance & community, 81 against 63
- Transparency & trust, 75 against 64
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
Watch for
Console API errors carry only status and message, and the spec documents no 429 response
Score by category
| Category | Weight this run | Heap | Statsig | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 72 | 79 | Statsig +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 57 | 82 | Statsig +25 |
| Agent ergonomics | 13%16.2 | 49 | 71 | Statsig +22 |
| Security & auth | 14%17.5 | 41 | 74 | Statsig +33 |
| Payments & pricing | 10%12.5 | 25 | 40 | Statsig +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 63 | 81 | Statsig +18 |
| Transparency & trust | 7%8.8 | 64 | 75 | Statsig +11 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 53 · D | 72.3 · BB |
Facts side by side
| Fact | Heap | Statsig |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Contentsquare (Content Square, Inc.) | Amplitude, Inc. |
| Hosted endpoint | https://heapanalytics.com | https://api.statsig.com/v3/mcp |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| Price for analytics events | not published | $0.0001 per transaction |
| x402 | no | no |
| Licence | Proprietary service under Contentsquare's master services agreement. The React Native bridge and the Node client on npm are MIT | Proprietary hosted service under Statsig's self-service or enterprise terms. The SDKs and the agent skills repository on GitHub are ISC |
| Tools exposed | none | 18 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | com.statsig/statsig-mcp-server |
| Last release | 2026-10-06 | 2026-09-28 |
| Terms last updated | no date given | 2025-08-04 |
| Privacy policy last updated | couldn't be read | 2026-08-31 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 213 npm/wk | 4.2M npm/wk, 894k PyPI/wk |
Verdicts
Heap
Heap's server-side API suits an agent that records events. Limits are published, bulk calls take 1,000 items and track accepts an idempotency key. The API returns no analytics, and ingest calls carry no secret beyond the environment ID. Heap's help centre lists a Heap MCP article, which a bot check stopped us reading, so the MCP server is ungraded.
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
Heap
- Send EU projects to https://c.eu.heap-api.com instead of https://heapanalytics.com. The path stays the same
- Pass one of
identityoruser_idon track, never both - Set
idempotency_keyon every track event so a retry doesn't duplicate it - Stay under 30 requests per 30 seconds per identity, or batch up to 1,000 events in one bulk call
- For deletion, exchange the app_id and API key of the Main Production environment for a token first. Any other environment ID returns Unauthorized
Statsig
- Connect to https://api.statsig.com/v3/mcp. The official MCP registry entry still lists the V1 URL, which has 93 tools
- Call
get_contextfirst to learn the project, your permissions and the review settings - Read the resource before
gate_update,experiment_updateordynamic_config_update. They replace the whole resource, so resend every field you want kept - Use
discover_toolsfor partial edits, and fetch a freshoperationHandlewhen one expires - 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, Heap or Statsig?
Statsig scores 72.3 (BB) on agent readiness against Heap's 53 (D), and leads in every scored category.
Do Heap and Statsig need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Heap and Statsig without installing anything?
Yes. Heap has a hosted endpoint at https://heapanalytics.com and Statsig at https://api.statsig.com/v3/mcp.
Other comparisons with Heap or Statsig
Machine-readable
- This page as Markdown
/compare/heap-vs-statsig.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/heap.json·/api/v1/tools/statsig.json - From a terminal
anchor compare heap statsig(the CLI) - Over MCP
compare_tools {"a": "heap", "b": "statsig"}at/mcp, no key