Skip to main content
SDK 0.6.0 The atlanai SDK works with Atlan Trident from code. One package per language covers two parts:
  • Management: read and write agents, skills, files, sessions, workspaces, datasets, experiments, and scorers. The operation reference describes the public contracts shipped in SDK 0.6.0. A newer Gateway can expose operations that this release does not contain.
  • Tracing: report what your agent did, including which model it called, what it cost, who it ran for, and how well it scored. It is OpenTelemetry-native.
Tracing is a thin layer over the stock OpenTelemetry SDK. It adds Atlan authentication, the agent-sdk.v1 semantic conventions, an export pipeline tuned for generative AI, and privacy controls. Anything already instrumented with OpenTelemetry in your process exports through the same pipeline once you initialize a client.
The two halves of the SDK: tracing is a thin layer over the stock OpenTelemetry SDK that adds Atlan authentication, agent-sdk.v1 conventions, an export pipeline, and privacy controls, and also carries OpenLLMetry and OpenInference spans to Atlan Trident. Management is a separate client with separate credentials that reads and writes Registry artifacts.The two halves of the SDK: tracing is a thin layer over the stock OpenTelemetry SDK that adds Atlan authentication, agent-sdk.v1 conventions, an export pipeline, and privacy controls, and also carries OpenLLMetry and OpenInference spans to Atlan Trident. Management is a separate client with separate credentials that reads and writes Registry artifacts.
Tracing records each run as a trace of typed observations (task, llm, tool) grouped into sessions. It records model, provider, token usage, and cost on the span that spent them, attaches scores next to latency and cost, and can derive a trace ID from a stable external key so retries converge on one trace. OpenLLMetry, OpenInference, and frameworks with native OpenTelemetry flow through the same pipeline. You can identify a visitor per request and mask content before export. The Gateway also enforces your organization’s trace-content policy.

Packages compared

To install, see Install atlanai SDK. Plain JavaScript works the same as TypeScript. The published package is compiled JavaScript with type declarations, so no TypeScript toolchain is required. Both languages can derive the same trace ID from a shared external key. Use this to correlate work across a Python service and a TypeScript service; see Set deterministic trace ID.

Core offerings

Connect management client

Verify your identity, list workspaces, and scope agent reads from Python or TypeScript.

Trace agent

You control the agent’s source and want spans, scores, cost, and visitor identity. Start by tracing your first run.

Evaluate agents

Build datasets, record experiments, retain results, and compare a candidate against a baseline.

Use MCP

Let an agent read Registry artifacts or call tools from a registered downstream server, without reporting its own telemetry.

Call HTTP API

Integrate from a language with no SDK.

Choose where to start

Before you build on the SDK:
  • The management client and the tracing client are independent. Tracing reads its own settings from the environment or from init() and does not reuse the management client’s token, so a process that does both configures both. See the Configuration.
  • client.identify() calls the Registry over HTTP and returns a visitor. Every other tracing operation only produces spans.
  • Tracing configuration usually logs a warning and returns a disabled client when it is invalid. Exporting to an Atlan endpoint without a workspace raises at init(), and an export failure can raise at flush(). See Install and setup errors.
  • Management writes are not retried automatically. See Errors and retries.