Source: https://ailoot.ai/models/en/qwen-long/
Canonical: https://ailoot.ai/models/en/qwen-long/
Language: en

# Qwen-Long

[Markdown](https://ailoot.ai/models/en/qwen-long/index.md) · [JSON](https://ailoot.ai/models/en/qwen-long/facts.json)

## [Qwen-Long](https://ailoot.ai/models/en/qwen-long/)

Qwen-Long is built for questions across large document collections. Its maker documents a file-upload and reference workflow with up to 10 million tokens of document context, comparison across files and structured text answers.

- [**Ailoot Ultra · OpenAI Chat** `POST /v1/chat/completions` `qwen-long`](https://ailoot.ai/models/en/qwen-long/#method-0)
- [**Ailoot Ultra · Anthropic Messages** `POST /v1/messages` `qwen-long`](https://ailoot.ai/models/en/qwen-long/#method-1)

About the model

This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.

Qwen-Long is the Qwen document-processing line for finding information, comparing material and answering questions across a large text corpus. Its distinctive feature is a documented file-upload and reference workflow that handles up to 10 million tokens. The task is not simply to produce a longer chat reply: it is to keep a substantial collection of source documents available while asking focused questions about them.

How the document workflow works

The maker describes two stages. First, upload the selected files and let the document parser finish. The resulting references identify the prepared documents. Second, ask a question while including the references for the material that should be considered. The model performs inference over the text associated with those documents. This separates document preparation from the question and avoids resending the complete file in every conversation turn.

Prepare a single document when the goal is a summary, an explanation of a section or extraction of specific conditions. Name the sections that matter and request an output with an observable purpose. For example: provide a product specification, ask for the operating conditions it explicitly lists, and request a short table containing the condition, the source section and any missing detail. Those field names are an illustrative design for the result, not a built-in fixed schema.

Multiple documents and follow-up questions

The documented workflow accepts several prepared files in the same request. This supports comparison across documents: identify a feature in each specification, distinguish shared statements from differences, and collect unresolved questions. Up to 100 file references can be included in one request. Select the files relevant to the question rather than assuming that the presence of a large context defines what should be compared.

The maker also demonstrates adding a new document after an initial answer. Keep the earlier answer in the conversation, add the new source and ask a follow-up such as how the two descriptions differ. In an application, distinguish the prior response from the newly supplied evidence. A useful result can be a comparison table with separate columns for each document and an explanation of disagreements, rather than a merged summary that loses the source of each statement.

Plain-text input is another documented route. Smaller materials can be supplied directly as text instead of uploaded file references. The producer guide requires the reference-based route when inline document content exceeds 1 million tokens because of request-size limits. That boundary is separate from the 10-million-token document context: a large supported corpus is not a promise that one equally large raw text payload will be accepted.

Formats, context and output

The document service lists TXT, DOCX, PDF, XLSX, EPUB, MOBI, MD, CSV and JSON, together with BMP, PNG, JPG/JPEG and GIF. Uploaded image files are limited to 20 MB; other supported files are limited to 150 MB. These are limits of the maker's document-preparation workflow, not a claim that the language model directly reasons over every binary format without parsing.

The published specification gives a 10,000,000-token context and maximum input, with up to 32,768 output tokens. In the documented file-reference conversation format, the user question has a separate limit of 9,000 tokens when a second system message supplies the documents. Keep the question concise and reserve the bulk of the document context for the source material. Long-context input and answer length solve different problems: a large corpus can still call for a short, tightly structured result.

The maker's FAQ documents JSON Schema-based structured output for Qwen-Long and its snapshots. This is useful for repeated extraction tasks that need the same fields across a collection. Specify the required information, the type of each field and what to do when the source does not contain a value. The service also documents asynchronous batch processing, which is an alternative submission workflow rather than an additional reasoning mode.

A practical document comparison

Prepare the relevant specifications and identify their roles before asking: which is the existing description, which is the proposed replacement, and which requirements are mandatory. Request a result with shared conditions, conflicting statements, missing information and source locations. A subsequent question can ask the model to turn that result into a concise explanation for a colleague while preserving the original distinctions.

Important preparation limits

Parsing must finish before the prepared files are used; larger documents can require more parsing time. The model's documented inference uses extracted text, so the completeness and readability of that prepared content matter. Keep file selection, the question and the required output explicit. Qwen-Long's document capacity should not be substituted for the limits of a different Qwen edition, a raw inline request or the final answer.

Practical task

### Compare maintenance documents

Technical example in English

```
Compare maintenance documents

Compare these source extracts for a maintenance checklist. Manual M1 section 4: Inspect the filter every week; replace it after 500 hours. Manual M2 section 6: Inspect the filter every week; replace it after 400 hours in dusty conditions. Keep shared rules, conditional differences and missing guidance separate. Do not assume which manual overrides the other.
```

#### Expected result

```
A comparison table with shared rule, condition, replacement interval, source section and one unresolved priority question.
```

#### Check the result

```
Check that the 400-hour rule remains conditional on dusty conditions and that no general precedence is invented.
```

**Ailoot Ultra · OpenAI Chat** `POST /v1/chat/completions` `qwen-long`

[`qwen-long`](https://ailoot.ai/models/en/#m=qwen-long&route=Ultra&caller=qwen-long&fmt=chat)

Alibaba /`qwen-long`

### Overview

Qwen-Long is built for questions across large document collections. Its maker documents a file-upload and reference workflow with up to 10 million tokens of document context, comparison across files and structured text answers.

Accepted inputs

Text

Results

Text

### Available in Ailoot · inputs & methods

**Ailoot Ultra · OpenAI Chat** `POST /v1/chat/completions`

Input types

`text`

Output types

`text`

Output format

json or SSE

| Field | Type | Requirement | Values & limits | Default |
| --- | --- | --- | --- | --- |
| Field`model` | Type`string` | RequirementRequired | Values & limits qwen-long | Default— |
| Field`messages` | Type`message[]` | RequirementRequired | Values & limits Minimum items: 1 | Default— |
| Field`messages[].role` | Type`string` | RequirementRequired | Values & limits Examples: system, user, assistant, tool, function Conditions: These roles are explicitly represented by Source compatibility types; the exact model role set remains model-specific. Model-specific | Default— |
| Field`messages[].content` | Type`string\|content_part[]\|null` | RequirementOptional | Values & limits | Default— |
| Field`messages[].tool_calls` | Type`tool_call[]` | RequirementOptional | Values & limits | Default— |
| Field`messages[].tool_call_id` | Type`string` | RequirementOptional | Values & limits Applies when: role=tool; use actual returned ID | Default— |
| Field`messages[].name` | Type`string` | RequirementOptional | Values & limits | Default— |
| Field`messages[].reasoning_content` | Type`string` | RequirementOptional | Values & limits Applies when: Round-trip actual returned reasoning where this model uses it | Default— |
| Field`messages[].reasoning_details` | Type`object\|array` | RequirementOptional | Values & limits Model-specific | Default— |
| Field`max_tokens` | Type`integer` | RequirementOptional | Values & limits Minimum: 1 Model-specific | Default— |
| Field`max_completion_tokens` | Type`integer` | RequirementOptional | Values & limits Minimum: 1 Model-specific | Default— |
| Field`stream` | Type`boolean` | RequirementOptional | Values & limits | Defaultfalse |
| Field`stream_options.include_usage` | Type`boolean` | RequirementOptional | Values & limits Model-specific | Default— |
| Field`temperature` | Type`number` | RequirementOptional | Values & limits Model-specific | Default— |
| Field`top_p` | Type`number` | RequirementOptional | Values & limits Model-specific | Default— |
| Field`stop` | Type`string\|string[]` | RequirementOptional | Values & limits Model-specific | Default— |
| Field`tools` | Type`function_tool[]` | RequirementOptional | Values & limits Model-specific | Default— |
| Field`tools[].type` | Type`string` | RequirementOptional | Values & limits function Model-specific | Default— |
| Field`tools[].function.name` | Type`string` | RequirementRequired | Values & limits Applies when: function tool supplied | Default— |
| Field`tools[].function.description` | Type`string` | RequirementOptional | Values & limits | Default— |
| Field`tools[].function.parameters` | Type`JSON_schema` | RequirementOptional | Values & limits | Default— |
| Field`tool_choice` | Type`string\|object` | RequirementOptional | Values & limits Model-specific | Default— |
| Field`parallel_tool_calls` | Type`boolean` | RequirementOptional | Values & limits Model-specific | Default— |
| Field`response_format` | Type`object` | RequirementOptional | Values & limits Model-specific | Default— |
| Field`reasoning_effort` | Type`string` | RequirementOptional | Values & limits Model-specific | Default— |
| Field`reasoning` | Type`object` | RequirementOptional | Values & limits Model-specific | Default— |
| Field`service_tier` | Type`string` | RequirementOptional | Values & limits Model-specific | Default— |
| Field`instructions` | Type`string` | RequirementOptional | Values & limits Compatibility field | Default— |
| Field`functions` | Type`function[]` | RequirementOptional | Values & limits Model-specific | Default— |
| Field`function_call` | Type`string\|object` | RequirementOptional | Values & limits Model-specific | Default— |
| Field`prompt_cache_options` | Type`object` | RequirementOptional | Values & limits Model-specific | Default— |
| Field`modalities` | Type`string[]` | RequirementOptional | Values & limits text | Default— |
| Field`provider` | Type`object` | RequirementOptional | Values & limits Conditions: provider.options is rejected on this Ultra text route | Default— |
| Field`cache_control.ttl` | Type`string` | RequirementOptional | Values & limits Conditions: 1h is rejected in actual prompt-cache locations | Default— |

Input material combinations

**Text** · UTF8 text

`messages[].content`

Method parameters and lifecycle

| Parameter | Contract |
| --- | --- |
| Parameter`content_type` | Contractapplication/json |
| Parameter`required` | Contractmodel, messages |
| Parameter`material_types` | Contracttext |
| Parameter`messages` | Contractmessage array with role/content shape |
| Parameter`file_material` | Contractactual UTF-8 document inserted as literal text; no file ID inferred |
| Parameter`optional_controls` | Contractstream, temperature, top\_p, stop, max\_tokens, max\_completion\_tokens, reasoning, response\_format, tools, tool\_choice |
| Parameter`control_scope` | Contractmodel-specific; user function tools differ from hosted tools |
| Parameter`output_modalities` | Contracttext |
| Parameter`hosted_operations` | Contractfalse |
| Parameter`multimodal_input_binding` | Contractnull |

Lifecycle: `synchronous_or_streamed`

Send exact model ID with messages.

Context length is not an output cap.

A text file may supply literal text; image/audio/file-object inputs need exact binding.

### Pricing

Tariff references do not add request options. Supported parameters are listed for the selected method.

Fast mode

Not specified When fast mode is selected

Flex mode

Not specified When flex mode is selected

Maximum reasoning effort

Not specified When maximum reasoning effort uses the default adjustment

#### Ailoot rates

#### Prices by configuration

| Configuration | Rate schedule | Charge |
| --- | --- | --- |
| ConfigurationBase token rates | Rate scheduleBase rate | Charge Input · Input tokens **$0.000144** / 1K tokens Output · Output tokens **$0.000572** / 1K tokens Input · Cache read **$0** / 1K tokens Input · Cache write **$0** / 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 →](https://ailoot.ai/docs/en/billing/reserve/)

### Example requests

#### Ailoot Ultra · OpenAI Chat

curlPython SDKPython stream

```bash
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
python3 - <<'PY_REQUEST'
import json,os
from pathlib import Path
p=json.loads('{"model": "qwen-long", "messages": [{"role": "user", "content": "Explain the difference between an observation and a hypothesis in three sentences."}]}')

Path("request.json").write_text(json.dumps(p,ensure_ascii=False))
PY_REQUEST
curl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/chat/completions \
  -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \
  --data-binary @request.json -D response-headers.txt -o result.json
python3 - <<'PY_RESULT'
import json
from pathlib import Path
r=json.loads(Path("result.json").read_text())
for x in r.get("choices",[]):
    if x.get("message",{}).get("content"): print(x["message"]["content"])
PY_RESULT
```

```python
from openai import OpenAI
import os

if not os.environ.get("AILOOT_API_KEY", "").strip(): raise SystemExit("Set AILOOT_API_KEY before making a request")
client=OpenAI(base_url="https://api.ailoot.ai/v1",api_key=os.environ["AILOOT_API_KEY"],max_retries=0)
result=client.chat.completions.create(model='qwen-long',messages=[{"role":"user","content":"Explain observations and hypotheses in three sentences."}])
import base64, json
from pathlib import Path

def save_result(data, stem="result"):
    # Keep every field, including usage, IDs, reasoning and tool requests.
    Path(stem + ".json").write_text(json.dumps(data, ensure_ascii=False, indent=2), encoding="utf-8")
    print(json.dumps(data, ensure_ascii=False, indent=2))
    def save_blob(encoded, suffix, label):
        raw = base64.b64decode(encoded, altchars=b"-_", validate=True)
        ext = "png" if raw.startswith(b"\x89PNG\r\n\x1a\n") else "jpg" if raw.startswith(b"\xff\xd8") else "webp" if raw[:4] == b"RIFF" and raw[8:12] == b"WEBP" else suffix
        file = Path(stem + "-" + label + "." + ext)
        file.write_bytes(raw)
        print("Saved", file)
    for index, block in enumerate(data.get("content") or []):
        print("Content", index, json.dumps(block, ensure_ascii=False))
    for choice in data.get("choices") or []:
        print("Choice", choice.get("index"), json.dumps(choice.get("message", choice.get("delta", {})), ensure_ascii=False))
    for index, item in enumerate(data.get("output") or []):
        print("Output", index, json.dumps(item, ensure_ascii=False))
        if item.get("type") == "image_generation_call" and item.get("result"):
            save_blob(item["result"], item.get("output_format") or "bin", "output-" + str(index))
    for ci, candidate in enumerate(data.get("candidates") or []):
        for pi, part in enumerate((candidate.get("content") or {}).get("parts") or []):
            print("Candidate/part", ci, pi, json.dumps(part, ensure_ascii=False))
            blob = part.get("inlineData") or part.get("inline_data")
            if blob and blob.get("data"):
                mime = blob.get("mimeType") or blob.get("mime_type")
                suffix = {"image/png":"png", "image/jpeg":"jpg", "image/webp":"webp", "audio/wav":"wav", "audio/mpeg":"mp3", "video/mp4":"mp4"}.get(mime, "bin")
                save_blob(blob["data"], suffix, "candidate-" + str(ci) + "-part-" + str(pi))

save_result(result.to_dict(mode="json"))
```

```python
from openai import OpenAI
import os
from pathlib import Path

if not os.environ.get("AILOOT_API_KEY", "").strip(): raise SystemExit("Set AILOOT_API_KEY before making a request")
client=OpenAI(base_url="https://api.ailoot.ai/v1",api_key=os.environ["AILOOT_API_KEY"],max_retries=0)
import base64, json
from pathlib import Path

def save_result(data, stem="result"):
    # Keep every field, including usage, IDs, reasoning and tool requests.
    Path(stem + ".json").write_text(json.dumps(data, ensure_ascii=False, indent=2), encoding="utf-8")
    print(json.dumps(data, ensure_ascii=False, indent=2))
    def save_blob(encoded, suffix, label):
        raw = base64.b64decode(encoded, altchars=b"-_", validate=True)
        ext = "png" if raw.startswith(b"\x89PNG\r\n\x1a\n") else "jpg" if raw.startswith(b"\xff\xd8") else "webp" if raw[:4] == b"RIFF" and raw[8:12] == b"WEBP" else suffix
        file = Path(stem + "-" + label + "." + ext)
        file.write_bytes(raw)
        print("Saved", file)
    for index, block in enumerate(data.get("content") or []):
        print("Content", index, json.dumps(block, ensure_ascii=False))
    for choice in data.get("choices") or []:
        print("Choice", choice.get("index"), json.dumps(choice.get("message", choice.get("delta", {})), ensure_ascii=False))
    for index, item in enumerate(data.get("output") or []):
        print("Output", index, json.dumps(item, ensure_ascii=False))
        if item.get("type") == "image_generation_call" and item.get("result"):
            save_blob(item["result"], item.get("output_format") or "bin", "output-" + str(index))
    for ci, candidate in enumerate(data.get("candidates") or []):
        for pi, part in enumerate((candidate.get("content") or {}).get("parts") or []):
            print("Candidate/part", ci, pi, json.dumps(part, ensure_ascii=False))
            blob = part.get("inlineData") or part.get("inline_data")
            if blob and blob.get("data"):
                mime = blob.get("mimeType") or blob.get("mime_type")
                suffix = {"image/png":"png", "image/jpeg":"jpg", "image/webp":"webp", "audio/wav":"wav", "audio/mpeg":"mp3", "video/mp4":"mp4"}.get(mime, "bin")
                save_blob(blob["data"], suffix, "candidate-" + str(ci) + "-part-" + str(pi))

with client.chat.completions.stream(model='qwen-long',messages=[{"role":"user","content":"Explain observations and hypotheses in three sentences."}]) as stream:
    with Path("stream-events.jsonl").open("w",encoding="utf-8") as log:
        for event in stream:
            payload=event.to_dict(mode="json")
            log.write(json.dumps(payload,ensure_ascii=False)+"\n"); log.flush()
            print(json.dumps(payload,ensure_ascii=False))
    final=stream.get_final_completion()
    save_result(final.to_dict(mode="json"),"stream-result")
```

### Receive and save results

#### Ailoot Ultra · OpenAI Chat

json or SSE

##### Keep all completed results

Keep every complete returned response, file and content part.

Keep every choice and its content/tool calls/reasoning. In SSE assemble deltas by choice/tool index, retain the final finish reason and usage.

##### If the original response needs checking

Keep request/response IDs and headers. No generic text job retrieval URL is supplied.

Response fields

| Field | Type |
| --- | --- |
| Field`choices[].index` | Typeinteger |
| Field`choices[].message.content` | Typestring\|null |
| Field`choices[].message.tool_calls` | Typetool\_call\[\] |
| Field`choices[].message.reasoning_content` | Typestring |
| Field`choices[].message.reasoning_details` | Typeobject\|array |
| Field`choices[].finish_reason` | Typestring\|null |
| Field`usage` | Typeobject |

Errors and next steps

| Response | Condition | Next step |
| --- | --- | --- |
| Response400 · `invalid_request_error` | ConditionInvalid required fields, material representation or parameter value | Next stepCorrect the indicated fields before a new creation request. |

### Aliases

#### Model aliases

**Ailoot Ultra** [`qwen-long`](https://ailoot.ai/models/en/#m=qwen-long&route=Ultra&caller=qwen-long&fmt=chat)

#### Method path aliases

Use the method paths shown above.

#### Related caller IDs

[`qwen-long`](https://ailoot.ai/models/en/#m=qwen-long&route=Ultra&caller=qwen-long&fmt=chat)

**Ailoot Ultra · Anthropic Messages** `POST /v1/messages` `qwen-long`

[`qwen-long`](https://ailoot.ai/models/en/#m=qwen-long&route=Ultra&caller=qwen-long&fmt=messages)

Alibaba /`qwen-long`

### Overview

Qwen-Long is built for questions across large document collections. Its maker documents a file-upload and reference workflow with up to 10 million tokens of document context, comparison across files and structured text answers.

Accepted inputs

Text

Results

json · sse

### Available in Ailoot · inputs & methods

**Ailoot Ultra · Anthropic Messages** `POST /v1/messages`

Input types

`text`

Output types

`json`, `sse`

Output format

JSON or SSE

| Field | Type | Requirement | Values & limits | Default |
| --- | --- | --- | --- | --- |
| Field`model` | Type`string` | RequirementRequired | Values & limits qwen-long | Default— |
| Field`messages` | Type`message[]` | RequirementRequired | Values & limits | Default— |
| Field`messages[].role` | Type`string` | RequirementRequired | Values & limits user, assistant | Default— |
| Field`messages[].content` | Type`string` | RequirementRequired | Values & limits | Default— |
| Field`max_tokens` | Type`integer` | RequirementRequired | Values & limits | Default— |
| Field`stream` | Type`boolean` | RequirementOptional | Values & limits | Defaultfalse |

Input material combinations

**Text** · UTF-8 text

`messages[].content string`

Method parameters and lifecycle

| Parameter | Contract |
| --- | --- |
| Parameter`content_type` | Contractapplication/json |
| Parameter`required` | Contractmodel, messages, max\_tokens |
| Parameter`optional_controls` | Contractstream |
| Parameter`material_types` | Contracttext |
| Parameter`text_file_material` | ContractRead the actual UTF-8 document and put its text in the indicated input or message content string. |

Lifecycle: `synchronous_or_streamed`

### Pricing

Tariff references do not add request options. Supported parameters are listed for the selected method.

Fast mode

Not specified When fast mode is selected

Flex mode

Not specified When flex mode is selected

Maximum reasoning effort

Not specified When maximum reasoning effort uses the default adjustment

#### Ailoot rates

#### Prices by configuration

| Configuration | Rate schedule | Charge |
| --- | --- | --- |
| ConfigurationBase token rates | Rate scheduleBase rate | Charge Input · Input tokens **$0.000144** / 1K tokens Output · Output tokens **$0.000572** / 1K tokens Input · Cache read **$0** / 1K tokens Input · Cache write **$0** / 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 →](https://ailoot.ai/docs/en/billing/reserve/)

### Example requests

#### Ailoot Ultra · Anthropic Messages

Complete minimal JSON bodycurl · use your UTF-8 documentPython · save the complete result

```json
{
  "model": "qwen-long",
  "max_tokens": 128,
  "messages": [
    {
      "role": "user",
      "content": "Summarize the incident report."
    }
  ],
  "stream": false
}
```

```bash
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
: "${AILOOT_TEXT_FILE:?Set your actual UTF-8 document}"
export AILOOT_TEXT_FILE
python3 - <<'PY_REQUEST'
import json, os
from pathlib import Path

source_file = Path(os.environ['AILOOT_TEXT_FILE'])
if not source_file.is_file():
    raise SystemExit('Set AILOOT_TEXT_FILE to your actual UTF-8 document')
text = source_file.read_text(encoding='utf-8')
if not text.strip():
    raise SystemExit('Choose a document containing text')
payload = {'model': 'qwen-long', 'max_tokens': 128, 'messages': [{'role': 'user', 'content': 'Summarize the incident report.'}]}
payload['messages'][0]['content'] = 'Summarize this material and quote supporting source passages.\n\n' + text
Path('request.json').write_text(json.dumps(payload, ensure_ascii=False), encoding='utf-8')
PY_REQUEST
curl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/messages \
  -H "x-api-key: $AILOOT_API_KEY" -H 'anthropic-version: 2023-06-01' -H 'Content-Type: application/json' \
  --data-binary @request.json -D response-headers.txt -o result.json
python3 - <<'PY_RESULT'
import json
from pathlib import Path

result = json.loads(Path('result.json').read_text(encoding='utf-8'))
print(json.dumps(result, ensure_ascii=False, indent=2))
PY_RESULT
```

```python
import json, os
from pathlib import Path

source_file = Path(os.environ['AILOOT_TEXT_FILE'])
if not source_file.is_file():
    raise SystemExit('Set AILOOT_TEXT_FILE to your actual UTF-8 document')
text = source_file.read_text(encoding='utf-8')
if not text.strip():
    raise SystemExit('Choose a document containing text')
payload = {'model': 'qwen-long', 'max_tokens': 128, 'messages': [{'role': 'user', 'content': 'Summarize the incident report.'}]}
payload['messages'][0]['content'] = 'Summarize this material and quote supporting source passages.\n\n' + text
from urllib.request import Request, urlopen
from urllib.error import HTTPError

api_key = os.environ['AILOOT_API_KEY']
if not api_key.strip():
    raise SystemExit('Set AILOOT_API_KEY before making a request')
headers = {'x-api-key': 'PLACEHOLDER_KEY', 'anthropic-version': '2023-06-01', 'Content-Type': 'application/json'}
headers['x-api-key'] = api_key
request = Request('https://api.ailoot.ai/v1/messages', data=json.dumps(payload, ensure_ascii=False).encode('utf-8'), headers=headers, method='POST')
try:
    with urlopen(request, timeout=120) as response:
        raw = response.read()
        Path('response-headers.txt').write_text(str(response.headers), encoding='utf-8')
except HTTPError as error:
    Path('result.json').write_bytes(error.read())
    Path('response-headers.txt').write_text(str(error.headers), encoding='utf-8')
    raise
Path('result.json').write_bytes(raw)
import json
from pathlib import Path

result = json.loads(Path('result.json').read_text(encoding='utf-8'))
print(json.dumps(result, ensure_ascii=False, indent=2))
```

### Receive and save results

#### Ailoot Ultra · Anthropic Messages

JSON or SSE

##### Keep all completed results

Keep every complete returned response, file and content part.

Keep all content blocks, thinking signatures and actual tool-use IDs. Assemble all SSE block deltas; a first text block is not the complete output.

##### If the original response needs checking

Keep request/response IDs and headers. No generic text job retrieval URL is supplied.

Response fields

| Field | Type |
| --- | --- |
| Field`id` | Typestring |
| Field`model` | Typestring |
| Field`content[]` | Typetext\|thinking\|tool\_use\|other content block |
| Field`stop_reason` | Typestring\|null |
| Field`usage` | Typeobject |

Errors and next steps

| Response | Condition | Next step |
| --- | --- | --- |
| Response400 · `invalid_request_error` | ConditionInvalid required fields, material representation or parameter value | Next stepCorrect the indicated fields before a new creation request. |

### Aliases

#### Model aliases

**Ailoot Ultra** [`qwen-long`](https://ailoot.ai/models/en/#m=qwen-long&route=Ultra&caller=qwen-long&fmt=messages)

#### Method path aliases

Use the method paths shown above.

#### Related caller IDs

[`qwen-long`](https://ailoot.ai/models/en/#m=qwen-long&route=Ultra&caller=qwen-long&fmt=messages)

FAQ · Qwen-Long

What inputs and results are available?

`POST /v1/chat/completions` · `qwen-long`: `text` → `text` `POST /v1/messages` · `qwen-long`: `text` → `json`, `sse`

Which fields does the request use?

`POST /v1/chat/completions` · `qwen-long`: `model`, `messages`, `stream`, `modalities`, `provider` `POST /v1/messages` · `qwen-long`: `model`, `messages`, `max_tokens`, `stream`

What limits apply?

`POST /v1/chat/completions` · `qwen-long`: `messages.min_items`: `1`

Connect Ailoot to Claude Code, OpenCode, Hermes or your own app.

## The company and its project portfolio

The company and its project portfolio: millions of customers; monthly sales in the billions.

## Buy tokens at a discount.

Subscription discounts for regular use. Promo codes offer up to 50% off token purchases.

Subscription

Choose a discounted plan for your regular requests.

Promo code: up to 50% off

Enter your code at checkout. The price updates to reflect the current promotion.

Spending in your history

The model, tokens and amount are recorded for each request.

[Choose a subscription](https://ailoot.ai/docs/en/billing/subscriptions/) · [View model prices](https://ailoot.ai/models/en/)

## Connect the API to a product you sell.

Use Ailoot in SaaS, apps and bots under its official service offer and licence agreement. Request a reseller licence for resale.

Commercial application

Add text, image, video and audio generation to paid features in your service.

Reseller licence

Send a description of your project and how you provide access. Request written terms for use and resale.

Documents on the website

The service offer, licence agreement and data processing policy are available before you connect.

[Request a reseller licence](mailto:support@ailoot.ai) · [Service offer and licence agreement](https://ailoot.ai/legal/offer?lang=en)

## Ailoot · The company and its project portfolio





Ailoot combines established operating experience, a large client base, stable service and ongoing KPI control.





The company and its project portfolio: millions of customers; monthly sales in the billions.





Ailoot brings that operating experience to API access for AI features in customer products, agents, applications and automations.