Skip to main content
GET
Get one agent's accountability
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.

v2 compatibility notes

Returns one agent’s accountability: owner assignment and review, identity attestation, the finding codes and a Console handoff when there is a finding. A missing, PERSONAL or unhomed agent, one you may not read, and one whose home does not give you grants:read, policies:read and audit:read are the same 404 Agent not found. Repair a finding in the Console, or with POST /api/v2/agents/assignOwner, acknowledgeReview and attestIdentity, which need agents:manage at the agent’s home; only a person (a Personal key) can attest. See Agent accountability. For every readiness check without the governance bundle, see Get an agent’s readiness.

Authorizations

Authorization
string
header
required

An External App: the JWT it obtains from POST /oauth/token with OAuth2 client_credentials. Pass as Authorization: Bearer <jwt>. An app's static companion key also authenticates as the app, but is deprecated and is not protected by Idempotency-Key.

Path Parameters

agentId
string
required

The agent's id; missing is 400.

Minimum string length: 1

Response

The agent's accountability

data
object
required

One agent's accountability: owned by an active person, reviewed on time and attested for its current definition. owner.finding is the agent_ownership gate's code and attestation.finding the identity_verification gate's; owner.assigned is true only for an active owner (an inactive owner reads false with agent_unowned). handoff is non-null exactly when a finding is. Times are epoch milliseconds. No owner identity, attesting person or definition hash is returned.

meta
object
required