agtOS uses API keys to authenticate with cloud AI providers. You can configure one or both providers — the system uses whichever is configured in the model slot registry.Documentation Index
Fetch the complete documentation index at: https://docs.agtos.ai/llms.txt
Use this file to discover all available pages before exploring further.
Anthropic (Claude)
Pay-per-token billing from console.anthropic.com.- Token prefix:
sk-ant-api03- - Sent via
X-Api-KeyHTTP header - Direct SDK connection to
api.anthropic.com
OpenAI
Pay-per-token billing from platform.openai.com.- Token prefix:
sk- - Used via OpenAI Node SDK v6
- Supports GPT-4o and GPT-4o Mini
Cloud Provider Selection
Cloud provider selection is configured per slot in~/.agtos/config.json via the Model Slot Registry (ADR-020). Run agtos setup to configure slots interactively, or edit the config file directly:
~/.agtos/config.json
claude, openai, ollama, openrouter). When both API keys are configured, you can mix providers across slots — e.g., Claude for chat and OpenAI for reasoning.
Claude Transport Options
By default, agtOS connects to the Anthropic API directly via the SDK. You can optionally spawn theclaude CLI binary as a subprocess:
ANTHROPIC_API_KEY is passed to the subprocess as an environment variable.
CLI transport requires the
claude CLI to be installed and on your PATH. Install from claude.ai/download.Advanced Options
Endpoint Authentication
Optionally protect all/api/* routes with a Bearer token:
Authorization: Bearer <key>. Uses timing-safe SHA-256 comparison. When unset, endpoints are open (suitable for local development).
What’s next
Providers
Configure Claude, OpenAI, Ollama, sherpa-onnx, and the model router.
Environment Variables
Complete reference for all configuration options.