Skip to main content
GET
/
v1
/
analytics
/
policies
/
revisions
/
{revision_id}
/
disclaimer-status
Whether an enforcing agent_response policy is attached (TTFT disclaimer)
curl --request GET \
  --url https://api-sandbox.featherhq.com/v1/analytics/policies/revisions/{revision_id}/disclaimer-status \
  --header 'x-api-key: <api-key>'
{
  "revision_id": "<string>",
  "channel": "<string>",
  "blocking_response_policy": true,
  "disclaimer": "<string>"
}

Authorizations

​
x-api-key
string
header
required

Path Parameters

​
revision_id
string<uuid>
required

Query Parameters

​
channel
string
default:text

Response

Successful Response

Whether an ENFORCING agent_response policy is in effect for an assistant + channel.

Drives the dashboard's TTFT-disclaimer surfacing: when blocking_response_policy is true, an attached mode=enforce agent_response policy gates the reply against a verdict before the user sees it (a visible first-token delay on the always-gate path), so the author should see the disclaimer copy. v3 is transport-independent — the signal is enforce vs monitor, not a channel-resolved mode; channel is echoed for the caller only.

​
revision_id
string
required
​
channel
string
required
​
blocking_response_policy
boolean
required
​
disclaimer
string | null