Current Gateway Shape
Accepted first. Then succeeded or failed_safe.
This is the smallest useful public evaluator view of the current Auditable Execution
Gateway API. It stays inside the current managed execution endpoint.
Request Example
{
"input": {
"text": "phase1-success"
},
"outputContract": "contract:extract.result.v1",
"budget": {
"maximumEu": 1,
"reserveEu": 1
},
"idempotencyKey": "eval-request-001",
"webhookUrl": "https://example.com/dlx/webhook"
}
Acceptance Response
{
"executionId": "exec_mmz8xtgp_h5pael2y",
"workflowId": "wf_mmz8xtgp_shoocoiz",
"status": "accepted",
"acceptedAt": "2026-03-20T18:42:32.425Z",
"pollUrl": "/v1/executions/exec_mmz8xtgp_h5pael2y"
}
pollUrl is relative. Resolve it against the gateway
base URL you are evaluating.
Succeeded Response
{
"executionId": "exec_mmz8xtgp_h5pael2y",
"workflowId": "wf_mmz8xtgp_shoocoiz",
"status": "succeeded",
"workflowStatus": "delivery_recorded",
"finalOutput": {
"result": "phase1-success",
"status": "complete"
},
"deliveryState": "recorded"
}
failed_safe Response
{
"executionId": "exec_mmz8xw6e_zyhx6twm",
"workflowId": "wf_mmz8xw6e_xvcyb99x",
"status": "failed_safe",
"workflowStatus": "delivery_recorded",
"safeFailure": {
"failureClassification": "schema_failure"
},
"deliveryState": "recorded"
}
Interpretation
- succeeded means deterministic validation passed.
- failed_safe means the workflow stopped without claiming succeeded.
- deliveryState describes notification handling, not business outcome truth.
- the latest confirmed live success and failed_safe runs both ended with deliveryState: "recorded".