glm-5.3-flashxZ.AI
- endpoints
- 1
- regions
- 1
- api
- chat
- released
- September 2026
capabilities 5/8
| # | flags | ||||||
|---|---|---|---|---|---|---|---|
| 1 | Global | 1.0M | $0.37 | $1.25 | $0.07 | no-train |
no measured traffic for this model yet. the endpoints table above carries provider pricing
no published benchmark scores for this model
tencent/glm-5.3-flashxthis model has no managed policy yet, so call the provider endpoint directly. every id in the endpoints table works the same way
Base url is https://router.requesty.ai/v1 for every id here. One key reaches the whole catalog.
from openai import OpenAI client = OpenAI( api_key="YOUR_REQUESTY_API_KEY", base_url="https://router.requesty.ai/v1",) response = client.chat.completions.create( model="tencent/glm-5.3-flashx", messages=[ {"role": "user", "content": "Explain quantum computing in one paragraph."}, ],) print(response.choices[0].message.content)
Change the base url, use your Requesty key, set the model to any id in the call pane. Existing OpenAI SDK code needs no other edit, and the same key reaches every other model in the catalog, so switching later is a one-parameter change. Browse all models
GLM-5.3-FlashX is the enhanced, high-speed (~200 tokens/s) variant of GLM-5.3-Flash with a 1M token context window and image, video and file understanding.
questions 5
Which providers serve glm-5.3-flashx?
How much does glm-5.3-flashx cost?
Is glm-5.3-flashx open weights?
What is the context window of glm-5.3-flashx?
How do I use glm-5.3-flashx with the OpenAI SDK?
more from z.ai 6
| model | context | from /M | providers |
|---|---|---|---|
| glm-5.3 | 1.0M | $1.14 | 11 |
| glm-5.3-flash | 1.0M | $0.12 | 11 |
| glm-5.2-fast | 1M | $2.10 | 1 |
| glm-5.2 | 1.0M | $0.80 | 12 |
| glm-5.1 | 205K | $0.84 | 5 |
| glm-5 | 203K | $1.00 | 2 |
route glm-5.3-flashx through one endpoint
One key for 1 provider on this model and 600+ others. No markup on provider prices, automatic failover, caching built in. Weekly aggregates in the measured pane come from production traffic routed through Requesty, one line per provider on a shared axis. Methodology
