VoidhashDocs
DevelopersHelp centerGuidesAPI reference
Dashboard
Get started
Introduction
Quickstart
How Voidhash works
Glossary
Versions and releases
Concepts
Teams, projects and environments
API keys
Products and perks
Offers
Subscription lifecycle
People and identity
Events
Features
Paywalls in your app
Feature flags and A/B tests
Paywall components
Push notifications
Ad attribution in your app
Client SDKs
React Native
Swift
Kotlin
Web
Your backend
Node.js
PHP
Go
Rust
Other languages
Payment sources
Forward store notifications
Developer tools
CLI
MCP server
Query analytics with VoidQL
MCP server
Tools
People and access
Catalog and payments
Paywalls
Flags and experiments
Analytics and ads
Webhooks and messaging
Projects, team and settings
Files and assets

Flags and experiments

MCP tools to roll out feature flags and run A/B tests.

These tools let an agent create and roll out feature flags, fix them for one person, and run A/B tests from draft to a concluded winner.

Early access

Feature flags and A/B tests are in early access. Ask us on Discord, or email support@voidhash.com on a paid plan, to turn them on for your team.

Feature flags

Key access: Feature flags.

ToolWhat it does
list_flagsFlags with their state, rollout, variants and list sizes.
get_flagOne flag with its overrides and allow and deny lists.
create_flagAdds a flag, off at 0% unless given a rollout.
update_flagTurns a flag on or off, or changes its rollout, key or variants. Asks first when people lose it or the key changes.
set_flag_overrideFixes a flag, or an experiment arm, for one person.
set_flag_targetsSets a flag's allow or deny list. Asks first when it changes who can get it.
evaluate_flagsWhat one person gets from each flag, and why.
archive_flagArchives a flag. Asks first when it's on.
restore_flagRestores an archived flag as it was.

Experiments

Key access: Experiments.

ToolWhat it does
list_experimentsA/B tests with their status, arms and split.
get_experimentOne experiment in depth, with what can be done next.
create_experimentSets up a draft experiment.
update_experimentChanges its setup. Asks first when changing arms after it started.
start_experimentStarts or resumes it. Asks first.
pause_experimentPauses it: everyone sees the control arm.
conclude_experimentEnds it for good with a winner. Asks first.
get_experiment_resultsEach arm's conversions and revenue against the control, with a verdict.
archive_experimentArchives a draft or concluded experiment.
restore_experimentRestores an archived experiment.

create_experiment and update_experiment take the goal event as primaryMetric. Have the agent set it: left empty, results count purchase_completed, an event Voidhash never sends, so every arm shows 0 conversions. See Conversions for which built-in event to use.

Example

Test whether showing the annual plan first at onboarding raises trial starts.

The agent calls list_paywalls, then create_experiment for a draft with primaryMetric set to $subscription.created, which also fires when a trial starts. Then it calls start_experiment, which asks first. Later, get_experiment_results reports each arm against the control.

Next steps

  • How a flag decides: targeting, overrides and rollouts.
  • A/B test results: conversions and verdicts.
  • Analytics and ads: measure the results.

Something wrong or missing on this page? Tell us by email or on Discord.

PreviousPaywallsNextAnalytics and ads

On this page

Feature flagsExperimentsExampleNext steps