statsig
Statsig is a feature management and experimentation platform that helps product teams ship features safely with feature flags, run A/B tests, and measure the impact of every feature on key metrics.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles statsig the way a machine reads it — 46 machine-readable artifacts across 18 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — statsig scores 48.5/100 (developing), with a separate agent-readiness read of 32/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-08-03 · rubric v0.9
Put this on your own site. The badge is drawn live from statsig's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/statsig/"
title="statsig on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/statsig.svg"
alt="statsig Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/statsig/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/statsig/"
title="statsig on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/statsig/card.svg"
alt="statsig Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile statsig
Each block below is one kind of artifact we hold for statsig. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Statsig Events API
The Statsig Events API handles the ingestion of event data from both client and server SDKs. It receives exposure events, custom events, and diagnostic data at the events.statsi...
statsig Audit Logs API
Access audit log entries tracking changes made to project configuration through the console or API.
statsig Autotunes API
Manage autotune configurations that automatically optimize parameter values based on a target metric.
statsig Configuration API
Endpoints for downloading full project configuration specs for server-side local evaluation.
statsig Dynamic Configs API
Manage dynamic configurations with full CRUD operations for server-driven configuration values.
statsig Experiments API
Manage A/B test experiments including creation, configuration, starting, resetting, and analysis.
statsig Feature Gates API
Endpoints for evaluating feature gates for users, returning boolean pass/fail values along with rule identification.
statsig Gates API
Manage feature gates including creation, updates, rules, overrides, enabling, disabling, launching, and archiving.
statsig Holdouts API
Manage holdout groups that exclude users from receiving specific features for measuring long-term impact.
statsig Initialization API
Endpoints for initializing client SDKs with all evaluated feature gates, configs, experiments, and layers for a given user.
statsig Keys API
Manage API keys for the project including server secret keys, client SDK keys, and console API keys.
statsig Layers API
Manage layers that enable sharing parameters across multiple experiments while maintaining mutual exclusivity.
statsig Metrics API
Access and manage metric definitions and metric sources used in experiment analysis.
statsig Segments API
Manage user segments for targeting rules across gates, configs, and experiments.
statsig Tags API
The Tags API from statsig — 1 operation(s) for tags.
statsig Target Apps API
Manage target application definitions that scope feature configurations to specific applications.
statsig Users API
Manage user data and lookup user properties within the Statsig project.
statsig Webhooks API
Endpoint for receiving event data from third-party applications via webhook integration.
Scroll within the panel for all 18 ·
Open Collections 5
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Statsig Client SDK API
OPEN COLLECTIONStatsig Console API
OPEN COLLECTIONStatsig Events API
OPEN COLLECTIONStatsig HTTP API
OPEN COLLECTIONStatsig Server SDK API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Statsig Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Statsig Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Statsig Webhook Events
Statsig's webhook system provides real-time event-driven notifications for exposure events and configuration changes. Webhooks are triggered at runtime as users are assigned to ...
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Statsig Context
JSON-LDSpectral Rules 3
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 3
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
JSON Structure 3
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Statsig Event Structure
JSON STRUCTUREStatsig Experiment Structure
JSON STRUCTUREStatsig Feature Gate Structure
JSON STRUCTUREExamples 5
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Statsig Check Gate Example
EXAMPLEStatsig Create Gate Example
EXAMPLEStatsig List Gates Example
EXAMPLEStatsig Log Events Example
EXAMPLESecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for statsig — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/statsig · machine-readable index on apis.io
This is an independent, third-party profile of statsig, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
[email protected]
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.