models

GLM-4-AirX

Markdown · JSON

GLM-4-AirX

GLM-4-AirX is Z.ai’s speed-oriented text model for low-latency dialogue, coding and tool-assisted workflows. Its published profile specifies an 8K context and up to 4K output, making it suited to focused tasks with concise, structured results.

About the model

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

Overview and model profile

GLM-4-AirX is the high-speed member of Z.ai’s GLM-4 Air line. The manufacturer positions it for low latency and concurrent application tasks, with particular attention to instruction following, engineering code and function calls. The model accepts text and returns text. Its own profile lists an 8K-token context window and a maximum output of 4K tokens. These are distinct from the larger context advertised for GLM-4-Air-250414; AirX keeps its own published profile.

For an interactive assistant, this points to focused requests: explain a function, classify a message, extract the fields from a supplied paragraph or turn a technical instruction into a concise response. Provide the relevant excerpt, current question and desired result together. Keep the complete conversation and any tool observations within the active context instead of assuming that a large background corpus will fit.

Capability support

The GLM-4 description lists streaming text, function calling, context caching, structured formats such as JSON and integration with MCP tools and data sources. Streaming presents the answer as it is generated, so an application can show useful text before the complete reply arrives. It changes delivery, not the model’s input or output modality.

Function calling lets the model propose an action from the functions described by the application. The application performs that action and returns the observation. A suitable cycle is a small lookup followed by a concise explanation of the returned data. MCP integration likewise depends on the tools and data the application provides. Context caching concerns reuse of repeated input; it does not imply that every repeated conversation has produced a cache hit.

For a JSON result, state the fields and their meaning before giving the material. For example, supply a technical request and ask for its category, required action and unanswered questions. The resulting structure is useful for the next application step, while the values still need to be checked against the supplied text.

Recommended scenarios

The manufacturer includes translation, semantic classification, document-field extraction, marketing writing, analytical reports and itinerary planning among GLM-4 applications. AirX’s shorter profile favors the immediate step within such a workflow. A translation request can supply a short passage, audience and terminology; the output is a rewritten passage that keeps the required names. A classification request can supply permitted labels and definitions, rather than asking for an unspecified judgment.

For extraction, define the requested identifiers and other fields and include only the relevant source passage. For writing, provide the product facts and one deliverable, such as a product paragraph or campaign line. For a report or itinerary, pass the relevant facts and constraints for the current step. If fresh information is needed, the application’s search or data tool supplies it; the model then works with that returned material.

Detailed preparation and speed focus

AirX is described as pre-trained on 15 trillion tokens, including substantial synthetic reasoning material. Its post-training uses dialogue preference alignment, rejection sampling and reinforcement learning to strengthen instructions, engineering code and function use. The manufacturer presents it as a faster variant of GLM-4-Air-250414, with changes to underlying components covering prompt prefilling and autoregressive decoding. This describes the manufacturer’s design, rather than a measured latency or concurrency guarantee for a particular deployment.

Preparing a useful request

Give AirX one bounded task and a compact expected artifact. For code, include the function, relevant input values and required behavior, then request a corrected fragment plus its explanation. For structured extraction, put the field definitions before the passage and ask it to mark absent information explicitly. Budget the result within the published 4K output profile; divide a large report into focused tasks instead of expecting an unrestricted document from one reply.

Ailoot Ultra · OpenAI Chat POST /v1/chat/completions glm-4-airx

glm-4-airx

Z.ai /glm-4-airx

Overview

GLM-4-AirX is Z.ai’s speed-oriented text model for low-latency dialogue, coding and tool-assisted workflows. Its published profile specifies an 8K context and up to 4K output, making it suited to focused tasks with concise, structured results.

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
glm-4-airx
Default—
FieldmessagesTypemessage[]RequirementRequiredValues & limits
Minimum items: 1
Default—
Fieldmessages[].roleTypestringRequirementRequiredValues & limits
Model-specific
Default—
Fieldmessages[].contentTypestringRequirementOptionalValues & limits
Applies when: Text conversation
Default—
FieldstreamTypebooleanRequirementOptionalValues & limitsDefaultfalse
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
Parametercontrol_scopeContractText conversation; stream is a boolean and defaults to false.
Parameteroutput_modalitiesContracttext
Parameterhosted_operationsContractfalse
Parametermultimodal_input_bindingContractnull

