statsig.com valid
Statsig Documentation
Official documentation for Statsig feature flags, experimentation, analytics, Warehouse Native, SDKs, APIs, and AI products.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T03:36:01.114Z. Cached copy · Source on statsig.com
# Statsig Documentation
> Official documentation for Statsig feature flags, experimentation, analytics, Warehouse Native, SDKs, APIs, and AI products.
Statsig Feature Gates are feature flags. Statsig Cloud processes hosted event data; Warehouse Native runs analysis against data in the customer's warehouse.
Use Docs MCP for targeted, read-only public documentation retrieval. Authenticated Statsig MCP accesses product resources according to the user's account permissions.
Prefer current SDKs for new implementations. Verify plan requirements, lifecycle status, and availability on the linked live page before making recommendations.
AI Experimentation is Early Access and is not accepting new customers. Use Docs MCP or `/api/content/<slug>` for targeted retrieval; use `llms-full.txt` only as an offline full-corpus resource.
## Start here
- [Statsig Overview](https://docs.statsig.com/api/content/welcome): Ship, measure, & learn with the same tools as the world's largest Tech companies. Run thousands of A/B tests, safely rollout features, & dive deep on user behavior in a single, unified platform.
- [Platform Overview](https://docs.statsig.com/api/content/understanding-platform): Learn what Statsig is used for and how to set it up with our Cloud and Warehouse Native deployment models Deployment: Both.
- [Statsig SDK Quickstart Guide](https://docs.statsig.com/api/content/sdks/quickstart): Get data flowing into Statsig with only a few lines of code.
- [Create your first feature flag](https://docs.statsig.com/api/content/guides/check-gate): How to call checkGate in Statsig client and server SDKs to evaluate a feature gate, including parameters, return values, and exposure logging.
- [Create an Experiment](https://docs.statsig.com/api/content/experiments/create-new): Create a new experiment in the Statsig console, including device-level, custom ID, and isolated experiments, then configure it on the Setup tab before you start it. Deployment: Both.
## Choose Statsig by goal
- [Feature Flags](https://docs.statsig.com/api/content/feature-flags/overview): Feature Gates, commonly known as feature flags, allow you to toggle the behavior of your product in real time without deploying new code.
- [Dynamic Config](https://docs.statsig.com/api/content/dynamic-config/overview): Dynamic configs replace hard-coded values in your application with JSON defined on the server.
- [Experiments Overview](https://docs.statsig.com/api/content/experiments/overview): Learn the fundamentals of experimentation with Statsig, including key concepts, randomization units, and statistical significance.
- [When to Use Feature Gates vs. Experiments?](https://docs.statsig.com/api/content/guides/featureflags-or-experiments): Decide whether to ship with a feature gate or run an experiment, and understand how the two work together.
- [Autotune (Bandits)](https://docs.statsig.com/api/content/autotune/overview): Autotune and Autotune AI automatically weigh explore versus exploit to deliver t
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| growthbook.io | growthbook.io | documentation Data and analytics Developer tools | — | 58 | ✓ | ||
| launchdarkly.com | LaunchDarkly Documentation | documentation DevOps and observability Developer tools | CA | 74 | ✓ | ✓ | |
| abmeter.ai | ABMeter | interface AI and machine learning Data and analytics +2 | — | 46 | ✓ | ✓ | |
| flagsmith.com | Flagsmith | interface Finance and payments DevOps and observability +2 | US | 60 | ✓ | ||
| drip-apex.com | Apex by DRIP | documentation Ecommerce Marketing +1 | US | 53 | ✓ | ✓ | |
| steadybit.com | Steadybit Documentation | documentation DevOps and observability Documentation and reference | — | 46 | ✓ | ✓ | |
| shuttlebase.com | Shuttlebase — Full Reference for Language Models | documentation | US | 46 | ✓ | ||
| devtodev.com | devtodev | Product Analytics Platform | documentation Data and analytics | IE | 58 | ✓ |
Machine-readable: GET /v1/resolve?q=statsig.com · GET /v1/domain/statsig.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage statsig.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for statsig.com:
1. POST https://agentwebmap.com/v1/sites/statsig.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://statsig.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/statsig.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/statsig.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.