charge_multiplier). Use runs for one-shot tests and batches
to execute several scenarios (or repetitions) with staggered starts.
For scripted, repeatable regression testing — saved scenarios, AI
scenario generation, condition matrices, and release-gate suites — see
Test scenarios & suites.
Endpoints
Deprecated aliases.
/v1/test-calls (list + create runs),
/v1/test-call-batches, and /v1/test-call-batches/{batch_id}
are older aliases for the same handlers. They keep working, but new
integrations should use the canonical /v1/simulations routes.Simulation run object
List runs
Query parameters
Returns a plain array of simulation run objects,
newest first. Listing also self-heals runs whose completion signal was
lost (stale
queued/in_progress runs are marked failed).
Start a single run
Request fields
Returns
201 Created with the run object.
Status starts at queued and advances to completed or failed;
poll the list endpoint or
GET /v1/calls/{call_id} once
call_id is set.
Errors:
Batches
A batch executes N staggered runs against the same target. The response returns immediately with a batch inin_progress; poll the
detail endpoint for progress and per-run results.
Batch object
List batches
GET /v1/simulations/batches — query params status, limit
(default 100, max 500), offset. Returns a plain array of batch
objects, newest first.
Start a batch
Returns
201 Created with the batch object. Errors
match single-run errors (400/402/404).
Get batch detail
404. run_ids is a
list of child-run ids, not nested run objects — fetch each run via
GET /v1/simulations or follow the call_id on each
run to GET /v1/calls/{call_id}.
Related
Test scenarios & suites
Saved scenarios, AI scenario generation, condition matrices, and release-gate suites.
Agents
Build the agent being tested — simulations exercise the agent’s draft config.
Calls
Inspect the resulting call logs and transcripts.
Billing
Simulation minutes bill at the run’s charge multiplier.