Connect to Atlan Trident

Atlan Trident is where your code publishes Skills, registers Agents, and captures execution traces. Every interaction goes through the same HTTP API, and every request carries a bearer credential that identifies your account. In this lesson, you make your first contact with the Registry. Three read-only calls confirm your credential is live and show what it can reach: the baseline you return to whenever something later does not behave as expected.

At the end of this lesson: your connection to Atlan Trident is verified. Your credential reaches the correct account, and you know which workspaces and Skills are visible to it.

Preview. Run the requests in an approved development environment before relying on them in production automation.

Before you begin

Before you start, make sure you have:

Bearer credential: An API key or token the Registry uses to identify your account. Request one through your organization’s access process. See Send bearer token. The next lesson creates an agent: if the Registry refuses your API key there with 403, use a user token instead.
For the Python tab: The SDK, installed with pip install atlanai. See Install atlanai SDK.

Prepare your shell

The examples in this lesson read from two environment variables. Load your token from an ignored local file (.env.local) or your organization’s secret manager, then set them:

export ATLAN_GATEWAY_URL="https://api.atlan.com"
export ATLAN_TOKEN="<your-token>"

Make your first reads

Run these three calls in order. Each one tells you something new about what your credential can reach: who you are, where you can work, and what is already there.

Confirm your identity

Your bearer credential is how the Registry knows who you are. Before making any write, confirm it resolves to the expected account.

Python
JavaScript

The SDK client sends the token on every call and raises one error type, AtlanAPIError, with the documented problem fields. Every call in this lesson uses this client.

import os

from atlanai import AtlanClient

client = AtlanClient(
    os.environ["ATLAN_GATEWAY_URL"],
    bearer_token=os.environ["ATLAN_TOKEN"],
)

identity = client.auth.whoami()
print(identity)

This helper applies a timeout, checks the response content type, and surfaces the documented problem body on failure. Copy it into your project — every call in this lesson and the next uses it.

export function createAtlanJsonClient({ gatewayUrl, token, timeoutMs = 10_000 }) {
  return async function requestJson(path, init = {}) {
    const headers = new Headers(init.headers);
    headers.set("Authorization", `Bearer ${token}`);
    if (init.body != null && !headers.has("Content-Type")) {
      headers.set("Content-Type", "application/json");
    }

    const response = await fetch(new URL(path, gatewayUrl), {
      ...init,
      headers,
      signal: init.signal ?? AbortSignal.timeout(timeoutMs),
    });
    const contentType = response.headers.get("content-type") ?? "";
    const isJson = contentType.includes("application/json") ||
      contentType.includes("application/problem+json");
    const body = isJson ? await response.json() : await response.text();

    if (!response.ok) {
      const error = new Error(body?.detail ?? `Atlan API returned ${response.status}`);
      error.status = response.status;
      error.code = body?.code;
      error.traceId = body?.trace_id;
      throw error;
    }
    if (!isJson) throw new TypeError("Expected a JSON response");
    return body;
  };
}

Then confirm your identity:

const atlan = createAtlanJsonClient({
  gatewayUrl: process.env.ATLAN_GATEWAY_URL,
  token: process.env.ATLAN_TOKEN,
});

const identity = await atlan("/registry/v1/auth/whoami");
console.log(identity);

If the account shown is not what you expect, stop here. Check your credential source before making any writes.

List your workspaces

The workspace ID is required for every write. This call shows which workspaces your credential can access.

Python
JavaScript

workspaces = client.workspaces.list()
print(workspaces)

const workspaces = await atlan("/registry/v1/workspaces?limit=20");
console.log(workspaces);

Note the ID of the workspace where you plan to register your agent. You use it in the next lesson.

List published Skills

See which Skills are already in the Registry before you publish your own.

Python
JavaScript

skills = client.skills.list(limit=20)
print(skills)

const skills = await atlan("/skill/v1/skills?limit=20");
console.log(skills);

An empty list is a successful read. It means no Skills are published yet in this workspace.

Verify results

Confirm the identity is the expected account and the workspace list includes the workspace where you plan to register your agent. An empty Skills list is expected in a fresh workspace.If any response is an error, see Errors and retries: error codes, causes, and when to retry. Do not change a workspace ID or retry a write until you understand the result.

What you have accomplished

You confirmed your credential works, saw which identity it acts as, found the workspace you will use, and read its skills. Every later call uses the same base URL, credential, and workspace.

Get started

Authenticate requests

Send and inspect traces

Record and replay sessions

Use MCP app resources

References

Endpoints

Connect to Atlan Trident

Before you begin

Prepare your shell

Make your first reads

What you have accomplished

What’s next