Reference
Changelog
Breaking and notable changes to the Caicaini API surface. Newest at the top. Watch this page if you depend on the API in production.
Versioning
The API is in v0.x. We are explicit about which fields are stable and which are not. Breaking changes will be announced here at least 30 days in advance once we ship v1.0; until then, expect occasional schema additions (always non-breaking) and rare schema renames (always announced).
Entries
- 2026-05-09v0.1.0Launch
Public Developer API live
The Caicaini Developer API is live in beta. Two compatible HTTP surfaces are available:
POST /v1/messageswith non-stream and SSE streaming.POST /v1/chat/completionswith non-stream and SSE streaming.POST /v1/messages/count_tokensfor input-token previews.GET /v1/models,GET /v1/account,GET /v1/usage.
Five virtual model ids ship:
caicaini/auto,caicaini/opus,caicaini/sonnet,caicaini/kimi,caicaini/haiku. Native vision, tool use, and extended thinking are supported on the models documented in their respective pages.Top-up packs ($10 → $1,000) and a custom-amount slider ($10 – $10,000) are live on /developers/billing. Top-up credits land in a dedicated
apiCreditspool, isolated from chat-product credits. - 2026-05-09v0.1.0New
Per-key rate-limit tiers with auto promotion
Rate-limit tiers (
free,pay_as_you_go,high_volume,enterprise) are wired in. Promotion runs every 5 minutes against confirmed lifetime top-up. Limits are surfaced live on every response viaX-RateLimit-*headers. See the Rate limits page. - 2026-05-09v0.1.0New
Dashboard at /developers/*
Sign in and visit /developers for a balance and usage overview, mint and revoke keys at /developers/keys, chart usage by model and by day at /developers/usage, and top up at /developers/billing.
- 2026-05-09v0.1.0Note
No first-party SDK in launch
We did not ship a vendor SDK. The HTTP surface is small enough that any HTTP client works. See Using HTTP clients for copy-paste-ready Python and TypeScript wrappers.
Get notified
We do not have an RSS feed yet. The fastest way to find out about a breaking change is to follow the support handles on the marketing footer; the page above will be updated the moment a change ships.