GLM-4.5-Flash
GLM-4.5-Flash is Zhipu’s text model for reasoning, code generation, long-document work and tasks involving external tools.
- Ailoot Ultra · OpenAI Chat
POST /v1/chat/completionsglm-4.5-flash - Ailoot Ultra · Anthropic Messages
POST /v1/messagesglm-4.5-flash
About the model
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
GLM-4.5-Flash is the text-only Flash edition in Zhipu’s GLM-4.5 family. The manufacturer describes a 128K context window, structured output and a hybrid design with reasoning and direct-response modes. Software engineering, frontend coding, tool use and multi-turn text work are central applications.
Prepare the task and evidence
For a software change, supply the relevant code, observed behavior, constraints and acceptance criteria. For a long-document task, label the source sections and identify the facts to extract or compare. State the required output structure, such as a patch, a JSON object or a translated passage.
Keep tools and answers distinct
The model’s tool-calling ability supports applications that provide tool definitions and return tool results. A generated tool request is a request for the application to execute that action. Retain the returned evidence when asking the model to continue, and verify code or structured data against the project’s requirements.
Through Ailoot, select this exact model ID in /v1/chat/completions and supply the task in messages. Each message carries a role and its content; keep the relevant instruction and source material together. Collect the complete JSON response or all SSE segments when stream is enabled, and retain usage with the written result.
Ailoot Ultra · OpenAI Chat POST /v1/chat/completions glm-4.5-flash
glm-4.5-flashOverview
GLM-4.5-Flash is Zhipu’s text model for reasoning, code generation, long-document work and tasks involving external tools.
- Accepted inputs
- Text · Images
- Results
- Text
Available in Ailoot · inputs & methods
Ailoot Ultra · OpenAI Chat POST /v1/chat/completions
- Input types
text,image- Output types
text- Output format
- JSON or SSE
| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits glm-4.5-flash Conditions: Use this exact Ailoot routing selector. | Default— |
Fieldmessages | Typearray | RequirementRequired | Values & limits Conditions: | Default— |
Fieldstream | Typeboolean | RequirementOptional | Values & limits Conditions: | Defaultfalse |
Input material combinations
text_input · Required: messages
image_with_text · Required: messages with actual image content blocks
Method parameters and lifecycle
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, messages |
Parameteroptional | Contractstream |
Parametermaterial_types | Contracttext, image |
Parameterconditions | ContractUse this exact Ailoot routing selector., Image content is carried by this protocol where the exact selected model supports vision. Protocol admission does not establish image capability for every model. |
Method aliases: /chat/completions
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
- Explicit cache pricing
- Not enabled When explicit cache is requested
- Text-only zero rates
- Cache, tools and media follow their separately listed pricing conditions. For text-only input and output
Ailoot rates
Prices by configuration
| Configuration | Rate schedule | Charge |
|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Charge Input · Input tokens $0 / 1K tokens Output · Output tokens $0 / 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
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
export AILOOT_API_KEY
python3 - <<'PY_REQUEST'
import json,os
from pathlib import Path
p=json.loads('{"model": "glm-4.5-flash", "messages": [{"role": "user", "content": "Explain how a rainbow forms."}]}')
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
# Submit once. Retain the complete result, original identifiers and every response header.
Receive and save results
Ailoot Ultra · OpenAI Chat
JSON or SSE
Keep all completed results
Keep every complete returned response, file and content part.
Retain every content block, tool-call ID, thinking signature when returned, all SSE deltas and complete usage. A first text fragment is not the whole result.
If the original response needs checking
Keep the original X-Client-Request-ID, response and headers. An unknown or result_pending_check outcome does not authorize a second creation.
Response fields
| Field | Type |
|---|---|
Fieldchoices[] | Typeobject |
Fieldusage | Typeobject |
Errors and next steps
| Response | Condition | Next step |
|---|---|---|
Response400 · invalid_request_error | ConditionA required field, model selector, type or input representation is invalid. | Next stepInspect the returned validation detail before preparing a separate request. |
Response | ConditionThe original request or result is unknown or requires a check. | Next stepKeep original identifiers and headers; read only supported status/library records. Do not submit creation again. |
Aliases
Model aliases
Ailoot Ultra glm-4.5-flash
Method path aliases
/chat/completions
Related caller IDs
Ailoot Ultra · Anthropic Messages POST /v1/messages glm-4.5-flash
glm-4.5-flashOverview
GLM-4.5-Flash is Zhipu’s text model for reasoning, code generation, long-document work and tasks involving external tools.
- Accepted inputs
- Text · Images
- Results
- json · sse
Available in Ailoot · inputs & methods
Ailoot Ultra · Anthropic Messages POST /v1/messages
- Input types
text,image- Output types
json,sse- Output format
- JSON or SSE
| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits glm-4.5-flash Conditions: Use this exact Ailoot routing selector. | Default— |
Fieldmessages | Typearray | RequirementRequired | Values & limits Conditions: | Default— |
Fieldstream | Typeboolean | RequirementOptional | Values & limits Conditions: | Defaultfalse |
Fieldmax_tokens | Typeinteger | RequirementRequired | Values & limits Minimum: 1 Conditions: | Default— |
Input material combinations
text_input · Required: messages
image_with_text · Required: messages with actual image content blocks
Method parameters and lifecycle
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, messages, max_tokens |
Parameteroptional | Contractstream |
Parametermaterial_types | Contracttext, image |
Parameterconditions | ContractUse this exact Ailoot routing selector., Image content is carried by this protocol where the exact selected model supports vision. Protocol admission does not establish image capability for every model. |
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
- Explicit cache pricing
- Not enabled When explicit cache is requested
- Text-only zero rates
- Cache, tools and media follow their separately listed pricing conditions. For text-only input and output
Ailoot rates
Prices by configuration
| Configuration | Rate schedule | Charge |
|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Charge Input · Input tokens $0 / 1K tokens Output · Output tokens $0 / 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
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
export AILOOT_API_KEY
python3 - <<'PY_REQUEST'
import json,os
from pathlib import Path
p=json.loads('{"model": "glm-4.5-flash", "messages": [{"role": "user", "content": "Explain how a rainbow forms."}], "max_tokens": 256}')
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/messages \
-H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \
--data-binary @request.json -D response-headers.txt -o result.json
# Submit once. Retain the complete result, original identifiers and every response header.
Receive and save results
Ailoot Ultra · Anthropic Messages
JSON or SSE
Keep all completed results
Keep every complete returned response, file and content part.
Retain every content block, tool-call ID, thinking signature when returned, all SSE deltas and complete usage. A first text fragment is not the whole result.
If the original response needs checking
Keep the original X-Client-Request-ID, response and headers. An unknown or result_pending_check outcome does not authorize a second creation.
Response fields
| Field | Type |
|---|---|
Fieldcontent[] | Typeobject |
Fieldusage | Typeobject |
Errors and next steps
| Response | Condition | Next step |
|---|---|---|
Response400 · invalid_request_error | ConditionA required field, model selector, type or input representation is invalid. | Next stepInspect the returned validation detail before preparing a separate request. |
Response | ConditionThe original request or result is unknown or requires a check. | Next stepKeep original identifiers and headers; read only supported status/library records. Do not submit creation again. |
Aliases
Model aliases
Ailoot Ultra glm-4.5-flash
Method path aliases
/chat/completions
Related caller IDs
FAQ · GLM-4.5-Flash
- What inputs and results are available?
POST /v1/chat/completions·glm-4.5-flash:text,image→textPOST /v1/messages·glm-4.5-flash:text,image→json,sse- Which fields does the request use?
POST /v1/chat/completions·glm-4.5-flash:model,messages,streamPOST /v1/messages·glm-4.5-flash:model,messages,stream,max_tokens- What limits apply?
POST /v1/messages·glm-4.5-flash:max_tokens.minimum:1