LLM API Keys · BYOK

Bring your own Anthropic or OpenAI key so agent buddies bill to your provider account instead of Waypath’s metered plan. Each buddy is routed independently. You can mix Metered, BYOK Claude, and BYOK OpenAI freely.

This page covers the provider key setup. For the per-buddy routing controls, see Agents → BYOK.

Generate a provider key

Configure in Waypath

Open Settings → Integrations and scroll to LLM Providers. Paste your key and click Save.

Under the hood:

POST /api/integrations/claude/configure
Authorization: Bearer <token>
Content-Type: application/json
 
{ "apiKey": "sk-ant-..." }

POST /api/integrations/openai/configure
Authorization: Bearer <token>
Content-Type: application/json
 
{ "apiKey": "sk-..." }

Validation behavior:

• Anthropic keys must start with sk-ant-; validated against https://api.anthropic.com/v1/models (free, no token cost)
• OpenAI keys must start with sk-; validated against https://api.openai.com/v1/models (free, no token cost)
• Invalid keys return 401 Invalid <provider> key: <reason>
• Read-only workspaces return 403

Successful responses look like:

{ "status": "configured", "provider": "claude" }

Remove

DELETE /api/integrations/claude
Authorization: Bearer <token>

DELETE /api/integrations/openai
Authorization: Bearer <token>

Either clears the stored key and drops the provider from the workspace’s connected platform list. Any buddy currently routed through that provider falls back to Metered on the next turn.

What happens next

Keys are persisted per-workspace via workspaceManager.setIntegrationConfig() with the same encryption policy as other integration configs. The chat runtime resolves the active key per request via resolveModelForBuddy(). See Agents → BYOK for the resolution order and behavioral differences between Metered and BYOK modes.