Kimi K3.1 Pro
Moonshot Kimi K3.1 Pro for long-horizon coding, 3D creation, financial research, and agent workflows.
Overview
- Moonshot launched Kimi K3.1 Pro on October 23, 2026 as the first model in its K3.1 series. Moonshot describes it as a 3T-class model with a 1M-token context window and improvements in coding, 3D creation, finance, and agentic work.
- The Moonshot API model ID is kimi-k3.1-pro; the Highspeed variant is kimi-k3.1-pro-highspeed. Check the GPT88 console and GET /v1/models for current account availability and routing.
- Moonshot-reported benchmarks and Artificial Analysis evaluations both indicate stronger agentic performance, but use different harnesses, datasets, and evaluation conditions.
Best Use Cases
- Multi-step engineering tasks in a terminal harness
- Generating or iterating on 3D/CAD assets from images or text
- Retrieval and analysis across long financial documents
- Long-context and tool-using agent evaluations with verifiable outcomes
Integration Notes
- Use https://api.gpt88.cc for GPT88 and check GET /v1/models for kimi-k3.1-pro before making a minimal request through a supported compatible endpoint.
- Moonshot API IDs are kimi-k3.1-pro and kimi-k3.1-pro-highspeed. IDs can differ across products and third-party gateways.
- Kimi Code documentation says K3.1 Pro requires thinking mode. Confirm reasoning parameter support in the current client and gateway.
Usage Notes
- Most launch scores are vendor-reported. Comparisons may combine different harnesses and leaderboard sources; read each benchmark footnote.
- Artificial Analysis gave it 55 on its Intelligence Index and ranked it fourth at publication. This is one organization’s composite metric, not a universal task ranking.
- A 1M context limit does not guarantee latency, quota, or task cost. Measure actual tokens, cache use, retries, and success rate.
- GPT88 routes, pricing, limits, permissions, and features follow the current console and API key; Moonshot list prices do not establish GPT88 billing.
Capabilities
Recommended Scenarios
- Complex coding and terminal tasks
- 3D/CAD modeling
- Financial document analysis
- Long-horizon agents
Endpoint Path
The endpoint path is determined by the model category. Chat, image, video, and audio models use different endpoints.
Send requests with Authorization: Bearer <API_KEY>. See Chat Completions API for the full parameter reference.
API Docs
Headers / Auth
| Field | Type | Required | Description |
|---|---|---|---|
Authorization | string | Required | Send Bearer <GPT88_API_KEY>. Create the API key in the gpt88.cc console. |
Content-Type | string | Required | Request body format. Audio transcription uploads use multipart/form-data.Default: application/json |
Accept | string | Optional | Non-streaming requests return JSON; streaming chat requests return SSE chunks. Default: application/json or text/event-stream |
AuthorizationstringRequiredSendBearer <GPT88_API_KEY>. Create the API key in the gpt88.cc console.Content-TypestringRequiredRequest body format. Audio transcription uploads usemultipart/form-data.Default:application/jsonAcceptstringNon-streaming requests return JSON; streaming chat requests return SSE chunks.Default:application/json or text/event-stream
Chat Protocol Differences
For chat models, the protocol used by the client matters as much as the model name. Claude Code / Anthropic SDK and OpenAI SDK build different request paths.
- Base URL
- https://api.gpt88.cc
- Endpoint
- POST /v1/chat/completions
- Body
- { "model": "kimi-k3.1-pro", "messages": [...] }
- Base URL
- https://api.gpt88.cc
- Endpoint
- POST /v1/messages
- Body
- { "model": "kimi-k3.1-pro", "messages": [...] }
This model is usually best accessed through the OpenAI-compatible protocol. Only use the Anthropic-style path when the target tool explicitly requires it.
Request Parameters
The fields below are generated by model category. Pricing, context limits, rate limits, and available routes should be confirmed in the gpt88.cc console.
| Field | Type | Required | Description |
|---|---|---|---|
model | string | Required | Current model ID: kimi-k3.1-pro. Preserve the exact casing when copying. |
messages | array<Message> | Required | Conversation history. Each message includes role and content. |
stream | boolean | Optional | Enable SSE streaming. Useful for chat interfaces and long responses. Default: false |
temperature | number | Optional | Sampling temperature. Higher values produce more variation; production workloads usually start with a fixed value. Default: 1 |
max_tokens | integer | Optional | Maximum output tokens for this request. Real context limits should be confirmed in the console. |
response_format | object | Optional | Structured output config, for example { "type": "json_object" }. |
tools | array<Tool> | Optional | Function-calling tool definitions. Availability depends on the model and account configuration. |
modelstringRequiredCurrent model ID:kimi-k3.1-pro. Preserve the exact casing when copying.messagesarray<Message>RequiredConversation history. Each message includesroleandcontent.streambooleanEnable SSE streaming. Useful for chat interfaces and long responses.Default:falsetemperaturenumberSampling temperature. Higher values produce more variation; production workloads usually start with a fixed value.Default:1max_tokensintegerMaximum output tokens for this request. Real context limits should be confirmed in the console.response_formatobjectStructured output config, for example{ "type": "json_object" }.toolsarray<Tool>Function-calling tool definitions. Availability depends on the model and account configuration.
Response Fields
Response bodies generally follow OpenAI-compatible shapes. Media models may return async task IDs or resource URLs.
| Field | Type | Required | Description |
|---|---|---|---|
id | string | Required | Unique completion ID for tracing and debugging. |
object | string | Required | Usually chat.completion or a streaming chunk type. |
model | string | Required | Actual model ID that handled inference. |
choices | array<Choice> | Required | Generated choices including message, delta, and finish_reason. |
usage | object | Optional | Token usage statistics. Streaming calls may return this only at the end or in non-streaming mode. |
idstringRequiredUnique completion ID for tracing and debugging.objectstringRequiredUsuallychat.completionor a streaming chunk type.modelstringRequiredActual model ID that handled inference.choicesarray<Choice>RequiredGenerated choices includingmessage,delta, andfinish_reason.usageobjectToken usage statistics. Streaming calls may return this only at the end or in non-streaming mode.
Status Codes
| Field | Type | Required | Description |
|---|---|---|---|
200 | OK | Required | Request succeeded. See the response field table above for the response body shape. |
400 | Bad Request | Optional | Invalid request fields, such as missing required fields, unsupported image size format, or unsupported file type. |
401 | Unauthorized | Optional | API key is missing, invalid, or malformed. |
404 | Not Found | Optional | Endpoint or model not found. Confirm the path is /v1/chat/completions and the model ID is kimi-k3.1-pro. |
429 | Rate Limited | Optional | Rate limit, concurrency cap, or insufficient balance. Check the console for the current allowance. |
5xx | Upstream Error | Optional | Upstream or request failure. Retry with the same Base URL and keep the request ID for debugging. |
200OKRequiredRequest succeeded. See the response field table above for the response body shape.400Bad RequestInvalid request fields, such as missing required fields, unsupported image size format, or unsupported file type.401UnauthorizedAPI key is missing, invalid, or malformed.404Not FoundEndpoint or model not found. Confirm the path is/v1/chat/completionsand the model ID iskimi-k3.1-pro.429Rate LimitedRate limit, concurrency cap, or insufficient balance. Check the console for the current allowance.5xxUpstream ErrorUpstream or request failure. Retry with the same Base URL and keep the request ID for debugging.
Errors and Troubleshooting
401: verifyAuthorizationisBearer <API_KEY>and the key is still valid.404: confirm the endpoint is/v1/chat/completionsand the model IDkimi-k3.1-prois available in the console.429: reduce concurrency, shorten requests, or check balance and quota in the console.5xx: retry with the same Base URL and keep the request ID for debugging.
Request Examples
curl https://api.gpt88.cc/v1/chat/completions \
-H "Authorization: Bearer $GPT88_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "kimi-k3.1-pro",
"messages": [
{"role": "user", "content": "Introduce gpt88.cc in one sentence."}
]
}'Expected response (trimmed example):
{
"id": "chatcmpl-kimi-k3-",
"object": "chat.completion",
"created": 1730000000,
"model": "kimi-k3.1-pro",
"choices": [
{
"index": 0,
"finish_reason": "stop",
"message": { "role": "assistant", "content": "..." }
}
],
"usage": { "prompt_tokens": 24, "completion_tokens": 64, "total_tokens": 88 }
}