REST API
Versioned routes under /api/v1 on your own control plane, authenticated with an API token. Every route lists the ability it needs.
API referenceDevelopers
Build on the API every Levelrail surface already uses
Levelrail is self-hosted, so there is no hosted public API. Your own instance serves a versioned REST API at /api/v1, and the dashboard, CLI and MCP server all run on it.
Three ways in, one API
levelrail-cli
A pure HTTP client for the same API: deploy, roll back, read logs and manage nodes from a terminal or a CI job.
CLI referenceMCP server
levelrail-mcp exposes the API as MCP tools over stdio or a network listener you run yourself, with read-only and tool profile modes.
MCP tool surfaceScoped API tokens
Tokens carry abilities such as read, write and deploy, so an agent or CI job gets only what it needs. IAM policies can further allow or deny access to one resource, such as a single app, and an explicit deny always wins.
Pick the narrowest ability set a client actually needs. Details are in Identity and access.
Route table and spec
An OpenAPI 3.1 document listing every route, its method, path parameters and required token ability is published at https://levelrail.com/openapi.json and regenerated with the API reference. Request and response bodies are not described yet, so they are left generic. Each instance also serves a route table at GET /api/v1/openapi.json.
Point a tool at your instance
Install Levelrail, create an API token, and call /api/v1 from the CLI, MCP server or your own code.