Skip to content

Integrations

Connecting a coding tool to SwatowAPI takes one change: point the tool's Base URL and API key at SwatowAPI. Everything else in your workflow stays the same. You do not switch tools or change how you work.

Which protocol surface a tool speaks (OpenAI / Anthropic / Google) is tied to the platform of the group your API key belongs to. The same host auto-routes to the matching surface based on your key's group platform. See Authentication and groups.

Summary

The table below maps common tools to their Base URL, environment variables, and protocol surface. Replace the example key (sk-...) with the one you issued in the console.

ToolBase URLEnv / auth headerSurface
OpenAI-compatible tools (Cursor, Cline, etc.)https://swato.ai/v1OPENAI_BASE_URL / OPENAI_API_KEYOpenAI
Claude Codehttps://swato.aiANTHROPIC_BASE_URL / ANTHROPIC_AUTH_TOKENAnthropic
Codexhttps://swato.ai/v1see CodexResponses API
Gemini CLI / Google SDKshttps://swato.ai/v1betax-goog-api-key: sk-...Google

TIP

When you are unsure of a model's exact model string, call GET /v1/models to get the exact id of a currently available model instead of guessing.

Per-tool setup

Claude Code

Set the two environment variables, then run claude:

bash
export ANTHROPIC_BASE_URL="https://swato.ai"
export ANTHROPIC_AUTH_TOKEN="sk-your-swatowapi-key"
claude

The client appends the /v1/messages request path after ANTHROPIC_BASE_URL. Using Claude Code requires your key to belong to an Anthropic-platform group.

Cursor

In Cursor's settings, enable a custom OpenAI base URL, set it to https://swato.ai/v1, paste your API key, and pick a model. The exact model ids come from GET /v1/models.

Cline / Roo Code

Choose the "OpenAI Compatible" provider, set Base URL to https://swato.ai/v1, set the API key to sk-..., and select the model you want.

Codex

Codex uses the Responses API with Base URL https://swato.ai/v1. It has its own detailed setup page: Codex.

Gemini CLI / Google SDKs

Gemini-family tools use the Base https://swato.ai/v1beta and authenticate with the x-goog-api-key: sk-... header (a ?key= query param also works), following Gemini's own convention. Using the Gemini surface requires your key to belong to a Google-platform group.

Verify

After configuring, run a small read-only task (for example, ask the tool to summarize a snippet without writing files), then open the usage ledger in the console and confirm the call shows up: you should see the model, input/output tokens, and the charge. Failed or timed-out requests are not billed.