Feature flags

Feature flags let you control feature rollouts remotely without deploying code. Turn features on or off, or roll them out to a percentage of users. Quickly disable features when issues arise without redeploying.

Turn it on

Create flags in Flags and evaluate them from your SDK.

How it works

SDKs evaluate flags with POST /v1/flags/evaluate and a publishable or secret key that has flags:evaluate. GET /v1/flags?keys= lists definitions and needs a secret key with flags:read. Evaluate flags with boolVariation, stringVariation, or jsonVariation:

// JavaScript/React/Next.js
const on = await Talaria.flags.boolVariation('new-checkout', false);

// Dart/Flutter
final on = await Talaria.flags.boolVariation('new-checkout', false);

Pass a key and a default value. When the flag is off or undefined, the default is returned. See the JavaScript SDK configuration and Flutter SDK configuration pages for full code examples.

Use it with an agent

Coding agents can manage flags via MCP. Ask your agent to list all feature flags, check the state of a specific flag, turn a flag off, or roll out a flag to a percentage of users. The tools are list_feature_flags, get_feature_flag, set_feature_flag_off, and set_feature_flag_percent. See the MCP tools reference.

Limits and billing

Feature flag evaluations are included in all plans. See pricing for plan details.

• flags:evaluate — Evaluate flags (browser-safe)
• flags:read — Read flag definitions

See Feature flags in the Ingest API reference for the endpoint contract.