# AX Check: statsig.com Checked 2026-10-06. Statsig quickstart and pricing are clear, but llms.txt is missing 16 of 23 checks passed: install steps, code samples, and pricing are all stated plainly. No llms.txt index exists (404), so doc discovery relies on normal navigation. ## Onboarding needs a login ## Coding sessions All three independent sessions (DeepSeek V4.1 Flash, Kimi K3, Qwen 3.8 Max) completed and reported pricing accurately from the pricing page: a free tier up to 2M events/mo, Pro at $150/mo plus $0.05 per 1K events, and custom Enterprise pricing, with each flagging the same metered-events assumption. ### DeepSeek V4.1 Flash [View public run](https://agents.withgauge.com/p/runs/29cd0176-1304-4cf6-8860-f34f0b03e78d) · [Read transcript](https://www.ax-check.com/statsig.com/sessions/deepseek.json) Final output's pricing table (Developer free/2M events, Pro $150/mo+$0.05/1K events, Enterprise custom) is sourced from the fetched statsig.com/pricing page (seq 20, 29, 138) with the event-based metering assumption named explicitly. #### End-to-end onboarding - **Onboarding needs a login**: Agent searched the sandbox for any Statsig credentials/env vars and found none. It never created a Statsig account or obtained a real Server Secret Key during the session. It ran the hosted code path with a fabricated fake key purely to observe the failure mode, which returned HTTP 401. The only 'successful' run used localMode + bootstrapValues (an offline, no-network fixture), which is explicitly a local mock and does not touch the hosted product, so it cannot establish onboarding. Event 5: ```text env | grep -iE 'statsig|STATSIG' || echo "no statsig env vars" ``` Event 6: ```text no statsig env vars --- no package.json ``` Event 137: ```text StatsigInitializeFromNetworkError: statsigSDK::initialize> Failed to initialize from the network: Request to https://api.statsigcdn.com/v1/download_config_specs/secret-fake-n****.json failed with status 401. ``` Event 132: ```text mode : OFFLINE (localMode + bootstrapValues) init : success=true source=Bootstrap ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No Statsig Server Secret Key available in the sandbox**: The environment had no STATSIG_SERVER_SECRET or any Statsig credential, and the agent has no self-service way to sign up for a Statsig account from the sandbox. This is a missing-credentials limitation of the test environment, not a product defect: a real user would simply log in to the Statsig Console and copy a key. The agent demonstrated the failure mode by running the hosted code path with a deliberately fake key, which the hosted API correctly rejected with 401, confirming the real API was reachable and behaving as expected. Event 21: ```text find / -maxdepth 4 \( -iname '*statsig*' -o -iname '*.env' \) 2>/dev/null | grep -v proc | head -20; echo "--- secrets dirs ---"; ls -la ~/.config 2>/dev/null; ls -la /run/secrets 2>/dev/null; echo "done" ``` Event 137: ```text Request to https://api.statsigcdn.com/v1/download_config_specs/secret-fake-n****.json failed with status 401 ``` #### Suggested Changes - **Add a working npm quickstart doc page for the Node server SDK**: The agent's curl check against docs.statsig.com/server/node and docs.statsig.com/quickstart both returned HTTP 404, forcing it to reverse-engineer the API from the npm package's bundled TypeScript declarations and test fixtures instead of official docs. Fix the links (or add redirects) so docs.statsig.com/server/node and /quickstart resolve, and verify by curling those exact paths and confirming a 200 with setup instructions. Event 39: ```text === https://docs.statsig.com/server/node === HTTP 404 === https://docs.statsig.com/quickstart === HTTP 404 === https://docs.statsig.com/server/introduction === HTTP 200 ``` ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/7a8c2a56-feda-4620-8a42-d5f69c3b4a67) · [Read transcript](https://www.ax-check.com/statsig.com/sessions/kimi.json) Final output states free tier limits (~1M events/mo), Pro tier (~$150/mo scaling with events), Enterprise custom pricing, and flags the assumption that feature-flag-only usage is free while analytics volume drives cost. #### End-to-end onboarding - **Onboarding needs a login**: The agent wrote a working Node.js script using the statsig-node SDK but could not obtain a Statsig server secret key itself, since key creation requires interactive signup/login on the Statsig web console. It never authenticated against the hosted product or ran a real authenticated operation; the script exits immediately with an error asking for a human-supplied key. Event 21: ```text every SDK call requires a Server Secret Key (or client SDK key) from `https://console.statsig.com`, which requires an interactive account signup I can't complete ``` Event 19: ```text Set STATSIG_SERVER_SECRET to your Statsig server secret key. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-service way to get a Statsig API key**: Statsig requires an account/API key created through the web console before any SDK call can succeed. The agent could not sign up or generate a key on its own, so the example script could not be executed against the real hosted product. This is a product/environment constraint (interactive signup requirement), not an agent mistake. Event 21: ```text Statsig has no anonymous/test mode — every SDK call requires a Server Secret Key (or client SDK key) from `https://console.statsig.com`, which requires an interactive account signup I can't complete. ``` #### Suggested Changes - **Offer a disposable/sandbox API key for quickstart testing**: The Statsig quickstart (console.statsig.com) currently gates every SDK call behind an interactively-created Server Secret Key. Providing a trial or sandbox key generation path (e.g., via CLI or public demo endpoint) would let developers run the official SDK examples end-to-end without manual console signup. Verify by having a fresh agent/environment run the statsig-node quickstart script and confirm a live checkGate/getConfig/logEvent call succeeds without a human pasting credentials. Event 21: ```text every SDK call requires a Server Secret Key (or client SDK key) from `https://console.statsig.com`, which requires an interactive account signup I can't complete ``` ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/3ce64ef0-7b38-4289-a5b9-47fe5820c784) · [Read transcript](https://www.ax-check.com/statsig.com/sessions/qwen.json) Final output gives a pricing table (Developer free/2M events, Pro $150/mo+$0.05/1K, Enterprise custom) sourced from statsig.com/pricing and explicitly names the metered-events-vs-unlimited-checks assumption and the event-dimension billing quirk. #### End-to-end onboarding - **Onboarding needs a login**: No real Statsig credentials existed in the sandbox. Agent probed the hosted API with a fake key (got a 403 RBAC rejection, not success) then built and ran the example entirely in the SDK's offline localMode using local override values instead of live data. It verified the live code path only with an invalid key (success=false, gates fell back to defaults) - this is not an authenticated operation. Agent explicitly states account creation and key retrieval require human interactive signup it cannot perform. Event 12: ```text timeout 25 curl -s https://api.statsig.com/v1/rulesets -H "STATSIG-SERVER-SECRET: secret-invalid-test" -w "\nHTTP:%{http_code}\n" | tail -3 ``` Event 57: ```text init OK. details: {"duration":33,"success":true} gate demo_gate = true config = {"color":"blue","maxItems":7} shutdown ok ``` Event 104: ```text Creating the account and copying a secret key is a human step — signup requires the console UI. Everything after that works. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No Statsig account credentials available in the sandbox**: Environment had zero Statsig secret keys (env scan returned nothing Statsig-related), and creating a real account/key requires interactive console signup that the agent cannot perform. This is a credentials/environment limitation, not a product defect — agent correctly flagged it as a normal login requirement rather than a bug. Event 5: ```text env | grep -iE 'statsig|feature|flag' ; echo "--- env keys count:"; env | wc -l ``` Event 104: ```text Creating the account and copying a secret key is a human step — signup requires the console UI. ``` - **Initial npm package name guess was wrong**: Agent first tried installing a package called statsig-node-core, which has no published versions, causing an install failure. This was an agent error (guessing a package name) quickly self-corrected by querying the npm registry for real candidates and landing on statsig-node v6.5.2. Event 19: ```text npm error code ENOVERSIONS npm error No versions available for statsig-node-core ``` - **statsig-node SDK export shape required trial and error**: Agent's first attempt to call Statsig.initialize() failed because the package exports a flat object plus a default export, not a Statsig namespace directly. Caused a TypeError before the agent inspected the module shape and corrected the destructuring. Event 52: ```text ERR: TypeError Cannot read properties of undefined (reading 'initialize') ``` #### Suggested Changes - **Clarify the correct current Node SDK package name in quickstart docs**: Agent initially tried installing 'statsig-node-core', which has no published versions on npm, before discovering 'statsig-node' v6.5.2 is the real current server SDK via a manual registry query. Check by looking at whatever quickstart or getting-started page recommends a package name and confirm it matches what npm registry shows today for both package names. Event 19: ```text npm error code ENOVERSIONS npm error No versions available for statsig-node-core ``` Event 24: ```text == statsig-node latest: 6.5.2 | deprecated? None ``` - **Document the statsig-node module export shape in SDK reference**: Agent had to read TypeScript definition files and experiment at the REPL to learn that require('statsig-node') returns a flat object with a 'default' property rather than a top-level Statsig object, causing an initial TypeError. Add a short snippet to the server SDK reference page showing the correct require/destructure pattern and confirm it matches the actual package.json main export. Event 52: ```text ERR: TypeError Cannot read properties of undefined (reading 'initialize') ``` Event 56: ```text const sdk=require('statsig-node'); const Statsig=sdk.default||sdk.Statsig; ``` ### Task given to each agent Help me build a simple example using Statsig. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop. No product credentials were supplied and no purchases were authorized. ## Score: B · 65/100 (provisional) Grades come from completed site checks. Coding sessions and skipped checks do not affect the score. ### Clarity - **Failed** — Homepage answers Markdown requests ```text Homepage returned text/html for a text/markdown Accept header; no Markdown representation served. ``` - **Failed** — llms.txt provides an actionable documentation index ```text https://statsig.com/llms.txt returns 404, so no documentation index exists. ``` - **Skipped** — llms.txt provides navigation guidance ```text No llms.txt body exists (404), so navigation guidance cannot be evaluated. ``` - **Skipped** — llms.txt mentions offered API, MCP, and skills ```text No llms.txt body exists (404), so API/MCP/skills mentions cannot be evaluated. ``` - **Pass** — A compact guide representation exists ```text Docs pages serve text/markdown; quickstart available as .md and via Accept: text/markdown. ``` - **Pass** — A focused guide is directly retrievable ```text SDK quickstart fetched as markdown with concrete React, JS, Python, Node install steps. ``` - **Pass** — Equivalent instructions fit a token budget ```text Quickstart markdown ~3073 tokens, well under 8000 and below HTML extraction size. ``` - **Skipped** — Product-docs links survive format changes ```text Homepage Markdown unsupported, so link preservation across formats cannot be measured. ``` - **Pass** — The compact guide is independently actionable ```text Quickstart gives concrete install, key setup, and gate/experiment/event steps for React, JS, Python, Node. ``` - **Pass** — Install and next-step links resolve ```text Fetched quickstart and API overview pages returned 200 with working install and next-step links. ``` ### Onboarding - **Pass** — Docs lead to a relevant quickstart ```text SDK Quickstart gives concrete React, JS, Python, Node install-and-run steps with next steps. ``` - **Pass** — Installation commands are extractable ```text Extractable install commands: npm install @statsig/react-bindings, pip install statsig-python-core, npm i @statsig/statsig-node-core. ``` - **Pass** — Code examples are available without interaction ```text Quickstart shows inline code examples for gates, experiments and events without interaction. ``` - **Pass** — Prerequisites and auth boundaries are explicit ```text Quickstart states client key and server secret key, linking console Settings to create them. ``` ### Pricing - **Pass** — Pricing is readable without interaction ```text Pricing page renders full plan tiers, prices and feature comparison without any interaction. ``` - **Pass** — Prices are stated, not gated ```text Free, Pro $150/mo, and Enterprise Custom prices are stated openly on the page. ``` - **Pass** — Pricing units and limits are explicit ```text Units explicit: 2M events/mo free, 5M events then $0.05 per 1K, replay limits. ``` - **Pass** — Agents identify pricing and its assumptions ```text 3 of 3 sessions were judged on pricing; 0 fell short. DeepSeek V4.1 Flash: Final output's pricing table (Developer free/2M events, Pro $150/mo+$0.05/1K events, Enterprise custom) is sourced from the fetched statsig.com/pricing page (seq 20, 29, 138) with the event-based metering assumption named explicitly. Kimi K3: Final output states free tier limits (~1M events/mo), Pro tier (~$150/mo scaling with events), Enterprise custom pricing, and flags the assumption that feature-flag-only usage is free while analytics volume drives cost. Qwen 3.8 Max: Final output gives a pricing table (Developer free/2M events, Pro $150/mo+$0.05/1K, Enterprise custom) sourced from statsig.com/pricing and explicitly names the metered-events-vs-unlimited-checks assumption and the event-dimension billing quirk. This behavioural item does not affect the fast grade. ``` ### Activation - **Pass** — An API reference or OpenAPI spec is reachable ```text Console API overview documents base URL, auth, and links an OpenAPI spec at api.statsig.com. ``` - **Skipped** — An MCP server is documented and well-formed ```text No MCP server documentation appears in the fetched Statsig documents. ``` - **Pass** — A CLI install path is documented ```text Docs sidebar lists Statsig CLI Overview, Commands, and Gate Management pages. ``` - **Pass** — SDK packages resolve on their registries ```text npm @statsig/react-bindings, @statsig/statsig-node-core, and PyPI statsig-python-core all returned HTTP 200. ``` - **Skipped** — Agent skills are published ```text No agent skills publication is present in the fetched Statsig documents. ``` [Full report data](https://www.ax-check.com/statsig.com/report.json)