GLM 5.3

glm-5.3by GLMrecommendedZDR enforceable

Compare Open in Playground

Context

1.05M

Max output

131K

Pricing

$1.19/M in$0.26/M cached$4.40/M out

Waterfall

Supported parameters

primary route

Sampling

Temperature0–2Top-p0–1Stop sequences

											Status
Azure Foundry via Experiential Cloudexperiential	110 tok/s	2.48s	70%	1.05M	131K	$1.40	$4.40	cache$0.26	—	—	active	measured
Tencent Cloud via Experiential Cloudexperiential	80.3 tok/s	4.78s	10.2%	1.05M	131K	$1.40	$4.40	cache$0.26	—	—	active	measured
Novita via Experiential Cloudexperiential	—	—	—	1.05M	131K	$1.40	$4.40	cache$0.26	—	ZDR	active	estimated
Wafer via Experiential Cloud	—	—	—	1.05M	131K	$1.19	$4.40	cache$0.26	—	—	disabled	estimated

not supported on every route; the gateway adapts or drops it (with a warning) on stricter providers.

Shown for the primary route; fallback routes may differ. Sending an unsupported field? See error reference.

Azure OpenAI docs

Quickstart

I want you to route my LLM calls for "glm-5.3" through the Experiential gateway instead of
calling the provider directly. It speaks the OpenAI Chat Completions API, so this is a base-URL
and key swap. Please:

1. Point the client at https://api.staging.experientiallabs.ai/v1 as the base URL.
2. Authenticate with my Experiential API key from the EXPLABS_API_KEY environment variable. If
   it isn't set, stop and tell me to create one under Settings -> API Keys and export it.
3. Use the model id "glm-5.3" exactly.
4. Update every place my code builds an LLM client for this model to use that base URL and key,
   leaving streaming and tool-calls as they are.
5. Make one test call and show me the reply plus the token usage, so we confirm it runs on my
   Experiential credits.

Tell me which files you changed.

Set EXPLABS_API_KEY to an organization API key before running your agent.

Benchmarks

Release notes

LMArena EloLMArena · Aug 20261477
Terminal-Benchvendor reported · Aug 202628.3