Skip to main content
Use this cookbook to register an Agent and preserve activity reported by the runtime that executes it. Atlan catalogs the Agent and its evidence. It does not start or execute the run.
Run Agent workloads in your configured provider or coding harness. Keep runtime credentials and execution controls in that environment.

​
Register an Agent

Create the provider and environment records when they apply. Then create the Agent through the Agent category in the API reference. The Agent record provides a stable identity for the runtime and for the sessions it reports. Keep provider credentials outside source code, URLs, browser storage, and committed configuration files. For a Claude workflow, see Claude Managed Agents.

​
Record a completed run

After the external runtime completes a run, create a final session record with the original execution timestamp, outcome, stop reason, and usage. For a coding harness transcript, add the ordered session_message records to the session. Retain the Agent and session IDs to correlate the external run with its Atlan record. For provider-run Agents, inspect provider-native activity through the session events endpoint. Use session messages for the transcript records your harness uploads.

​
Verify a recorded run

Use the recorded session identifier to inspect reported events, messages, and traces. A successful create request confirms that Atlan accepted the final record. Compare its timestamp and outcome with the external runtime when you need to verify the execution itself.