Gladia Agentic Access
Gladia exposes 21 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: 11 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 | /audio/text/audio-transcription | safety-critical | required |
| POST | /v2/live | safety-critical | required |
| DELETE | /v2/live/{id} | safety-critical | required |
| PATCH | /v2/live/{id} | safety-critical | required |
| POST | /v2/pre-recorded | safety-critical | required |
| DELETE | /v2/pre-recorded/{id} | safety-critical | required |
| POST | /v2/transcription | safety-critical | required |
| DELETE | /v2/transcription/{id} | safety-critical | required |
| POST | /v2/upload | safety-critical | required |
| POST | /video/text/video-transcription | safety-critical | required |