Kimi API

Kimi API coverage on the gogogoapi roadmap

Kimi is tracked as a route candidate for long-context and assistant workflows while gogogoapi validates integration readiness.

Follow route readiness

Use the live DeepSeek endpoint now and check the model catalog for Kimi status, use cases, and pricing reference data.

Current status: integration-check
Candidate model: kimi-k2.5
Best for: long-context chat, coding, tool use, and multimodal inputs

Long-context candidate

Kimi is a relevant target for users comparing China model options beyond the first DeepSeek route.

Transparent status

The catalog separates live routes from integration candidates so developers do not confuse roadmap with availability.

Unified billing goal

The roadmap is built around one prepaid balance across supported model routes.

Decision guide

Kimi route snapshot

Use this snapshot to decide whether the route matches your first production or smoke-test use case.

Status
integration-check

Treat as roadmap coverage until route checks pass.

Best for
long-context chat, coding, tool use, and multimodal inputs

Useful for future agent and document workflows.

Pricing reference
$0.60 in / $3.00 out per 1M tokens

Shown for comparison before launch.

FAQ

Questions before you test

Short answers for the questions developers usually ask before creating the first API key.

Is Kimi live on gogogoapi?

Kimi should be treated as a candidate route unless the model catalog marks it live.

Why compare Kimi before launch?

Users planning China model coverage often compare long-context model options before choosing a gateway.

Can one API key cover future Kimi routes?

That is the intended product model once a route is live: one account, one key, and one prepaid credit balance.

Ready to build

Sign in, buy credits, create an API key.

Use the dashboard to fund USD credits with USDT or USDC, create a backend key, and send your first China model API request.

Open dashboard