Kimi K2.5 from one catalog
Use Kimi K2.5 without a separate integration, then compare it with DeepSeek, Qwen, GPT, Claude, and Gemini from the same account.
Kimi K2.5 · long context · agents
Kimi K2.5 API
Call Kimi K2.5 through one OpenAI-compatible API key. Keep your existing SDK, switch base_url and api_key, and use one account for Kimi alongside DeepSeek, Qwen, and other supported models.
GPT · Gemini · Claude · DeepSeek · Kimi · Seedance — one key, one invoice · no credit card to start
Kimi K2.5 API access
| Kimi K2.5 / 1M tokens | $1.20 | $3.00 |
| OpenAI SDK migration | base_url + key | Provider SDK work |
| Kimi and other models | One key | Separate accounts |
* Representative coverage — see live pricing for current model rates and availability.
OpenAI-compatible API
Keep the OpenAI SDK already in your application. Change base_url, set a flatkey API key, and select a supported Kimi model id.
Live pricing before you scale
Check Kimi K2.5 pricing and availability in one account, then manage its spend alongside the rest of your model usage.
A low-commitment way to evaluate
Use one OpenAI-compatible integration to evaluate Kimi without committing to another subscription or rewriting your API client.
Kimi K2.5 API
Call Kimi K2.5 through one OpenAI-compatible API key. Keep your existing SDK, switch base_url and api_key, and use one account for Kimi alongside DeepSeek, Qwen, and other supported models.
Get your Kimi K2.5 API keyGPT · Gemini · Claude · DeepSeek · Kimi · Seedance — one key, one invoice · no credit card to start
Can I call Kimi K2.5 through this API?
Yes. Use the kimi-k2.5 model ID with a flatkey API key and the OpenAI-compatible /v1 base URL.
Can I use my existing OpenAI SDK?
Yes. Point the SDK at the flatkey /v1 base URL, use a flatkey API key, and choose the Kimi model id you need.
Do I have to change my code?
No. flatkey.ai is OpenAI-compatible: keep your existing OpenAI SDK and switch base_url plus api_key. Model ids stay the same.
How is billing handled across models?
One plan covers every model. Usage analytics and a single invoice keep spend bounded before you scale.