POST/v1/boundary/check
UseCall this from the covered production system when the agreed high-risk action is about to proceed.
Headers
Authorization: Bearer <CRATON_API_KEY>, Content-Type: application/json
Returnsverdict, receipt, commitment_id, request_id, boundary_snapshot.
curl -X POST -H "Authorization: Bearer <CRATON_API_KEY>" -H "Content-Type: application/json" -d '{
"partner_id": "northstar_controls",
"gate_type": "threshold_gate",
"system_scope": "operations_console",
"decision_type": "threshold_execution_request",
"decision_owner": "operations_owner",
"decision_size_usd": 500000,
"case_id": "host-case-001",
"external_reference": "host-request-123",
"context": {
"authorization_status": "present",
"authorization_reference": "approval-2026-001",
"authorization_source": "approval_workflow"
}
}'
Authorization fields are submitted metadata. Craton does not verify whether the underlying approval, authorization, or workflow event occurred; the signed receipt proves what was submitted and how the locked boundary policy evaluated it.