models

Qwen-Turbo-2024-11-01

Markdown · JSON

Qwen-Turbo-2024-11-01

Alibaba’s Qwen Turbo 2024-11-01 is a fixed text-model snapshot for answering questions about supplied material, summarizing related documents and reading source code. It also supports the maker’s JSON Object mode for extracting information into a parseable result.

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 Turbo 2024-11-01 is Alibaba’s fixed Qwen-Turbo snapshot from the Qwen2.5 generation. It takes written instructions and text context and produces a text answer. Useful tasks include questions about supplied documents, summaries that connect several sources, explanations of a codebase and extraction into JSON. Keep the dated model name with the prompt when comparing results between editions.

Read connected material with a specific question

Qwen’s Qwen2.5-Turbo introduction demonstrates reading long narratives and several related papers. The useful output depends on the question: an overview can explain the relationship between works, while a focused comparison can separate their approaches and supporting evidence. Supply clearly labeled text and ask for the distinctions that matter to the reader. An original brief might request each document’s main proposal, the passage supporting it and any disagreements between the documents. Ask for the answer in the language the audience needs, and keep quotations connected to their source.

Understand a repository through its text

The maker also demonstrates reading a repository assembled into a text file, first explaining its purpose and then locating classes and their file paths. Prepare code with file boundaries, names and relevant surrounding definitions intact. Ask for a map of a component before requesting a narrower explanation of how its parts relate. The resulting explanation or list of locations can guide inspection of the original files; review those locations against the supplied code.

Supply instructions and material as messages

In the manufacturer’s documented text workflow, a system message establishes the role and task rules, a user message supplies the question and material, and the model replies as the assistant. Keep the intended artifact explicit: a summary, a comparison table, a concise explanation or extracted fields. For a document task, distinguish the text to be read from the instruction describing what to do with it. Include terminology, output language and any rule for handling information that the source does not provide.

Continue a conversation with the relevant history

The maker’s Chat Completions workflow is stateless: continued discussion uses conversation history supplied with the next question. Append the preceding user and assistant messages when the follow-up depends on them. A first turn can establish a document’s argument; a second can ask which passage supports one conclusion. Keep the necessary source context available rather than assuming that a previous answer gives the model permanent memory. As the discussion grows, retain recent turns and the important source facts, or use a reviewed summary of earlier material. Removing history or compressing it can remove details needed for the next answer.

Extract information with JSON Object mode

Alibaba explicitly includes qwen-turbo-2024-11-01 in its JSON Object support. In the maker’s workflow, the response format is set to json_object and a system or user instruction must contain the word JSON. Specify field names and the treatment of missing information. For example, an extraction brief can request a document title, its named author and a supporting passage, with a stated convention for an absent author.

JSON Object mode targets valid JSON syntax; it does not enforce a particular schema, stable field names or field types. Inspect the returned object for the fields and values the task requires before using it downstream. A result cut off before completion may also be invalid JSON. Retain the complete object and its source text so that a formatting problem can be distinguished from an incorrect extraction.

Review the answer against the original material

Qwen’s introduction identifies instability in demanding long-sequence tasks. A large amount of supplied text does not guarantee that every detail is retrieved or every relationship is interpreted correctly. Check important statements, references and code locations against the original material, especially when the conclusion combines distant passages. Preserve the source, exact prompt and selected response as the working artifact. Alibaba’s version mapping distinguishes this snapshot from Qwen-Turbo-2025-04-28, so a comparison of editions should retain both model names and the same task.

Practical task

Map a component from supplied code text

Technical example in English

Map a component from supplied code text

Map this miniature repository. File reader.py: class CsvReader exposes read(path). File service.py: class ImportService receives a reader and calls reader.read(path) inside import_file(path). Explain each class’s role, identify where file loading occurs and list the supplied paths. Do not invent validation, storage or error handling absent from the excerpts.

Expected result

A two-component map, the read call location and an explicit list of unspecified behavior.

Check the result

Check that file loading is attributed to CsvReader.read and orchestration to ImportService.import_file, using the supplied paths only.
Ailoot Ultra · OpenAI Chat POST /v1/chat/completions qwen-turbo-2024-11-01

qwen-turbo-2024-11-01

Alibaba /qwen-turbo-2024-11-01

Overview

