Get Latest Publish Gate Run

Return the agent’s most recent publish-gate decision, or null when it has never been gated. This is the durable answer to “are this agent’s checks passing, and when were they last run”, without republishing it.

This endpoint is in beta: a decision exists on workspaces granted publish_eval_gate or red_team_publish_gate - the second is enabled automatically alongside durable_runs_access, so any workspace that can start durable runs records decisions here. Every other workspace reads null.

Return the agent's most recent publish-gate decision, or `null` when it has never been gated. This is the durable answer to "are this agent's checks passing, and when were they last run", without republishing it. This endpoint is in beta: a decision exists on workspaces granted `publish_eval_gate` or `red_team_publish_gate` - the second is enabled automatically alongside `durable_runs_access`, so any workspace that can start durable runs records decisions here. Every other workspace reads `null`.

Authentication

AuthorizationBearer

Enter your API key with the Bearer prefix, e.g. ‘Bearer sk_…’.

Path parameters

agent_idstringRequired

Prefixed agent id.

Response headers

Speechify-Request-IdstringOptional

Unique identifier for this request, present on every response (2xx and non-2xx alike). If the caller sends a Speechify-Request-Id request header the server echoes it back (sanitized and length-capped) so one logical request can be traced end-to-end; otherwise the server generates a fresh value. Log it on every response and quote it in support requests

it is the stable handle that ties your observation to Speechify’s server-side logs, and it matches the request_id field in the error envelope.

The legacy alias X-Request-ID carries the same value and is still accepted on requests, until 2027-07-24. Prefer the un-prefixed name (RFC 6648).

Unique identifier for this request, present on every response (2xx and non-2xx alike). If the caller sends a `Speechify-Request-Id` request header the server echoes it back (sanitized and length-capped) so one logical request can be traced end-to-end; otherwise the server generates a fresh value. Log it on every response and quote it in support requests - it is the stable handle that ties your observation to Speechify's server-side logs, and it matches the `request_id` field in the error envelope. The legacy alias `X-Request-ID` carries the same value and is still accepted on requests, until 2027-07-24. Prefer the un-prefixed name (RFC 6648).

Response

The latest gate decision, or null if the agent was never gated.

gate_runobject or null

Null when the agent has never been gated.

publishedboolean

Whether the agent’s current configuration carries a passing (or overridden) decision, so a run on it is admitted. A trigger whose agent reads false here will fail every fire until the agent is published again.

config_fingerprintstring

The identity of the current configuration - what a publish records. It moves with the prompt, model, guardrails, tools and their schemas, never with the knowledge bases attached or with per-run variables.

Errors

401

Unauthorized Error

403

Forbidden Error

404

Not Found Error

500

Internal Server Error