Per-agent authorization pull
Default endpoint for verification consumers (DSPs, sales houses, agencies). Returns the rows where the requested agent appears as agent_url — typically ≤ a few hundred. Pair with /api/registry/feed?entity_type=authorization to tail subsequent changes via the X-Sync-Cursor header.
evidence defaults to adagents_json only. agent_claim is opt-in (?evidence=adagents_json,agent_claim) to prevent buy-side trust misuse — see specs/registry-authorization-model.md.
Authorizations
Bearer token in the Authorization header. Two token types are accepted:
- Organization API key (
sk_...) issued via the dashboard. Org-scoped, long-lived, for server-to-server use. - User JWT obtained via the OAuth 2.1 authorization code flow with PKCE. User-scoped, short-lived. Discover the authorization server at
/.well-known/oauth-authorization-serverand the protected-resource metadata at/.well-known/oauth-protected-resource/api.
Query Parameters
Agent URL to look up. Canonicalized server-side (lowercased, trailing slashes trimmed).
effective (default) applies override layer; raw reads base table.
raw, effective Comma-separated evidence allowlist. Defaults to adagents_json.
"adagents_json,agent_claim"