Alibaba’s Qwen Turbo 2024-11-01 is a fixed text-model snapshot for answering questions about supplied material, summarizing related documents and reading source code. It also supports the maker’s JSON Object mode for extracting information into a parseable result.

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
FieldTypeRequirementValues & limitsDefault
FieldmodelTypestringRequirementRequiredValues & limits
qwen-turbo-2024-11-01
Default—
FieldmessagesTypemessage[]RequirementRequiredValues & limits
Minimum items: 1
Default—
Fieldmessages[].roleTypestringRequirementRequiredValues & 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—
Fieldmessages[].contentTypestring|content_part[]|nullRequirementOptionalValues & limitsDefault—
Fieldmessages[].tool_callsTypetool_call[]RequirementOptionalValues & limitsDefault—
Fieldmessages[].tool_call_idTypestringRequirementOptionalValues & limits
Applies when: role=tool; use actual returned ID
Default—
Fieldmessages[].nameTypestringRequirementOptionalValues & limitsDefault—
Fieldmessages[].reasoning_contentTypestringRequirementOptionalValues & limits
Applies when: Round-trip actual returned reasoning where this model uses it
Default—
Fieldmessages[].reasoning_detailsTypeobject|arrayRequirementOptionalValues & limits
Model-specific
Default—
Fieldmax_tokensTypeintegerRequirementOptionalValues & limits
Minimum: 1
Model-specific
Default—
Fieldmax_completion_tokensTypeintegerRequirementOptionalValues & limits
Minimum: 1
Model-specific
Default—
FieldstreamTypebooleanRequirementOptionalValues & limitsDefaultfalse
Fieldstream_options.include_usageTypebooleanRequirementOptionalValues & limits
Model-specific
Default—
FieldtemperatureTypenumberRequirementOptionalValues & limits
Model-specific
Default—
Fieldtop_pTypenumberRequirementOptionalValues & limits
Model-specific
Default—
FieldstopTypestring|string[]RequirementOptionalValues & limits
Model-specific
Default—
FieldtoolsTypefunction_tool[]RequirementOptionalValues & limits
Model-specific
Default—
Fieldtools[].typeTypestringRequirementOptionalValues & limits
function
Model-specific
Default—
Fieldtools[].function.nameTypestringRequirementRequiredValues & limits
Applies when: function tool supplied
Default—
Fieldtools[].function.descriptionTypestringRequirementOptionalValues & limitsDefault—
Fieldtools[].function.parametersTypeJSON_schemaRequirementOptionalValues & limitsDefault—
Fieldtool_choiceTypestring|objectRequirementOptionalValues & limits
Model-specific
Default—
Fieldparallel_tool_callsTypebooleanRequirementOptionalValues & limits
Model-specific
Default—
Fieldresponse_formatTypeobjectRequirementOptionalValues & limits
Model-specific
Default—
Fieldreasoning_effortTypestringRequirementOptionalValues & limits
Model-specific
Default—
FieldreasoningTypeobjectRequirementOptionalValues & limits
Model-specific
Default—
Fieldservice_tierTypestringRequirementOptionalValues & limits
Model-specific
Default—
FieldinstructionsTypestringRequirementOptionalValues & limits
Compatibility field
Default—
FieldfunctionsTypefunction[]RequirementOptionalValues & limits
Model-specific
Default—
Fieldfunction_callTypestring|objectRequirementOptionalValues & limits
Model-specific
Default—
Fieldprompt_cache_optionsTypeobjectRequirementOptionalValues & limits
Model-specific
Default—
FieldmodalitiesTypestring[]RequirementOptionalValues & limits
text
Default—
FieldproviderTypeobjectRequirementOptionalValues & limits
Conditions: provider.options is rejected on this Ultra text route
Default—
Fieldcache_control.ttlTypestringRequirementOptionalValues & limits
Conditions: 1h is rejected in actual prompt-cache locations
Default—
Input material combinations

Text · UTF8 text

messages[].content

Method parameters and lifecycle
ParameterContract
Parametercontent_typeContractapplication/json
ParameterrequiredContractmodel, messages
Parametermaterial_typesContracttext
ParametermessagesContractmessage array with role/content shape
Parameterfile_materialContractactual UTF-8 document inserted as literal text; no file ID inferred
Parameteroptional_controlsContractstream, temperature, top_p, stop, max_tokens, max_completion_tokens, reasoning, response_format, tools, tool_choice
Parametercontrol_scopeContractmodel-specific; user function tools differ from hosted tools
Parameteroutput_modalitiesContracttext
Parameterhosted_operationsContractfalse
Parametermultimodal_input_bindingContractnull

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

