Kimi K3 is Moonshot AI’s open-weight multimodal agentic model for long-horizon coding, knowledge work and reasoning. It combines text with native visual understanding of images and video and produces a textual answer or tool request. The manufacturer highlights extended engineering sessions, large repositories and tasks that use screenshots or visual feedback alongside code. A useful brief defines the desired artifact, the evidence to use and the condition that marks the work complete.
The model card describes a sparse Mixture of Experts with 2.8 trillion total parameters and 104 billion activated parameters. Its Stable LatentMoE design selects 16 of 896 experts per token, using Kimi Delta Attention and Attention Residuals together with gated attention. The exact context length is 1,048,576 tokens. This is room for a substantial task context, not a reason to discard source boundaries or the space needed for the result.
The published native artifact uses quantization-aware training with MXFP4 weights and MXFP8 activations. That is the manufacturer’s release format, distinct from a separately supplied quantized edition or a claim about how a particular route serves the model. Open weights and a large parameter count do not turn the active-parameter figure into the total storage or hardware requirement.
Provide the relevant repository material, the existing behavior, the requested change and the compatibility constraints. Identify the files or interface that the result must affect, the checks that determine success and any supplied error or input that exposes the problem. A useful result can be a focused code change with an explanation and evidence from the checks that actually ran, rather than a description of actions that were never performed.
For a visual development task, include a screenshot or a clear view of the intended result with the relevant code and a specific discrepancy. The maker describes workflows spanning frontend work, games and CAD that use visual feedback. Ask for the change that connects the code to the observed result, and retain the reference so the delivered artifact can be checked against it.
The producer’s quickstart uses typed content objects for visual messages; content is an array, not a serialized representation of that array. Its image workflow uses encoded image data or a supported file reference rather than a public image address. The video example uploads a video file and supplies the resulting reference with a question about its content. Give a legible source and specify the observation, interval or relationship that matters. The producer’s vision workflow accepts JPEG, PNG, GIF, WebP, BMP, HEIC and HEIF images, and MP4, MPEG, MOV, AVI, FLV, MPG, WebM, WMV and 3GPP video. Animated GIF or WebP can be decoded as video. Supply SVG source as text. The maker recommends images up to 4096 × 2160 and video up to 1920 × 1080; these are resolution recommendations, not rejection thresholds. Keep the request body within the documented 100M size bound and upload large or repeatedly used media as files.
For document-heavy research, label the sources and state the questions the final report should answer. For a video explanation, identify the events or sequence to analyze rather than requesting unrestricted commentary. K3 uses visual content as evidence for reasoning and returns text or tool requests. An application can pass those requests to media tools to create separate image or video artifacts.
K3’s producer interface always has thinking enabled. The top-level reasoning_effort setting accepts low, high and max, with max as the default. These choices are model-specific; a non-thinking setting or an effort value from another family should not be assumed. The maker’s migration guidance distinguishes K3 from K2.x by using reasoning_effort rather than carrying over the older thinking configuration.
The producer documents separate reasoning_content and final-answer content in streamed results. For a multi-turn conversation or tool workflow, it requires the complete returned assistant message to be passed back unchanged, including reasoning_content and tool_calls. Retaining only the visible final answer loses information that the model’s preserved-thinking workflow expects on the next step.
The quickstart documents strict JSON-schema output for the final message content. Define the fields and their meanings around the artifact the application needs, and parse that final content rather than combining it with the reasoning field. A structured result can represent extracted information from supplied material or a defined report format; the schema constrains its shape, while the source evidence determines whether its values are correct.
Partial mode can continue a supplied text prefix. The producer’s example places a partial assistant message at the end of the history and combines that prefix with the returned continuation for display. Use this when the required artifact has a meaningful fixed beginning, keeping the prefix distinct from the generated remainder.
K3 supports custom function tools. The producer’s example requires a tool on the first turn, preserves the complete assistant message, executes each returned call and appends a matching tool result before requesting the final answer. A proposed call is not evidence that the operation succeeded; the actual returned result becomes the evidence for the next step.
Its dynamic-loading workflow introduces a complete tool definition at a specific point in message history. The definition needs its name, purpose and parameters, and it must remain in subsequent history because the server does not retain that declaration independently. Keep tool capabilities, supplied arguments and real observations associated so a long task can continue from the work already completed.
The producer documents a default completion allowance of 131,072 tokens, configurable up to 1,048,576 within the model’s overall context constraints. Its current K3 API fixes temperature at 1.0, top_p at 0.95, one result, and zero presence and frequency penalties, directing callers to omit those sampling controls. These are the exact producer profile’s settings, not a transferable list of adjustable controls.
Context caching is automatic for eligible repeated prefixes, with documented 5-minute and 1-hour TTL choices and 5 minutes as the default. Partial cache blocks remain misses. Keep reusable context stable and check actual usage rather than asserting a cache hit from repeated text alone. For the final artifact, retain the supplied sources, actual tool evidence and required output structure, and check that a long answer or engineering result meets the stated completion criteria.
", "aboutText": "Kimi K3 is Moonshot AI’s open-weight multimodal agentic model for long-horizon coding, knowledge work and reasoning. It combines text with native visual understanding of images and video and produces a textual answer or tool request. The manufacturer highlights extended engineering sessions, large repositories and tasks that use screenshots or visual feedback alongside code. A useful brief defines the desired artifact, the evidence to use and the condition that marks the work complete.\n\n### Architecture and long context\n\nThe model card describes a sparse Mixture of Experts with 2.8 trillion total parameters and 104 billion activated parameters. Its Stable LatentMoE design selects 16 of 896 experts per token, using Kimi Delta Attention and Attention Residuals together with gated attention. The exact context length is 1,048,576 tokens. This is room for a substantial task context, not a reason to discard source boundaries or the space needed for the result.\n\nThe published native artifact uses quantization-aware training with MXFP4 weights and MXFP8 activations. That is the manufacturer’s release format, distinct from a separately supplied quantized edition or a claim about how a particular route serves the model. Open weights and a large parameter count do not turn the active-parameter figure into the total storage or hardware requirement.\n\n### Prepare a substantial coding task\n\nProvide the relevant repository material, the existing behavior, the requested change and the compatibility constraints. Identify the files or interface that the result must affect, the checks that determine success and any supplied error or input that exposes the problem. A useful result can be a focused code change with an explanation and evidence from the checks that actually ran, rather than a description of actions that were never performed.\n\nFor a visual development task, include a screenshot or a clear view of the intended result with the relevant code and a specific discrepancy. The maker describes workflows spanning frontend work, games and CAD that use visual feedback. Ask for the change that connects the code to the observed result, and retain the reference so the delivered artifact can be checked against it.\n\n### Images, video and knowledge-work preparation\n\nThe producer’s quickstart uses typed content objects for visual messages; content is an array, not a serialized representation of that array. Its image workflow uses encoded image data or a supported file reference rather than a public image address. The video example uploads a video file and supplies the resulting reference with a question about its content. Give a legible source and specify the observation, interval or relationship that matters. The producer’s vision workflow accepts JPEG, PNG, GIF, WebP, BMP, HEIC and HEIF images, and MP4, MPEG, MOV, AVI, FLV, MPG, WebM, WMV and 3GPP video. Animated GIF or WebP can be decoded as video. Supply SVG source as text. The maker recommends images up to 4096 × 2160 and video up to 1920 × 1080; these are resolution recommendations, not rejection thresholds. Keep the request body within the documented 100M size bound and upload large or repeatedly used media as files.\n\nFor document-heavy research, label the sources and state the questions the final report should answer. For a video explanation, identify the events or sequence to analyze rather than requesting unrestricted commentary. K3 uses visual content as evidence for reasoning and returns text or tool requests. An application can pass those requests to media tools to create separate image or video artifacts.\n\n### Thinking is always enabled\n\nK3’s producer interface always has thinking enabled. The top-level reasoning_effort setting accepts low, high and max, with max as the default. These choices are model-specific; a non-thinking setting or an effort value from another family should not be assumed. The maker’s migration guidance distinguishes K3 from K2.x by using reasoning_effort rather than carrying over the older thinking configuration.\n\nThe producer documents separate reasoning_content and final-answer content in streamed results. For a multi-turn conversation or tool workflow, it requires the complete returned assistant message to be passed back unchanged, including reasoning_content and tool_calls. Retaining only the visible final answer loses information that the model’s preserved-thinking workflow expects on the next step.\n\n### Structured final answers and partial continuation\n\nThe quickstart documents strict JSON-schema output for the final message content. Define the fields and their meanings around the artifact the application needs, and parse that final content rather than combining it with the reasoning field. A structured result can represent extracted information from supplied material or a defined report format; the schema constrains its shape, while the source evidence determines whether its values are correct.\n\nPartial mode can continue a supplied text prefix. The producer’s example places a partial assistant message at the end of the history and combines that prefix with the returned continuation for display. Use this when the required artifact has a meaningful fixed beginning, keeping the prefix distinct from the generated remainder.\n\n### Tools and continuity of their results\n\nK3 supports custom function tools. The producer’s example requires a tool on the first turn, preserves the complete assistant message, executes each returned call and appends a matching tool result before requesting the final answer. A proposed call is not evidence that the operation succeeded; the actual returned result becomes the evidence for the next step.\n\nIts dynamic-loading workflow introduces a complete tool definition at a specific point in message history. The definition needs its name, purpose and parameters, and it must remain in subsequent history because the server does not retain that declaration independently. Keep tool capabilities, supplied arguments and real observations associated so a long task can continue from the work already completed.\n\n### Output controls and repeated context\n\nThe producer documents a default completion allowance of 131,072 tokens, configurable up to 1,048,576 within the model’s overall context constraints. Its current K3 API fixes temperature at 1.0, top_p at 0.95, one result, and zero presence and frequency penalties, directing callers to omit those sampling controls. These are the exact producer profile’s settings, not a transferable list of adjustable controls.\n\nContext caching is automatic for eligible repeated prefixes, with documented 5-minute and 1-hour TTL choices and 5 minutes as the default. Partial cache blocks remain misses. Keep reusable context stable and check actual usage rather than asserting a cache hit from repeated text alone. For the final artifact, retain the supplied sources, actual tool evidence and required output structure, and check that a long answer or engineering result meets the stated completion criteria.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "9fe93228dcf00e8ab0106bab4d7d334ab268746b8514200e49e5acd694358c43", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "moonshotai/kimi-k3:batchKimi K3 is Moonshot AI’s native multimodal reasoning model for long coding tasks and knowledge work. It reads text, images and video, produces text, and supports tool-driven workflows with a 1,048,576-token context and preserved thinking history across steps.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
Kimi K3 is Moonshot AI’s open-weight multimodal agentic model for long-horizon coding, knowledge work and reasoning. It combines text with native visual understanding of images and video and produces a textual answer or tool request. The manufacturer highlights extended engineering sessions, large repositories and tasks that use screenshots or visual feedback alongside code. A useful brief defines the desired artifact, the evidence to use and the condition that marks the work complete.
The model card describes a sparse Mixture of Experts with 2.8 trillion total parameters and 104 billion activated parameters. Its Stable LatentMoE design selects 16 of 896 experts per token, using Kimi Delta Attention and Attention Residuals together with gated attention. The exact context length is 1,048,576 tokens. This is room for a substantial task context, not a reason to discard source boundaries or the space needed for the result.
The published native artifact uses quantization-aware training with MXFP4 weights and MXFP8 activations. That is the manufacturer’s release format, distinct from a separately supplied quantized edition or a claim about how a particular route serves the model. Open weights and a large parameter count do not turn the active-parameter figure into the total storage or hardware requirement.
Provide the relevant repository material, the existing behavior, the requested change and the compatibility constraints. Identify the files or interface that the result must affect, the checks that determine success and any supplied error or input that exposes the problem. A useful result can be a focused code change with an explanation and evidence from the checks that actually ran, rather than a description of actions that were never performed.
For a visual development task, include a screenshot or a clear view of the intended result with the relevant code and a specific discrepancy. The maker describes workflows spanning frontend work, games and CAD that use visual feedback. Ask for the change that connects the code to the observed result, and retain the reference so the delivered artifact can be checked against it.
The producer’s quickstart uses typed content objects for visual messages; content is an array, not a serialized representation of that array. Its image workflow uses encoded image data or a supported file reference rather than a public image address. The video example uploads a video file and supplies the resulting reference with a question about its content. Give a legible source and specify the observation, interval or relationship that matters. The producer’s vision workflow accepts JPEG, PNG, GIF, WebP, BMP, HEIC and HEIF images, and MP4, MPEG, MOV, AVI, FLV, MPG, WebM, WMV and 3GPP video. Animated GIF or WebP can be decoded as video. Supply SVG source as text. The maker recommends images up to 4096 × 2160 and video up to 1920 × 1080; these are resolution recommendations, not rejection thresholds. Keep the request body within the documented 100M size bound and upload large or repeatedly used media as files.
For document-heavy research, label the sources and state the questions the final report should answer. For a video explanation, identify the events or sequence to analyze rather than requesting unrestricted commentary. K3 uses visual content as evidence for reasoning and returns text or tool requests. An application can pass those requests to media tools to create separate image or video artifacts.
K3’s producer interface always has thinking enabled. The top-level reasoning_effort setting accepts low, high and max, with max as the default. These choices are model-specific; a non-thinking setting or an effort value from another family should not be assumed. The maker’s migration guidance distinguishes K3 from K2.x by using reasoning_effort rather than carrying over the older thinking configuration.
The producer documents separate reasoning_content and final-answer content in streamed results. For a multi-turn conversation or tool workflow, it requires the complete returned assistant message to be passed back unchanged, including reasoning_content and tool_calls. Retaining only the visible final answer loses information that the model’s preserved-thinking workflow expects on the next step.
The quickstart documents strict JSON-schema output for the final message content. Define the fields and their meanings around the artifact the application needs, and parse that final content rather than combining it with the reasoning field. A structured result can represent extracted information from supplied material or a defined report format; the schema constrains its shape, while the source evidence determines whether its values are correct.
Partial mode can continue a supplied text prefix. The producer’s example places a partial assistant message at the end of the history and combines that prefix with the returned continuation for display. Use this when the required artifact has a meaningful fixed beginning, keeping the prefix distinct from the generated remainder.
K3 supports custom function tools. The producer’s example requires a tool on the first turn, preserves the complete assistant message, executes each returned call and appends a matching tool result before requesting the final answer. A proposed call is not evidence that the operation succeeded; the actual returned result becomes the evidence for the next step.
Its dynamic-loading workflow introduces a complete tool definition at a specific point in message history. The definition needs its name, purpose and parameters, and it must remain in subsequent history because the server does not retain that declaration independently. Keep tool capabilities, supplied arguments and real observations associated so a long task can continue from the work already completed.
The producer documents a default completion allowance of 131,072 tokens, configurable up to 1,048,576 within the model’s overall context constraints. Its current K3 API fixes temperature at 1.0, top_p at 0.95, one result, and zero presence and frequency penalties, directing callers to omit those sampling controls. These are the exact producer profile’s settings, not a transferable list of adjustable controls.
Context caching is automatic for eligible repeated prefixes, with documented 5-minute and 1-hour TTL choices and 5 minutes as the default. Partial cache blocks remain misses. Keep reusable context stable and check actual usage rather than asserting a cache hit from repeated text alone. For the final artifact, retain the supplied sources, actual tool evidence and required output structure, and check that a long answer or engineering result meets the stated completion criteria.
POST /v1/batchestexttext| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldendpoint | Typestring | RequirementRequired | Values & limits /v1/chat/completions | Default— |
Fieldmodel | Typestring | RequirementRequired | Values & limits moonshotai/kimi-k3:batch | Default— |
Fieldrequests | Typebatch_item[] | RequirementRequired | Values & limits Minimum items: 1 | Default— |
Fieldrequests[].custom_id | Typestring | RequirementRequired | Values & limits | Default— |
Fieldrequests[].body.messages | Typemessage[] | RequirementRequired | Values & limits | Default— |
Fieldcompletion_window | Typestring | RequirementOptional | Values & limits 24h | Default— |
Fieldprovider | Typeobject|null | RequirementOptional | Values & limits | Default— |
Fieldrequests[].body.model | Typestring | RequirementOptional | Values & limits moonshotai/kimi-k3:batch, moonshotai/kimi-k3 | Default— |
Fieldprovider.only | Typestring[] | RequirementOptional | Values & limits deepinfra/bf16 | Default— |
Fieldprovider.allow_fallbacks | Typeboolean|null | RequirementOptional | Values & limits false, null | Default— |
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractendpoint, model, requests |
Parametermaterial_types | Contracttext |
Parameterrepresentation | Contractinline requests[]; each item has custom_id and body |
Parameterrequest_endpoint_profile | Contract/v1/chat/completions |
Parameterfile_material | ContractCaller may read actual UTF-8 JSONL locally into requests[]. No upload purpose, input_file_id or file reference is used. Missing/empty customer material stops preparation before POST. |
Parameterserialization_order | Contractendpoint, model, provider (if supplied), completion_window (if supplied), requests last |
Parameteroptional_controls | Contractprovider.only, provider.allow_fallbacks, completion_window |
Parameterschema_scope | ContractText Chat Completions bodies in the documented inline Batch envelope. |
Lifecycle: asynchronous
GET /v1/batches/{operation_id} · actual original create response.id; same user/key/group
Tariff references do not add request options. Supported parameters are listed for the selected method.
Match each charge to the conditions shown. Use one rate for each set of alternative configurations.
| Configuration | Rate schedule | Context tokens, more than | Context tokens, up to and including | Charge |
|---|---|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Context tokens, more than— | Context tokens, up to and includingNo upper bound | Charge Input · Input tokens $0.00456 / 1K tokens Output · Output tokens $0.0228 / 1K tokens Input · Cache read $0.000456 / 1K tokens Input · Cache write — / 1K tokens Input · Cache write, 1 hour — / 1K tokens |
| ConfigurationRequest-length tier 1 | Rate schedule— | Context tokens, more than0 | Context tokens, up to and includingNo upper bound | Charge Input · Input tokens $0.00456 / 1K tokens Output · Output tokens $0.0228 / 1K tokens Input · Cache read $0.000456 / 1K tokens Input · Cache write — / 1K tokens Input · Cache write, 1 hour — / 1K tokens |
Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →
set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\npython3 - <<'PY_REQUEST'\nimport json\nfrom pathlib import Path\nbody=json.loads('{"endpoint":"/v1/chat/completions","model":"moonshotai/kimi-k3:batch","requests":[{"custom_id":"req-0001","body":{"messages":[{"role":"user","content":"Hello!"}],"max_tokens":16}}]}')\nPath("batch-request.json").write_text(json.dumps(body,ensure_ascii=False),encoding="utf-8")\nPY_REQUEST\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/batches \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \\\n --data-binary @batch-request.json -D batch-response-headers.txt -o batch-create-response.json\nimport json, os\nfrom pathlib import Path\nfrom urllib.request import Request, urlopen\n\ndef prepare_requests(customer_path):\n path = Path(customer_path)\n if not path.is_file(): raise ValueError("Customer JSONL file is missing")\n items = [json.loads(line) for line in path.read_text(encoding="utf-8").splitlines() if line.strip()]\n if not items: raise ValueError("Customer JSONL contains no requests")\n ids = set()\n for item in items:\n if set(item) != {"custom_id", "body"}: raise ValueError("Each item needs custom_id and body")\n cid = item["custom_id"]\n if not isinstance(cid, str) or not cid.strip() or cid in ids: raise ValueError("custom_id must be nonempty and unique")\n ids.add(cid)\n if not isinstance(item["body"], dict) or not item["body"].get("messages"): raise ValueError("Supply actual text messages")\n supplied_model = item["body"].get("model")\n if supplied_model is not None and supplied_model not in ['moonshotai/kimi-k3:batch', 'moonshotai/kimi-k3']: raise ValueError("body.model must be an exact documented caller or wire ID")\n return {"endpoint":"/v1/chat/completions", "model":"moonshotai/kimi-k3:batch", "requests":items}\n\nif __name__ == "__main__":\n material = os.environ.get("AILOOT_BATCH_REQUESTS_JSONL", "")\n if not material: raise SystemExit("Set AILOOT_BATCH_REQUESTS_JSONL to your actual customer file")\n body = prepare_requests(material)\n key = os.environ.get("AILOOT_API_KEY", "")\n if not key: raise SystemExit("Set AILOOT_API_KEY")\n request = Request("https://api.ailoot.ai/v1/batches", data=json.dumps(body, ensure_ascii=False).encode("utf-8"), headers={"Authorization":"Bearer " + key, "Content-Type":"application/json"}, method="POST")\n with urlopen(request) as response:\n raw = response.read()\n Path("batch-create-response.json").write_bytes(raw)\n print(raw.decode("utf-8"))\nimport json\nfrom pathlib import Path\nraw = Path("batch-status-response.json").read_bytes()\nresponse = json.loads(raw)\nif response.get("status") != "completed":\n raise SystemExit("Keep the original operation; read its status without resubmitting")\nresults = response.get("results")\nif not isinstance(results, list) or not results:\n raise SystemExit("Preserve the original response; completed results are missing")\nPath("batch-results.jsonl").write_text("".join(json.dumps(item, ensure_ascii=False) + "\\n" for item in results), encoding="utf-8")\n# Preserve batch-status-response.json with aggregate usage and every result/error.\ninline results[].response.body JSON
GET /v1/batches/{operation_id}set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\nBATCH_OPERATION_ID="$(python3 - <<'PY_ID'\nimport json\nfrom pathlib import Path\nfrom urllib.parse import quote\nresponse = json.loads(Path("batch-create-response.json").read_text(encoding="utf-8"))\noperation = response.get("id")\nif not isinstance(operation, str) or not operation: raise SystemExit("No actual original operation ID; preserve the response and do not resubmit")\nprint(quote(operation, safe=""))\nPY_ID\n)"\ncurl --fail-with-body --silent --show-error "https://api.ailoot.ai/v1/batches/$BATCH_OPERATION_ID" \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -o batch-status-response.json\nKeep every complete returned response, file and content part.
Preserve the full original status JSON, every result/custom_id and complete response or error body. Save completed results[] as JSONL without filtering.
Preserve the original operation ID. 503 result_pending_check has X-Should-Retry:false; never resubmit an unknown original batch.
| Field | Type |
|---|---|
Fieldresults[].custom_id | Typestring |
Fieldresults[].response.body.choices[].message.content | Typestring|null |
Fieldresults[].error | Typeobject|null |
Fieldusage | Typeobject|null |
Fieldid | Typestring |
Fieldmodel | Typestring |
Fieldendpoint | Typestring |
Fieldstatus | Typestring |
Fieldrequest_counts | Typeobject |
Fieldresults[].id | Typestring |
Fieldresults[].response.status_code | Typeinteger |
Fieldresults[].response.request_id | Typestring |
| Response | Condition | Next step |
|---|---|---|
Response400 · invalid_request_error | ConditionInvalid documented inline envelope, duplicate keys, item identity, or configured model capabilities conflict. | Next stepCorrect the indicated fields before any new submission. |
Response401 · authentication_error | ConditionInvalid API key. | Next stepUse the authorized Ailoot key. |
Response403 · permission_error | ConditionBatch group unavailable. | Next stepCheck key/group entitlement. |
Response422 · invalid_request_error | ConditionBatch uses balance billing; subscription creation is rejected. | Next stepUse the authorized balance-billed group. |
Response422 · price_unavailable | ConditionBatch input cannot be quoted. | Next stepPreserve response; use documented family input. |
Response402 · billing_error | ConditionBatch reserve unavailable. | Next stepResolve admission before a new request. |
Response503 · price_unavailable | ConditionBatch method price/native rates unavailable. | Next stepPreserve response; do not substitute prices. |
Response503 · api_error | ConditionExact supplier route unavailable. | Next stepPreserve response for route repair. |
Response503 · result_pending_check | ConditionOriginal result requires checking; X-Should-Retry:false. | Next stepKeep original operation_id/id and read its status; never repeat original POST. |
Response404 · not_found | ConditionBatch status operation absent or owned by another identity. | Next stepUse exact original id and same user/key/group. |
Ailoot Ultra moonshotai/kimi-k3:batch
Use the method paths shown above.