Skip to main content
Kilo Code can connect to the powertokens platform through two provider paths:
  • OpenAI Compatible provider for text models that work through /v1/chat/completions.
  • Anthropic provider with a custom base URL for Anthropic-path models validated as default tool-workflow choices.
Choose the path by protocol support. OpenAI-compatible support does not mean the same model can also be used through the Anthropic provider. If you need to choose the endpoint first, see Text model protocols and endpoints.

​
Choose a path

GoalKilo Code providerBase URLModel scope
Use OpenAI-compatible text modelsOpenAI Compatible or OpenAI (Compatible)https://api.powertokens.ai/v1Text models that support /v1/chat/completions
Use Anthropic-path modelsAnthropic with custom base URLhttps://api.powertokens.ai/v1Recommended Zhipu, MiniMax, Qwen, BytePlus DeepSeek, and re-validated Seed models that support Messages
Use OpenAI-compatible preferred modelsOpenAI Compatiblehttps://api.powertokens.ai/v1Text models whose upstream provider does not support /v1/messages, such as seed-1-6-flash-250715

​
OpenAI Compatible setup

Create a provider profile in Kilo Code:
FieldValue
API ProviderOpenAI Compatible or OpenAI (Compatible)
Base URLhttps://api.powertokens.ai/v1
API KeyYour powertokens platform API key
ModelFor example glm-5.2, MiniMax-M3, or seed-2-0-pro-260328
Max output tokensSet for your task and selected model
Context windowSet conservatively if you are unsure
Image supportEnable only when the model and the platform API publicly support image input
Verify the same path with: 
curl -X POST "https://api.powertokens.ai/v1/chat/completions" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_POWERTOKENS_API_KEY" \
  --data '{
    "model": "glm-5.2",
    "messages": [
      {"role": "user", "content": "Reply with ok."}
    ],
    "stream": false
  }'

​
Anthropic provider setup

Use Kilo Code’s Anthropic provider when you want the Claude/Anthropic path:
FieldValue
API ProviderAnthropic
Use custom base URLEnabled
Custom base URLhttps://api.powertokens.ai/v1
Anthropic API KeyYour powertokens platform API key
ModelOne of the recommended model IDs below
Kilo Code’s Anthropic provider appends /messages to Custom base URL. Set the field to the version path https://api.powertokens.ai/v1 so the final request reaches the platform’s /v1/messages endpoint. Recommended Anthropic tool-workflow models:
Upstream providerModels
Zhipuglm-4.5-air, glm-4.7, glm-4.7-flash, glm-5, glm-5-turbo, glm-5.2
MiniMaxMiniMax-M2.5, MiniMax-M2.5-highspeed, MiniMax-M2.7, MiniMax-M2.7-highspeed, MiniMax-M3
Alibaba Qwenqwen3-coder-plus, qwen3-max, qwen3.5-flash, qwen3.6-plus
BytePlus DeepSeekdeepseek-v3-2-251201
BytePlus Seedseed-1-6-250915, seed-1-8-251228, seed-2-0-lite-260228, seed-2-0-mini-260215, seed-2-0-pro-260328
When you verify the Anthropic path with curl, use the full endpoint path: 
curl -X POST "https://api.powertokens.ai/v1/messages" \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_POWERTOKENS_API_KEY" \
  -H "anthropic-version: 2023-06-01" \
  --data '{
    "model": "glm-5.2",
    "max_tokens": 64,
    "messages": [
      {"role": "user", "content": "Reply with ok."}
    ],
    "stream": false
  }'
Use these models through OpenAI Compatible, not through the Anthropic provider, even if model discovery declares anthropic:
Upstream providerModels
BytePlusseed-1-6-flash-250715

​
Validation checklist

  1. Send a tiny prompt that only asks for ok.
  2. Run one real code-edit task and confirm Kilo Code can read files, propose edits, and finish.
  3. If you enabled streaming, validate a long response.
  4. Validate tool calling, image input, and caching separately before relying on them.

​
Troubleshooting

SymptomAction
Invalid API KeyCheck the key and provider path
Model Not FoundCheck the exact model ID; enter glm-5.2 manually if discovery does not list it
Anthropic provider tool workflow failsThe model is not currently suitable for Kilo Code Anthropic-provider workflows; use OpenAI Compatible
Anthropic provider returns an empty responseDo not use that model as the Anthropic-provider default until you validate it; use OpenAI Compatible first
Tool output or fields differ from upstream docsCheck whether the field is publicly supported by the platform