> ## Documentation Index
> Fetch the complete documentation index at: https://platform.atlan.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on Atlan objects, use the Atlan MCP server at https://api.atlan.com/mcp or the SDK. To install or publish skills from a terminal, use the `aireg` CLI; `aireg --map json` prints its command map. The `atlanai` CLI is deprecated. Run a read-only identity check before any write.
> The docs MCP server at /mcp searches these docs only. It cannot read or change Atlan objects.
> SDK packages: Python `atlanai` (PyPI) and TypeScript `@atlanai/sdk` (npm). Show Python first, then TypeScript.
> These docs cover Atlan AI Registry, Atlan's hosted product. The AI registry specification and aireg CLI are maintained separately. /open-source lists publicly reachable signed installers and explains that the source repository and hosted CLI reference currently require GitHub access. Do not claim the repository or its reference docs are publicly accessible. Use these docs for Atlan-specific setup such as the adapter, sign-in and workspaces.

# API · 14 October 2026 (0.9.291–0.10.56)

> You can now register a repository from its remote and link what came from it, and editing a released agent now publishes its next version.

Released 14 October 2026 · API 0.9.291–0.10.56.

## Features

### Connect a repository

The API has a new endpoint, `POST /repo/v1/repos`, that registers a repository
in a workspace from its remote URL alone. `GET /repo/v1/repos/{repo_id}` reads
it back. Two spellings of one remote land on the same repository, so registering
again is safe. Skills, agents, and scorers can now name the repository they came
from with a `sourced_from` relationship, so you can find everything that came
from one repository. A coding agent can do both steps with the
`extension__repo__register_repo` MCP tool and the `atlan-connect-repo` default
skill. To start, run the `atlan-connect-repo` skill from a checkout of your
repository.

## Improvements

* **Agents:** `PATCH /agent/v1/agents/{agent_id}` now publishes a released
  agent's next version when it changes the model or instructions, instead of
  failing with `version_already_released`.
* **Agents:** Added `POST /agent/v1/agents/{agent_id}/versions`, which publishes
  a version from only the fields that change, and `GET
  /agent/v1/agents/\{agent_id\}/versions` to list every version.
* **Agents:** Each skill an agent uses can now be pinned to an exact
  `version_ordinal`; a skill without one is pinned to its current release.
* **Agents:** An agent can now record the MCP servers it calls with a
  `uses_mcp_server` relationship, as it records skills with `uses_skill`.
* **Agents:** `POST /agent/v1/agents/{agent_id}/sessions` now takes an
  `Idempotency-Key` header on the Atlan runtime, so a retry returns the same
  session instead of starting another.
* **Agents:** `GET /agent/v1/sessions/{session_id}` now reports a session's
  `launch_status` on the Atlan runtime: `pending`, `started`, `failed`, or
  `unknown`.
* **Agents:** A session on the Atlan runtime now keeps its outcome and usage in
  `execution` after its run's history expires.
* **Agents:** A session whose run stopped before saving its outcome is now
  recovered, or reported with `session_status` `unknown` when no outcome can be
  found.
* **Agents:** `extension__agent__get_trace_spans` now returns a step's content,
  errors, and attributes when asked with `include`, and keeps only some steps
  with `names` or `errors_only`.
* **Evals:** `PATCH /eval/v1/scorers/{scorer_id}` and `PATCH
  /eval/v1/datasets/\{dataset_id\}/records/\{record_id\}` now save a new version in
  one step, so a failed edit no longer half-saves.
* **Evals:** Renaming or re-describing a scorer with `PATCH
  /eval/v1/scorers/\{scorer_id\}` no longer creates a new version of it.
* **Ontology:** Added `POST /ontology/v1/draft-saves`, which saves a reviewed
  import's new definitions as unpublished drafts once a person approves the
  preview.
* **Registry:** `POST /registry/v1/search` and `POST /registry/v1/aggregate` now
  take `rel.<rel_type>` filters, which keep the artifacts with that relationship
  to the artifacts you name.
* **Registry:** `POST /registry/v1/aggregate` now groups by a relationship's
  target with `group_by` `rel.<rel_type>`, for example to count the agents that
  use each skill.

## Fixes

* **Ontology:** Fixed importing an ontology export into another ontology or
  workspace, which needed its IDs edited first (`POST
  /ontology/v1/imports/preview`).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.