Method aliases: /chat/completions

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
Standard rate When fast mode is selected
Flex mode
Standard rate When flex mode is selected
Maximum reasoning effort
Standard rate When maximum reasoning effort uses the default adjustment

Ailoot rates

Prices by configuration

Match each charge to the conditions shown. Use one rate for each set of alternative configurations.

ConfigurationRate scheduleContext tokens, more thanContext tokens, up to and includingCharge
ConfigurationBase token ratesRate scheduleBase rateContext tokens, more than—Context tokens, up to and includingNo upper boundCharge
Input · Input tokens $0.0028 / 1K tokens
Output · Output tokens $0.0028 / 1K tokens
Input · Cache read — / 1K tokens
Input · Cache write — / 1K tokens
Input · Cache write, 1 hour — / 1K tokens
ConfigurationRequest-length tier 1Rate schedule—Context tokens, more than0Context tokens, up to and includingNo upper boundCharge
Input · Input tokens $0.0028 / 1K tokens
Output · Output tokens $0.0028 / 1K tokens
Input · Cache read — / 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 →

Example requests

Ailoot Ultra · OpenAI Chat

curlPython SDK
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
python3 - <<'PY_REQUEST'
import json,os
from pathlib import Path
p=json.loads('{"model":"glm-4-airx","messages":[{"role":"user","content":"hello"}],"stream":false}')

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="glm-4-airx", messages=[{"role":"user","content":"hello"}], stream=False)
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"))

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 glm-4-airx

Method path aliases

/chat/completions

Related caller IDs

glm-4-airx

Ailoot Ultra · Anthropic Messages POST /v1/messages glm-4-airx

glm-4-airx

Z.ai /glm-4-airx

Overview

GLM-4-AirX is Z.ai’s speed-oriented text model for low-latency dialogue, coding and tool-assisted workflows. Its published profile specifies an 8K context and up to 4K output, making it suited to focused tasks with concise, structured results.

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
glm-4-airx
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
Standard rate When fast mode is selected
Flex mode
Standard rate When flex mode is selected
Maximum reasoning effort
Standard rate When maximum reasoning effort uses the default adjustment

Ailoot rates

Prices by configuration

Match each charge to the conditions shown. Use one rate for each set of alternative configurations.

ConfigurationRate scheduleContext tokens, more thanContext tokens, up to and includingCharge
ConfigurationBase token ratesRate scheduleBase rateContext tokens, more than—Context tokens, up to and includingNo upper boundCharge
Input · Input tokens $0.0028 / 1K tokens
Output · Output tokens $0.0028 / 1K tokens
Input · Cache read — / 1K tokens
Input · Cache write — / 1K tokens
Input · Cache write, 1 hour — / 1K tokens
ConfigurationRequest-length tier 1Rate schedule—Context tokens, more than0Context tokens, up to and includingNo upper boundCharge
Input · Input tokens $0.0028 / 1K tokens
Output · Output tokens $0.0028 / 1K tokens
Input · Cache read — / 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 →

Example requests

Ailoot Ultra · Anthropic Messages

Complete minimal JSON bodycurl · use your UTF-8 documentPython · save the complete result
{
  "model": "glm-4-airx",
  "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': 'glm-4-airx', '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': 'glm-4-airx', '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 glm-4-airx

Method path aliases

/chat/completions

Related caller IDs

glm-4-airx

FAQ · GLM-4-AirX
What inputs and results are available?

POST /v1/chat/completions · glm-4-airx: text → text

POST /v1/messages · glm-4-airx: text → json, sse

Which fields does the request use?

POST /v1/chat/completions · glm-4-airx: model, messages, stream

POST /v1/messages · glm-4-airx: model, messages, max_tokens, stream

What limits apply?

POST /v1/chat/completions · glm-4-airx: 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