Kimi K3's 256K context window makes it a natural fit for long-document agents — but official pricing (¥20 input / ¥100 output per 1M tokens) is the steepest of the major Chinese labs. Bridge serves K3 at $1.50/$3.50.
| Kimi K3 (per 1M tokens) | Official (¥) | Official (≈$) | Bridge |
|---|---|---|---|
| Input | ¥20 | ≈$2.82 | $1.50 |
| Output | ¥100 | ≈$14.08 | $3.50 |
| Cache-hit input | ¥2 | ≈$0.28 | $0.15 |
from openai import OpenAI
client = OpenAI(
base_url="https://bridge.computeindex.net/v1",
api_key="sk-bridge-YOUR_KEY",
)
completion = client.chat.completions.create(
model="kimi-k3",
messages=[
{"role": "system", "content": "You summarize long legal documents."},
{"role": "user", "content": open("contract.txt").read()},
],
stream=True,
)
for chunk in completion:
if chunk.choices[0].delta.content:
print(chunk.choices[0].delta.content, end="")
256K-context workloads are exactly where token accounting matters most: a single 200K-token prompt at official output prices gets expensive fast. Bridge meters every request from the upstream usage field, applies the cached-input discount automatically, and lets you reconcile any request by its x-request-id.
Is Kimi K3 on Bridge the same as Moonshot's official model? Yes — same model, served through the OpenAI-compatible Bridge gateway.
Can I stream K3 responses? Yes — standard SSE streaming with stream_options.include_usage supported.
Get $1 free credit → try Kimi K3