Hanzo
CLIExperiment

Experiment

7 `hanzo` commands for Experiment, each calling one operation on api.hanzo.ai.

Package experiments is A/B testing anything: a flag, an ad, a subject line, a model.

7 commands · API reference →

CommandCallsWhat it does
hanzo experiments analyze <id>POST /v1/experiment/{id}/analyzeIs per-variant conversion, lift and statistical significance against the control arm.
hanzo experiments assign <id> --subject <subject>GET /v1/experiment/{id}/assignIs the variant one subject is bucketed into, and the payload that variant carries.
hanzo experiments decide <id> --winner <winner>POST /v1/experiment/{id}/decidePromotes one variant to the whole rollout and records who decided.
hanzo experiments get <id>GET /v1/experiment/{id}Is one experiment's definition and lifecycle: variants, weights, control arm, status and winner.
hanzo experiments healthGET /v1/experiment/healthIs whether the experiments subsystem is mounted and serving in this process.
hanzo experiments listGET /v1/experimentIs every experiment in the caller's org, with its variants, status and decision, ordered by project then id.
hanzo experiments create --id <id> --metric-event <metricEvent> --variants '[{"control":false,"key":"<key>","payload":"<payload>","weight":0}]'POST /v1/experimentRegisters a controlled experiment AND puts its assignment flag live, in that order, so the arms start bucketing…

How is this guide?