Documentation
Nefin
Nefin gives you one standard chat-completions request shape in front of the CLI agent you already pay for. Each agent gets its own endpoint inside your tenant — /t/<slug>/codex/chat/completions, /claude/..., /gemini/..., /grok/... — the request body stays the same shape across all four.
# pick the agent by path, not by a "model" field
curl -X POST \
https://api.yourdomain.dev/t/acme/codex/chat/completions \
-H "Authorization: Bearer $TENANT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"messages": [
{"role": "user", "content": "Summarize this repo"}
]
}'
Agents aren't interchangeable behind the scenes. Tool-calling reliability, vision support, and available request fields differ per agent — see Providers before you pick one for a given workload.
Where to start
Getting started
Provision a tenant, sign in, send your first request.
Providers
Codex, Claude Code, Gemini CLI, Grok — capabilities compared.
Authentication
Tenant keys, and how each agent gets signed in.
Chat completions
The core endpoint — request and response shape.
Streaming
Server-sent events, token by token.
Tool & MCP calling
Bridge your own tools — reliability varies by agent.