ConfigurationRate scheduleCharge
ConfigurationBase token ratesRate scheduleBase rateCharge
Input · Input tokens $0.0001 / 1K tokens
Output · Output tokens $0.00018 / 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 →

Example requests

Ailoot Ultra · OpenAI Chat

curlPython SDKPython stream
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-turbo-2024-11-01", "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
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-turbo-2024-11-01',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"))
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-turbo-2024-11-01',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
FieldType
Fieldchoices[].indexTypeinteger
Fieldchoices[].message.contentTypestring|null
Fieldchoices[].message.tool_callsTypetool_call[]
Fieldchoices[].message.reasoning_contentTypestring
Fieldchoices[].message.reasoning_detailsTypeobject|array
Fieldchoices[].finish_reasonTypestring|null
FieldusageTypeobject
Errors and next steps
ResponseConditionNext step
Response400 · invalid_request_errorConditionInvalid required fields, material representation or parameter valueNext stepCorrect the indicated fields before a new creation request.

Aliases

Model aliases

Ailoot Ultra qwen-turbo-2024-11-01

Method path aliases

Use the method paths shown above.

Related caller IDs

qwen-turbo-2024-11-01

Ailoot Ultra · Anthropic Messages POST /v1/messages qwen-turbo-2024-11-01

qwen-turbo-2024-11-01

Alibaba /qwen-turbo-2024-11-01

Overview

Alibaba’s Qwen Turbo 2024-11-01 is a fixed text-model snapshot for answering questions about supplied material, summarizing related documents and reading source code. It also supports the maker’s JSON Object mode for extracting information into a parseable result.

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
FieldTypeRequirementValues & limitsDefault
FieldmodelTypestringRequirementRequiredValues & limits
qwen-turbo-2024-11-01
Default—
FieldmessagesTypemessage[]RequirementRequiredValues & limitsDefault—
Fieldmessages[].roleTypestringRequirementRequiredValues & limits
user, assistant
Default—
Fieldmessages[].contentTypestringRequirementRequiredValues & limitsDefault—
Fieldmax_tokensTypeintegerRequirementRequiredValues & limitsDefault—
FieldstreamTypebooleanRequirementOptionalValues & limitsDefaultfalse
Input material combinations

Text · UTF-8 text

messages[].content string

Method parameters and lifecycle
ParameterContract
Parametercontent_typeContractapplication/json
ParameterrequiredContractmodel, messages, max_tokens
Parameteroptional_controlsContractstream
Parametermaterial_typesContracttext
Parametertext_file_materialContractRead 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

ConfigurationRate scheduleCharge
ConfigurationBase token ratesRate scheduleBase rateCharge
Input · Input tokens $0.0001 / 1K tokens
Output · Output tokens $0.00018 / 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 →

Example requests

Ailoot Ultra · Anthropic Messages

Complete minimal JSON bodycurl · use your UTF-8 documentPython · save the complete result
{
  "model": "qwen-turbo-2024-11-01",
  "max_tokens": 128,
  "messages": [
    {
      "role": "user",
      "content": "Summarize the incident report."
    }
  ],
  "stream": false
}
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-turbo-2024-11-01', '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
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-turbo-2024-11-01', '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
FieldType
FieldidTypestring
FieldmodelTypestring
Fieldcontent[]Typetext|thinking|tool_use|other content block
Fieldstop_reasonTypestring|null
FieldusageTypeobject
Errors and next steps
ResponseConditionNext step
Response400 · invalid_request_errorConditionInvalid required fields, material representation or parameter valueNext stepCorrect the indicated fields before a new creation request.

Aliases

Model aliases

Ailoot Ultra qwen-turbo-2024-11-01

Method path aliases

Use the method paths shown above.

Related caller IDs

qwen-turbo-2024-11-01

FAQ · Qwen-Turbo-2024-11-01
What inputs and results are available?

POST /v1/chat/completions · qwen-turbo-2024-11-01: text → text

POST /v1/messages · qwen-turbo-2024-11-01: text → json, sse

Which fields does the request use?

POST /v1/chat/completions · qwen-turbo-2024-11-01: model, messages, stream, modalities, provider

POST /v1/messages · qwen-turbo-2024-11-01: model, messages, max_tokens, stream

What limits apply?

POST /v1/chat/completions · qwen-turbo-2024-11-01: messages.min_items: 1

More details

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 · View model prices

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 · Service offer and licence agreement