Skip to main content

Overview

This document provides an overview of the k0rdent API shape, covering Atlas (Provider Console), Arc (Customer AI Console), and shared services like Auth.
Core Concept: Atlas maps, Arc deploys, k0rdent executes.

RFC Endpoints

Request for Comments (RFC) endpoints are endpoints that are being proposed for discussion and feedback. They are not fully implemented yet, but are subject to change.

Arc API

Self-service portal for AI/ML workload deployment and cluster management

Atlas API

Internal infrastructure management for bare metal, k0rdent clusters, and VMs

Auth API

Centralized authentication with OAuth, session management, and multi-tenant support

Notifications API

In-app/email/slack notification management

Early Draft Endpoints

These endpoints are still in their earlier days

Audit API

Self-service portal for AI/ML workload deployment and cluster management

Billing API

Internal infrastructure management for bare metal, k0rdent clusters, and VMs

Regions API

Centralized authentication with OAuth, session management, and multi-tenant support

Better Auth API

Better authentication with OAuth, session management, and multi-tenant support

API Domain Architecture

k0rdent uses domain-based API routing to separate Atlas (internal provider operations) from Arc (customer-facing operations):

API Endpoint Reference

Atlas API (api.internal.example.com)

Arc API (api.example.com)

Shared Services (Both Domains)

Auth API

Notifications API

Future Planned

TBD/WIP

To be discussed and engineered on what and where these endpoints will be.
Atlas API (api.internal.example.com): Arc API (api.example.com):

TBD - Direct API Access

The following APIs are being evaluated for direct API access. Implementation and availability are to be determined.

Workflows API

Workflow orchestration for long-running operations. Built on Trigger.dev.
Note: Direct API access to Workflows is under evaluation. The current implementation uses Trigger.dev for workflow orchestration. Whether to expose direct API endpoints for workflow management is being determined based on use cases and security considerations.
Design Principle: All infrastructure mutations flow through workflows. This provides durable execution, automatic retries, audit trails, and observability. Workflows double as the event log for the platform.

API Changelog

This section tracks API endpoint changes and iterations to help understand the evolution of the k0rdent API specification.

2026-02-04 - Endpoint Restructuring

Summary: Reorganized API endpoints under domain-based paths and removed implicit /v1 prefix from all documentation.

Removes internal codename arc and atlas from the API endpoint paths

Atlas API (api.internal.example.com)

Arc API (api.example.com)

Auth API (Both Domains)

Future

Moved to TBD Section

  • Workflows API - move to new section, TBD if we expose direct API access to workflows