Codebase work
Submit relevant files, interface constraints, and acceptance criteria, let the model analyze cross-module changes, then have your application run tests.
Kimi K3.1 Pro is Moonshot's flagship model, with native support for visual understanding and million-token context. It is suitable for codebase analysis, cross-document research, and tasks requiring multi-step reasoning. Use Chat Completions on Ace Data Cloud to submit messages and read usage.
Point the Base URL to api.acedata.cloud, configure your platform API key and the model ID below, and use your compatible SDK or client.
api.acedata.cloudkimi-k3.1-proimport os
from openai import OpenAI
client = OpenAI(
api_key=os.environ["ACEDATACLOUD_API_KEY"],
base_url="https://api.acedata.cloud/v1",
)
response = client.chat.completions.create(
model="kimi-k3.1-pro",
messages=[{"role": "user", "content": "Hello!"}],
)
print(response.choices[0].message.content)Choose an available protocol for this model. OpenAI SDK uses a Base URL ending in /v1; Anthropic SDK uses the root URL. See each guide for protocol-specific parameters, tools and response formats.
Verify the request format before selecting a model.
Provide sufficient context and verifiable objectives for complex tasks.
Submit relevant files, interface constraints, and acceptance criteria, let the model analyze cross-module changes, then have your application run tests.
Ask clear questions using text, charts, or screenshots, and require it to identify evidence, assumptions, and items to be verified.
First verify the API with a short message, then gradually add context.
POST /kimi/chat/completions
{"model":"kimi-k3.1-pro","messages":[{"role":"user","content":"请总结这段代码的关键风险"}],"reasoning_effort":"low"}The model always has reasoning enabled. Reasoning effort can be set to low, high, or max; do not pass settings that disable reasoning. For image input, use image_url content blocks in messages.
Treat model output as analysis that needs to be verified.
Costs depend on actual token usage and the purchased Credit plan.
View the current input, output, and cache hit prices in the Pricing card in the model catalog. Long conversations should limit the history messages sent; cache hits and writes are subject to actual usage fields and billing.
Understand the division of responsibilities between model capabilities and application execution.
Quickly troubleshoot invocation and model selection issues.
No. This model always has reasoning enabled, with low, high, or max intensity available.
Use an image_url image block in the content of messages and submit it together with the text question. First use a small image to verify the format and permissions.
The examples on this page use Chat Completions. Before choosing another protocol, review the separate model list for that API.
Limit irrelevant history, choose an appropriate output budget, and check the Pricing card for prices for the current plan.
Save relevant message history; if the response contains reasoning_content or tool_calls, return the complete assistant message in the next turn and verify the tool results.
Choose a development approach or application suited to this model and follow its setup guide.
OpenAI Chat Completions API
SDK installation, authentication and examplesUsing Ace Data Cloud with Cherry Studio
Chat client setup · Base URL, API key and modelUsing Ace Data Cloud with ChatBox
Chat client setup · Base URL, API key and modelThis is only a basic call example. See the full docs for more parameters and advanced usage.
View Docs