Production gate
POST /v1/gate/outbound is the canonical production insertion point. It scans
send-bound content, persists the decision, binds an immutable snapshot, and
returns the submission status.
Use GET /v1/gate/outbound/{action_id} to poll a persisted action and
GET /v1/gate/submissions to list workspace submissions
(limit/offset pagination, limit up to 1000, response includes has_more).
The request also accepts content_type (overrides the automatic email/message
classification used by the policy engine) and governance_action_id (links the
submission to a governance agent action). The response also returns
queue_reason (set on QUEUED) and config_hash alongside snapshot_id.
Multi-channel outbound (WhatsApp, Telegram, SMS, LinkedIn, Slack) uses
POST /v2/gate/outbound instead. See
v2 multi-channel gate.
Preview
POST /v1/check is a stateless policy preview. It does not create review work or
dispatch content. See Gate versus preview check.
Usage
GET /v1/gate/usage/tokens reports the workspace’s daily governance token usage.
Quota and rate-limit responses include structured recovery guidance and usage
headers.
The API reference intentionally exposes only supported customer endpoints. It
does not mirror internal operator, admin, or archived product routes.