Skip to main content
These pages are for teams that build agents and need to register them, equip them with reviewed skills, and see what each one did. Atlan Trident records and equips agents; your own runtime, client, or framework runs them. An agent’s record holds its name, description, workspace, instructions, framework, and model, shown on Overview on its profile. It has its own API key and client secret, so it calls Atlan as itself; see How agent identity works and Settings > Identity. Each change to its definition saves a new version that pins the tools it declares and the exact skill versions it uses, shown in Settings > Relationships and released under the workspace’s policy in Settings > Releases. Its sessions, traces, usage, and outputs appear in Sessions, Usage, and Library; see How agent sessions work and How trace inspection works. Agent profile with its tabs and summary of recorded activity

Core offerings

Bring agent into Atlan

Register an agent from its repository with its skills and context, and send its first trace.

Pin agent skills

Lock each skill to an exact, reviewed version.

Manage agent credentials

Rotate or revoke the agent’s own key.

Trace agent runs

See sessions, tool calls, models, and cost.

Evaluate agent quality

Score runs against datasets and compare versions.

Save agent outputs

Keep every document and file it makes in the Library.

Choose where to start

Atlan Trident doesn’t deploy your code: changing an agent’s record doesn’t change how your application runs until you update its configuration. An agent’s machine name and workspace are fixed at registration. A version can pin up to 64 skills, and a skill’s new release doesn’t move a pin until you change the manifest. Archiving revokes the agent’s key, and the app has no restore; its history stays readable.

See also