Register an agent

Define a stable agent identity before assigning tool access.

Before you start

Identify the automation owner, environment, purpose, and the verified identity claims that will represent the agent.

Procedure

1. Create an agent record with a stable identifier and owner.

2. Configure the identity relationship using the deployment-supported signed claims or workload identity mechanism.

3. Restrict policy to the required tools and context. Keep the human delegator separate from the agent identity.

4. If the upstream needs credentials, create a binding for the intended agent and target rather than reusing an unrestricted account.

Verify the result

Make a call through the actual client and inspect the audit record for the expected agent identity and credential mode.

If it does not work

If the agent is missing from audit or policy context, repair identity mapping. A client-supplied label is not sufficient identity evidence.

Read the related concept or consult the Admin API for exact request fields.

Implementation reference

Read the source contract.