Read receptionist release readiness, evidence status, and rollback availability
const url = 'https://api.vocapable.com/v1/agents/example/receptionist-release';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.vocapable.com/v1/agents/example/receptionist-release \ --header 'Authorization: Bearer <token>'Expose a compact control-center view without leaking sealed prompt knowledge.
A passing scripted replay keeps its historic meaning (publish-ready), while
production_ready requires the separate live-model and carrier evidence that a
silent or misrouted PSTN session actually depends on.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Responses
Section titled “Responses”Successful Response
Current publish/rollback state without exposing the sealed prompt evidence.
object
An immutable published snapshot, as a list row.
object
An immutable published snapshot, as a list row.
object
A customer-visible release-gate request and its immutable replay verdict.
The request snapshot remains in the restricted eval ledger rather than being echoed wholesale to a browser. These fields show which draft revision the worker evaluated, which built-in dataset it used, and every assertion result once it settles.
object
object
A customer-visible release-gate request and its immutable replay verdict.
The request snapshot remains in the restricted eval ledger rather than being echoed wholesale to a browser. These fields show which draft revision the worker evaluated, which built-in dataset it used, and every assertion result once it settles.
object
object
The non-scripted serving proof required before a receptionist is production-ready.
This is persisted under eval_runs.results.live_model_preflight by an operational
routing-chain worker. It is intentionally structured so a generic successful model
replay cannot be misread as a proof that the exact production request fits and tools
can continue after a result.
object
Exact serving-envelope evidence captured by a live-model preflight.
object
One server-derived readiness fact for a receptionist release.
object
Example
{ "active_version": { "action_confirmation_policy": "legacy_v0", "receptionist_release_status": "not_applicable" }, "rollback_candidate": { "action_confirmation_policy": "legacy_v0", "receptionist_release_status": "not_applicable" }, "current_gate": { "status": "queued", "mode": "scripted_stand_in" }, "current_live_model_preflight": { "status": "queued", "mode": "scripted_stand_in" }, "production_ready": false, "checks": [ { "status": "ready" } ]}Validation Error
object
object
object
Examplegenerated
{ "detail": [ { "loc": [ "example" ], "msg": "example", "type": "example", "input": "example", "ctx": {} } ]}