Start a simulation run for an automation
Freezes the validated scenario batch into one run with one episode per scenario and starts the orchestration. Each episode admits its synthetic trigger through the automation’s production path and runs the requested agent version (the automation’s pinned version by default) against its real integrations with every non-read-only tool call recorded instead of executed, unless allowWrites opted into real writes. Within the organization-wide receipt namespace, Idempotency-Key plus the exact HTTP method, escaped path, raw query, and raw body bytes identify the durable result.
Authorizations
A Recursion API key, created in the console under API keys.
Headers
Replay-protection key in an organization-wide namespace shared by keyed mutations. It must contain 1 to 256 visible ASCII characters and be sent as exactly one header value. Request identity is the exact HTTP method, escaped path, raw query, and raw body bytes. The same request replays the original successful response; any different request returns 409 idempotency_conflict, and an active matching request returns 409 idempotency_in_progress. Completed receipts are retained for approximately 24 hours, pending claims may be reclaimed after approximately 1 hour, and no deduplication is guaranteed after expiry.
1 - 256^[!-~]+$Optional tenant consistency check. When present, it must name the tenant bound to the API key, including when x-organization-id is default.
1Organization in which to act. Required for a tenant-scoped API key. Optional for an organization-scoped key, where it must name that same organization. The value may be an organization id or default.
1Path Parameters
The agent whose automation is simulated.
Body
The automation to simulate. Must belong to the agent in the path.
Scenario batch document, schemaVersion 1: at most 20 scenarios, each one synthetic trigger input with optional checks, rubric and limits.
The agent version to test. Must be a version of the automation's agent. Omitted, the run tests the automation's pinned version.
Execute integration writes for real instead of recording them. For sandbox tenants of the integrations only; requires the role that can edit the automation.
Evaluator for scenario rubrics. Omitted, the simulated agent grades its own episodes through the hardened evaluation path.
Response
Accepted
Whether integration writes executed for real.
-9007199254740991 <= x <= 9007199254740991-9007199254740991 <= x <= 9007199254740991-9007199254740991 <= x <= 9007199254740991SHA-256 of the frozen scenario batch.
Run lifecycle. Episode verdicts, not run status, say whether the agent passed.
pending, running, completed, failed, cancelled Canonical member URL for polling this run.
Aggregated cost of the episode and rubric grader sessions in micro-USD, recorded when the run settles. For a cancelled or failed run it is the spend known at settlement, while its sessions were still stopping.
-9007199254740991 <= x <= 9007199254740991Why the run failed, when it did.