Skip to content
Documentation · Access & base URLs
Docs / Get started

Access & base URLs

Choose the connection your application needs. The model API, MCP tools and dashboard share your account balance, but use different setup steps.

On this page

Choose a connection

Use caseConnect withSetup
Your application calls a modelAPI key + model APIQuickstart
Codex or Claude Code uses our modelsAPI key + client provider settingsCoding agents
An agent needs inference and account toolsMCP browser sign-in or API keyMCP server
You want guided tools and commandsClient plugin + MCP sign-inPlugins

Base URLs

this deployment
OpenAI SDK / Codex   https://xavainf.com/v1
Claude Code          https://xavainf.com
Gemini CLI           https://xavainf.com
MCP with sign-in     https://xavainf.com/mcp/account

Codex appends /responses to its base URL. Claude Code appends /v1/messages, so its base URL must not include /v1. A complete request URL belongs in an HTTP call, not in an SDK's base URL setting.

Keep environments together

Production uses xavainf.com; staging uses zinf.dev. Accounts, balances and keys belong to the environment where you created them. When switching environments, update both the hostname and the key.

Examples throughout these docs use the site you are viewing. Keep credentials in environment variables or your secret manager. Never include them in browser code or a shared configuration file.

Browse before authenticating

GET /v1/models is public. Use it to discover model ids, request endpoints and prices. Inference requests require an API key and available funds.