The secret key ("secret-...") must never be shipped to a browser or mobile client - it is server-only, unlike client SDK keys.
In pre-fork WSGI setups, initializing Statsig once before forking can break child workers; initialize per-worker after fork instead.
Feature gates default to OFF; a gate with no rules configured in the console will always evaluate false for check_gate.
The Python core SDK doesn't cache or enrich user attributes between calls - pass the full StatsigUser object on every check_gate call.
You must call statsig.shutdown().wait() before the process exits or recently logged/exposure events can be lost because they're batched and flushed asynchronously.
statsig-python-core is a different package and API surface from the legacy `statsig` PyPI package - don't mix their method signatures.
Give your agent this knowledge — and 15,700+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?