07/Integrations

Connecting Clients

Base URLs and auth to connect IDEs and tools to the gateway.


Most clients connect via a "custom OpenAI base URL". Some tools (Claude, Cursor, Codex, Grafana) use their own compatible paths. All authenticate with a Bearer token.

#Base URLs

PathUsed by
/v1OpenAI-compatible clients (VS Code, Kilo, Codex CLI, Cursor override)
/claudeClaude Code, Claude Desktop (Anthropic-compatible)
/openclawOpenClaw
/codexCodex Desktop App (Responses API conversion)
/cursorCursor IDE
/grafana/assistantGrafana Assistant
/api/*Ollama-native clients
Model naming
The gateway forwards the model id the client sends; it does not guess unknown names. Use a mapped model name or a model group name. Using a group name makes dynamic model switching easy.

#Provider node types

ProviderEndpointsHighlights
Ollama/api/chat, /api/generate, /api/pullLocal inference, model pull, warmup, health checks
vLLM/v1/chat/completions, /v1/embeddingsOpenAI-compatible, SSE streaming, Bearer forwarding
Cursor AI/v1/chat/completionsAuto base URL, model discovery
Antigravity/v1internalGoogle OAuth 2.0, Gemini & Claude, auto token refresh
AWS Bedrock/bedrockConverse API, image input, streaming, STS session tokens