Skip to main content
Use the API when your application needs direct access to Registry resources, Skills, Agents and outputs, Files, MCP catalogs, or OTLP ingestion. Core is the Registry-backed surface: it resolves the caller’s account and workspace scope and identifies the extension that owns an artifact where that applies. Direct HTTP API requests apply the caller’s account and workspace permissions.
Preview. This reference describes the currently published public contract. Verify behavior in your environment before relying on it in production.

​
MCP connection endpoint

MCP clients use OAuth with the Streamable HTTP endpoint https://agentgateway.atlan.engineering/mcp. Use the MCP cookbook for client setup and this reference for server and tool catalog operations. The reference is rendered from public OpenAPI artifacts pinned to one reviewed Agent Gateway commit. It keeps the public paths, operations, request shapes, and response schemas while presenting the reference with product-facing labels. The raw snapshots and their checksums are committed in this repository. Refresh and compose them from a reviewed Gateway commit with:
The API playground is disabled, so this site cannot send requests or store a token.

​
Start here

API quickstart

Make three read-only requests before you build a write workflow.

Cookbooks

Complete Skill, MCP, Agent, and coding-harness tasks step by step.

Authentication

Review authentication requirements for direct HTTP API requests.

Compatibility

Understand the Preview contract and deterministic reference process.