Object ids
Every prefix the system emits, and what to store.
Every object carries a prefixed id. The prefixes appear throughout the API, the decision log, the exports and the signed verdicts, and they are stable: an id is never reissued and never changes shape.
| Prefix | Object | Where you meet it first |
|---|---|---|
agt_ | Agent | POST /v1/agents |
mnd_ | Mandate | POST /v1/mandates |
dec_ | Decision | the response to an authorization request |
rev_ | Review | a decision with verdict review |
pol_ | Policy version | stamped on every decision and verdict |
n_ | Nonce | inside a signed verdict |
esc_ | Escrow | POST /v1/escrows |
whk_ | Webhook endpoint | POST /v1/webhooks |
evt_ | Webhook event | the jti of a signed webhook event |
req_ | API request (trace) | X-Request-Id on every response |
What to store
Store dec_ against your own order or invoice. It is the join key between your books and ours, it appears in every export, and it is the id support will ask for.
Store req_ when something goes wrong. It identifies one HTTP request in our trace, including requests that never produced a decision, which is exactly the case where the decision id does not exist yet.
The two are not interchangeable and answer different questions: dec_ asks what was decided, req_ asks what happened to a call.