Skip to main content
Split testing routes an agent’s live calls across variants — weighted configurations that override specific fields (prompt, voice, product, …) while inheriting everything else from the agent’s deployed config. Each call records which variant served it (agent_variant_id / agent_variant_label on the Call object), and the stats endpoint compares outcomes per variant. The control variant (is_control: true) represents the agent’s deployed config unchanged. Enabling split testing auto-creates a control if none exists.

Endpoints

Variant object

POST requires label (everything else optional) and returns 201. PATCH accepts any subset; DELETE returns 204.

Enable / disable split testing

Response
The toggle is staged as a draft on the agent — live traffic starts (or stops) splitting only after you deploy. Enabling with no control variant auto-creates one (label: "Control", weight: 100).

Variant stats

Response

Agents

split_testing_enabled lives on the agent (draft/deploy).

Calls

Filter call history by agent_variant_id fields on each call.