Response contains a flags object keyed by flag key with enabled state, variant, and evaluation reason metadata.
Optionally add config=true as a query param to get PostHog config in the same response.
Docs: https://posthog.com/docs/api/flags
Known gotchas
This endpoint replaced the older /decide endpoint — new integrations should use /flags?v=2.
Group-targeted flags evaluate as false unless you pass the matching "groups" object in the body.
If your organization exceeds its feature flag quota, responses include quotaLimited and flags stop evaluating — check billing rather than debugging your code.
Server-side evaluation without person_properties overrides uses stored person properties; pass overrides explicitly if you need up-to-the-moment values.
Each /flags request is billed as a flag request — for high volume use local evaluation via /flags/definitions instead.
Give your agent this knowledge — and 15,500+ 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?