HLA-Verify Agentic Access
HLA-Verify exposes 25 API operations that an AI agent could call, of which 15 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: 10 read, 14 write, and 1 physical.
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.
API Evangelist recommendations, not provider rules. These classifications are generated heuristically from each operation's method, path and name. They suggest how an agent's access could be scoped. They are not authorization, approval or human-in-the-loop requirements that the provider enforces.
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 | Recommended human-in-loop |
|---|---|---|---|
| POST | /v1/checkout | physical | conditional |
Source
Agentic Access
Work with this as data
Every access contract here is available over the APIs.io API and to AI agents over MCP. Agentic Access is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.