Skip to main content
POST
The core enforcement call. Every PEP method resolves to one authorize request. The PDP evaluates the agent’s attached latches for the given stage and returns a binding verdict.
Clients must fail closed: on any error, timeout, or unrecognized verdict, treat the step as BLOCK. See Fail-closed.

Authorizations

​
Authorization
string
header
required

Workspace API key (ak_live_…).

Body

application/json
​
agentId
string
required

Must resolve to a workspace agent, else 404.

Example:

"health-ai"

​
stage
enum<string>
required
Available options:
input,
context_egress,
output,
delivery,
action
​
session
string

Telemetry session id; defaults to "unknown".

Example:

"sess_demo"

​
content
string

Text for input / context_egress / output / delivery.

​
tool
string

Tool name for the action stage; normalized before matching.

Example:

"renew_meds"

​
args
object

Action arguments; action checks read args.medication.

Example:
​
simulated
boolean
default:false

Marks the decision as simulated in the evidence feed.

Response

A policy decision.

​
verdict
enum<string>
required
Available options:
ALLOW,
WARN,
BLOCK,
ESCALATE
​
stage
string
required
​
policyId
string
required
Example:

"latch-1"

​
rule
string
required
Example:

"Prescription & Controlled Substance Authorization"

​
reason
string
required
​
transformedContent
string | null

Rewritten content on WARN (e.g. PHI-minimized).

​
tool
string | null
​
permitId
string | null

Set only on ALLOW + action.

​
attachedPolicyIds
string[]

Enterprise baseline ∪ agent.policyIds.