LongCat 2.0 is a sparse mixture-of-experts language model from Meituan, with 48 billion active parameters out of 1.6 trillion total. Its published role includes coding, repository-level changes, long-horizon problem solving and agent workflows. Select meituan/longcat-2.0 with POST /v1/chat/completions using model and a messages array. This profile accepts text and produces text or function-call requests within the conversation.
For a repository change, supply the relevant files or excerpts, the behaviour that should change and the constraints the implementation must preserve. Ask for a concrete result, such as a patch, a proposed change sequence or an explanation of how a failure passes through the supplied modules. For document analysis, provide the actual source text and identify the questions the answer must resolve. Label different source passages so the response can connect its conclusions to the supplied material.
The published context window is 1,048,756 tokens, and the model profile lists up to 262,144 completion tokens. Plan the source material, conversation history, tool results and requested answer within the overall context budget. Set max_tokens for the requested output allowance. A large context can hold substantial text, but the task still benefits from explicit file boundaries, the current objective and a description of what a useful answer should contain.
The supported controls include tools and tool_choice for function calling. An application can declare functions for reading a selected file, running an approved check or obtaining a record, then supply the resulting data in subsequent conversation turns. The model can request a function call; your application validates its arguments, performs the permitted action and returns the result. Keep the request, tool result and next answer together when a task spans several steps.
Other published parameters include temperature, top_p, top_k, min_p, stop, seed, frequency_penalty, presence_penalty and repetition_penalty. reasoning and include_reasoning also appear in the supported parameter list. The model profile does not support response_format, so an instruction to produce JSON remains a prompt instruction. Parse and validate any structured text before passing it into code, a database or another workflow.
Use a complete Chat Completions response when the next step needs the assembled answer, or stream text when the application displays it as it arrives. Read message content and any tool calls from the returned choices, preserving usage and response information. Assemble streamed deltas before treating a proposed patch or structured answer as complete. For a code change, evaluate the completed proposal against the supplied requirements and actual checks before applying its result.
", "aboutText": "LongCat 2.0 is a sparse mixture-of-experts language model from Meituan, with 48 billion active parameters out of 1.6 trillion total. Its published role includes coding, repository-level changes, long-horizon problem solving and agent workflows. Select meituan/longcat-2.0 with POST /v1/chat/completions using model and a messages array. This profile accepts text and produces text or function-call requests within the conversation.\n\nFor a repository change, supply the relevant files or excerpts, the behaviour that should change and the constraints the implementation must preserve. Ask for a concrete result, such as a patch, a proposed change sequence or an explanation of how a failure passes through the supplied modules. For document analysis, provide the actual source text and identify the questions the answer must resolve. Label different source passages so the response can connect its conclusions to the supplied material.\n\nThe published context window is 1,048,756 tokens, and the model profile lists up to 262,144 completion tokens. Plan the source material, conversation history, tool results and requested answer within the overall context budget. Set max_tokens for the requested output allowance. A large context can hold substantial text, but the task still benefits from explicit file boundaries, the current objective and a description of what a useful answer should contain.\n\nThe supported controls include tools and tool_choice for function calling. An application can declare functions for reading a selected file, running an approved check or obtaining a record, then supply the resulting data in subsequent conversation turns. The model can request a function call; your application validates its arguments, performs the permitted action and returns the result. Keep the request, tool result and next answer together when a task spans several steps.\n\nOther published parameters include temperature, top_p, top_k, min_p, stop, seed, frequency_penalty, presence_penalty and repetition_penalty. reasoning and include_reasoning also appear in the supported parameter list. The model profile does not support response_format, so an instruction to produce JSON remains a prompt instruction. Parse and validate any structured text before passing it into code, a database or another workflow.\n\nUse a complete Chat Completions response when the next step needs the assembled answer, or stream text when the application displays it as it arrives. Read message content and any tool calls from the returned choices, preserving usage and response information. Assemble streamed deltas before treating a proposed patch or structured answer as complete. For a code change, evaluate the completed proposal against the supplied requirements and actual checks before applying its result.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "8d9c479221fee58cbfd1277ad4f89e3ba5a00debb61ca86782b42552c5697eb8", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "meituan/longcat-2.0LongCat 2.0 is Meituan’s text model for coding, repository-level changes, extended problem solving and application-controlled agent workflows. Its published context window is 1,048,756 tokens. Use the exact meituan/longcat-2.0 ID with Chat Completions, supplying the relevant code, documents and tool results as text.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
LongCat 2.0 is a sparse mixture-of-experts language model from Meituan, with 48 billion active parameters out of 1.6 trillion total. Its published role includes coding, repository-level changes, long-horizon problem solving and agent workflows. Select meituan/longcat-2.0 with POST /v1/chat/completions using model and a messages array. This profile accepts text and produces text or function-call requests within the conversation.
For a repository change, supply the relevant files or excerpts, the behaviour that should change and the constraints the implementation must preserve. Ask for a concrete result, such as a patch, a proposed change sequence or an explanation of how a failure passes through the supplied modules. For document analysis, provide the actual source text and identify the questions the answer must resolve. Label different source passages so the response can connect its conclusions to the supplied material.
The published context window is 1,048,756 tokens, and the model profile lists up to 262,144 completion tokens. Plan the source material, conversation history, tool results and requested answer within the overall context budget. Set max_tokens for the requested output allowance. A large context can hold substantial text, but the task still benefits from explicit file boundaries, the current objective and a description of what a useful answer should contain.
The supported controls include tools and tool_choice for function calling. An application can declare functions for reading a selected file, running an approved check or obtaining a record, then supply the resulting data in subsequent conversation turns. The model can request a function call; your application validates its arguments, performs the permitted action and returns the result. Keep the request, tool result and next answer together when a task spans several steps.
Other published parameters include temperature, top_p, top_k, min_p, stop, seed, frequency_penalty, presence_penalty and repetition_penalty. reasoning and include_reasoning also appear in the supported parameter list. The model profile does not support response_format, so an instruction to produce JSON remains a prompt instruction. Parse and validate any structured text before passing it into code, a database or another workflow.
Use a complete Chat Completions response when the next step needs the assembled answer, or stream text when the application displays it as it arrives. Read message content and any tool calls from the returned choices, preserving usage and response information. Assemble streamed deltas before treating a proposed patch or structured answer as complete. For a code change, evaluate the completed proposal against the supplied requirements and actual checks before applying its result.
POST /v1/chat/completionstexttext| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits meituan/longcat-2.0 | Default— |
Fieldmessages | Typearray | RequirementRequired | Values & limits | Default— |
Fieldstream | Typeboolean | RequirementOptional | Values & limits | Defaultfalse |
Fieldmax_tokens | Typeinteger | RequirementOptional | Values & limits Minimum: 1 | Default— |
Fieldmax_completion_tokens | Typeinteger | RequirementOptional | Values & limits Minimum: 1 | Default— |
Fieldn | Typeinteger | RequirementOptional | Values & limits Minimum: 1 | Default— |
Fieldtemperature | Typenumber | RequirementOptional | Values & limits | Default— |
Fieldtop_p | Typenumber | RequirementOptional | Values & limits | Default— |
Fieldseed | Typeinteger | RequirementOptional | Values & limits | Default— |
Fieldstop | Type | RequirementOptional | Values & limits | Default— |
Fieldfrequency_penalty | Typenumber | RequirementOptional | Values & limits | Default— |
Fieldpresence_penalty | Typenumber | RequirementOptional | Values & limits | Default— |
Fielduser | Typestring | RequirementOptional | Values & limits | Default— |
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, messages |
Parameteroptional | Contractstream, max_tokens, max_completion_tokens, n, temperature, top_p, seed, stop, frequency_penalty, presence_penalty, user |
Parametermaterial_types | Contracttext |
Parameterconditions | Contract |
Lifecycle: synchronous_json_or_sse
Tariff references do not add request options. Supported parameters are listed for the selected method.
| Configuration | Rate schedule | Charge |
|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Charge Input · Input tokens $0.0015 / 1K tokens Output · Output tokens $0.006 / 1K tokens Input · Cache read $0.00003 / 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}"\nexport AILOOT_API_KEY\npython3 - <<'PY_REQUEST'\nimport json,os\nfrom pathlib import Path\np=json.loads('{"model": "meituan/longcat-2.0", "messages": [{"role": "user", "content": "Summarize the supplied text in three concise points."}], "stream": false}')\n\nPath("request.json").write_text(json.dumps(p,ensure_ascii=False))\nPY_REQUEST\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/chat/completions \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \\\n --data-binary @request.json -D response-headers.txt -o result.json\n# Submit once. Retain the complete result, original identifiers and every response header.\nJSON or supported SSE
Keep every complete returned response, file and content part.
Retain the complete response, all actual results, original identifiers, usage and response headers.
Preserve the original response, headers and X-Client-Request-ID. An uncertain outcome does not authorize another creation.
Ailoot Ultra meituan/longcat-2.0
Use the method paths shown above.