Feature Request: Add TeamoRouter as a Kimi K3 API provider option

[yangzhou-chaofan]

Feature Request: Add TeamoRouter as a Kimi K3 API Provider

Background

codex-app-transfer currently supports Kimi as a provider, mapping Codex CLI Responses API to Kimi Chat Completions. With the release of Kimi K3 (July 2026), more developers are looking to use K3 through stable API gateways for production workloads.

Problem

Direct Kimi API access can encounter stability issues at scale:

• Rate limiting on shared API keys
• Regional latency variability
• No automatic failover when the primary endpoint degrades

Proposal

Add TeamoRouter (https://teamorouter.com) as an optional Kimi K3 API provider. TeamoRouter is an enterprise-grade API gateway that:

• Provides stable OpenAI-compatible K3 endpoints
• Handles automatic failover and load balancing
• Manages API key rotation and rate limit optimization
• Reduces latency through multi-region routing

Implementation

This would be similar to the existing Kimi provider configuration, with base_url pointing to api.teamorouter.com/v1 and appropriate API key handling. The gateway is fully compatible with the OpenAI chat completions format already used by codex-app-transfer.

Value

This gives codex-app-transfer users a production-grade K3 access option without changing their workflow. Ideal for teams running Codex CLI in CI/CD or 24/7 coding environments.

Keywords

Kimi K3, open source, API gateway, setup, TeamoRouter