Xantly for developers

Every Xantly developer resource, at a predictable URL. If you are an agent, start with llms.txt or agent-instructions.md.

Xantly API

Resource	URL
Xantly API base URL	`https://api.xantly.com/v1`
Xantly OpenAPI specification	xantly.com/openapi.json
Xantly API documentation	docs.xantly.com/docs/
Xantly Quickstart	docs.xantly.com/docs/quickstart
Xantly Authentication guide	xantly.com/docs/authentication
Xantly Rate Limits	xantly.com/docs/rate-limits
Xantly Versioning & Deprecation Policy	xantly.com/docs/versioning-and-deprecation
Xantly Webhooks	xantly.com/dashboard/developer/webhooks

The API is OpenAI-compatible. Point base_url at https://api.xantly.com/v1, pass your key as a bearer token, and send model xantly/auto.

Xantly MCP server

Xantly speaks the Model Context Protocol, so Claude, ChatGPT, Cursor, VS Code and Zed can call it as a tool server natively.

Resource	URL
Xantly MCP endpoint (Streamable HTTP)	`https://api.xantly.com/mcp`
Xantly MCP manifest	xantly.com/.well-known/mcp.json
Xantly MCP documentation	xantly.com/docs/xantly-mcp-launch

Authenticate with your Xantly API key as a bearer token. An anonymous request returns 401 with a WWW-Authenticate header naming the metadata document. Fifteen tools cover routing decisions, cache inspection, memory, cost breakdowns and intelligence-mode control.

Machine-readable discovery

Document	URL
Protected resource metadata, RFC 9728, with `scopes_supported`	xantly.com/.well-known/oauth-protected-resource
Authorization server metadata, RFC 8414	xantly.com/.well-known/oauth-authorization-server
Agent instructions, when and how to call Xantly	xantly.com/.well-known/agent-instructions.md
Plugin manifest	xantly.com/.well-known/ai-plugin.json
llms.txt, site index for agents	xantly.com/llms.txt
llms-full.txt, the whole documentation corpus	xantly.com/llms-full.txt
sitemap.xml	xantly.com/sitemap.xml

Scoped API keys

Xantly API keys carry scopes, and the gateway enforces them. The full list is published in the RFC 9728 protected-resource metadata above under scopes_supported, so an agent can request least privilege without reading prose. A key with no scopes is unrestricted, which keeps existing keys working; naming scopes on a key narrows it.

Scopes follow resource:action: inference:read, inference:write, routing:read, routing:write, governance:read, governance:write, cache:read, cache:write, analytics:read, audit:read, billing:read, billing:write, team:read, team:write, webhook:read, webhook:write, and admin:full.

Getting a key

Account creation, key generation and top-up are self-serve at xantly.com/register; no sales contact at any stage. GET /v1/models needs a key but invokes no model and bypasses the budget check, so it is the zero-cost way to verify a key works. There is no free tier and no sandbox; usage is prepaid from $5.