Agents

An agent is a non-human identity that represents an automated system. Link an agent to an API key so traces uploaded with that key are attributed to the agent instead of the key creator.

When to use agents

A background service or bot uploads traces and you want them labeled clearly
Multiple automated systems share a namespace and you need to tell them apart
Team members rotate but your CI pipeline's identity should stay the same

Unlike personal accounts, agents are not tied to a team member. They persist when people leave the organization.

Create an agent

Open /<org-slug>/settings/agents
Select Create Agent
Enter a name and optional description
Optionally upload an avatar

The agent's slug is generated from its name. You can create up to 25 agents per namespace.

Link an agent to an API key

Each API key can be linked to one agent. A single agent can have multiple API keys.

To link an existing key:

Open /<org-slug>/settings/api-keys
Click the agent dropdown on the key row
Select an agent (or No agent to unlink)

For more on key creation and scopes, see API Keys.

How trace attribution works

When a trace arrives via an API key linked to an agent, the agent's name and avatar appear as the trace author in the feed and trace detail views. A robot icon marks agent-attributed traces.

If the key has no linked agent, the trace is attributed to the key creator as usual.

Edit an agent

Open /<org-slug>/settings/agents
Click the edit button on the agent row
Update the name, description, or avatar

Changing an agent's name updates the display on all its existing traces.

Delete an agent

Deleting an agent removes its identity from the namespace. Existing traces keep their content but no longer display the agent's name or avatar.

API keys previously linked to the agent are not revoked. They revert to attributing traces to the key creator.