Requesty
Sign in

identity

open weights
Z.AI logo

glm-5.1Z.AI

from /1M in$0.84deepinfra inc.
context205K128K out
providers52 regions
price spread1.7x6 endpoints
endpoints
6
regions
2
api
chat
released
April 2026
eu routing
available

capabilities 4/8

visionreasoningtoolscachingweb searchjson schemacomputer useimage gen

The same weights cost 1.7x more on fireworks ai than on deepinfra inc.. That is what the endpoints table is for.

endpoints

6 / 2 regions
Providers serving glm-5.1, with pricing and measured performance. Best value in each column is coloured.
#flags
1DeepInfra Inc.Global203K$0.84$2.80$0.16zdr
2DeepInfra Inc.Global203K$1.05$3.50$0.20zdr
3Novita AIGlobal205K$1.38$4.40-zdr
4Fireworks AIGlobal202K$1.40$4.40$0.26zdr
5Nebius AIEU200K$1.40$4.40$1.40zdr
6Z.aiGlobal200K$1.40$4.40$0.26zdr
provider price, no markupper 1M tokensblank where no qualifying sample

measured

through Sep 12

no measured traffic for this model yet. the endpoints table above carries provider pricing

benchmarks

artificial analysis
Benchmark scores, each normalised to 100
evalScore as a share of 100/100
τ²-Bench97.7
GPQA Diamond86.8
Coding Index55.8
SciCode44.8
Terminal-Bench Hard43.2
Humanity's Last Exam30.1
Intelligence Index26.4
7 evalsmean55.0

Scores from Artificial Analysis and public leaderboards, normalised to 100. Bar colour is the band, not the rank: green 80 and up, blue 55 and up, amber 30 and up. Benchmarks measure narrow skills, so test on your own workload before committing. Released 2026-04-07.

call it

model=
glm-5.1

requesty routes this id across every provider serving glm-5.1, picking on price and health and failing over automatically. the id stays valid when a provider changes underneath it

Base url is https://router.requesty.ai/v1 for every id here. One key reaches the whole catalog.

quickstart

openai compatible
main.py
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="glm-5.1",    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

notes

reference

GLM-5.1 is Z.AI's latest flagship model, meticulously engineered for long-horizon autonomous tasks. Capable of working continuously on a single assignment for up to 8 hours, it autonomously manages the entire workflow—from initial planning and execution to iterative optimization and the delivery of production-grade results. While its general capabilities and coding proficiency are on par with Claude Opus 4.6, GLM-5.1 excels particularly in sustained execution, complex engineering optimization, a

questions 6

Which providers serve glm-5.1?
glm-5.1 is available from 5 providers through Requesty: DeepInfra Inc., Novita AI, Fireworks AI, Nebius AI, Z.ai. All endpoints share one OpenAI-compatible API and one key, and Requesty fails over between them automatically.
How much does glm-5.1 cost?
Pricing starts at $0.84 per million input tokens and $2.80 per million output tokens on the cheapest provider. Prices vary by provider and region; the table above shows every endpoint. Requesty charges exactly what the upstream provider charges, with no markup.
Is glm-5.1 open weights?
Yes. glm-5.1 is an open-weights model from Z.AI, which is why multiple inference providers can host it. Provider choice affects price, latency, and data-privacy terms, all compared above.
What is the context window of glm-5.1?
glm-5.1 supports up to 205K tokens of context, with up to 128K output tokens per response. Some providers expose a smaller window; check the per-endpoint context column above.
How do I use glm-5.1 with the OpenAI SDK?
Install the OpenAI SDK, set base_url to "https://router.requesty.ai/v1", set your API key to your Requesty key, and set the model to "glm-5.1" or any endpoint id from the table above. The quickstart section shows Python, JavaScript and cURL snippets.
Should I call glm-5.1 by its managed id or a provider id?
Use the managed id, "glm-5.1". Requesty picks which of the 5 providers serves each request based on price and health, and fails over when one degrades, so the id keeps working while the routing changes underneath it. There is also an EU-only id, "glm-5.1@eu", which routes the same way but only through EU-hosted providers. Send a provider id like "deepinfra/zai-org/GLM-5.1:flex" only when you need one specific deployment and want no failover.

more from z.ai 6

Other Z.AI models
modelcontextfrom /Mproviders
glm-5.3-flash1.0M$0.077
glm-5.31.0M$1.206
glm-5.2-fast1M$2.101
glm-5.21.0M$0.8011
glm-5203K$1.002
glm-4.7200K$0.601

route glm-5.1 through one endpoint

One key for 5 providers 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

glm-5.15 providers6 endpointsfrom $0.84 /1M inctx 205Kspread 1.7xupdated Sep 12