Denim Agentic Access
Denim exposes 19 API operations that an AI agent could call, of which 10 are state-changing ‘acting’ operations. This is a recommended x-agentic-access execution contract — the scope, audience, consequence tier, short-lived token constraints, and escalation each action should carry before it is handed to an autonomous agent.
By consequence: 9 read and 10 safety-critical.
10 operations are classed safety-critical and should require human-in-the-loop approval at runtime.
Contracts are classified heuristically from the provider’s OpenAPI and refresh on every APIs.io network build; audience is bound per deployment. The model follows Curity’s Access Intelligence (apidays Munich 2026). Browse every provider’s agent contracts at agentic-access.apis.io.
By consequence
Highest-consequence actions
The physical and safety-critical operations an agent could invoke — the ones that most warrant scoped tokens, tight TTLs, and escalation. Full per-operation contracts are in the source below.
| Method | Path | Consequence | Human-in-loop |
|---|---|---|---|
| POST | /api/v1/debtor-relationships | safety-critical | required |
| POST | /api/v1/jobs | safety-critical | required |
| POST | /api/v1/jobs/quote | safety-critical | required |
| DELETE | /api/v1/jobs/{id} | safety-critical | required |
| POST | /api/v1/jobs/{job_id}/documents | safety-critical | required |
| POST | /api/v1/jobs/{job_id}/revert-to-draft | safety-critical | required |
| POST | /api/v1/payee-relationships | safety-critical | required |
| POST | /api/v1/payee-relationships/{client_payee_relationship_id}/update-assign-factor | safety-critical | required |
| POST | /api/v2/jobs | safety-critical | required |
| POST | /api/v2/jobs/{job_id}/document | safety-critical | required |