Model ID and API Format
There is no official request model ID, and OpenAI API compatibility has not been confirmed.
Check the official GLM 5.5 API status, EvoLink access, model ID, pricing, context window, and limits. No callable API has been verified yet; join the alert and decide whether to integrate after real production metrics are available.
We will email you when EvoLink verifies the official release, a callable route, the request model ID, pricing, and supported API behavior.
We will only email you about GLM 5.5 availability. No spam.
Want faster updates? Join the EvoLink Discord
When access opens we will email you a launch alert, and this page will be updated with the verified model ID, live pricing, API compatibility, regions and limits — plus the path to integrate through EvoLink's unified API while keeping a fallback model.
These are the fields developers need before integration. No reliable values are available yet; EvoLink will update them only after official publication and route-level verification.
There is no official request model ID, and OpenAI API compatibility has not been confirmed.
Input, output, cache, and plan pricing are unpublished. The live EvoLink pricing module will be the source of truth after launch.
No reliable context length, maximum output token limit, or effective long-context result is available.
Regions, concurrency, quotas, rate limits, and 429 behavior require a callable production route.
No official or aggregator GLM 5.5 route has been verified. EvoLink will update this field after access is live.
Only real workloads on a real API route can answer that question. These six user-demand metrics are what EvoLink will verify after access opens; they are not confirmed GLM 5.5 capabilities.
Measure whether bug fixes, multi-file refactors, and test tasks actually pass instead of judging one response.
Track argument errors, repeated calls, unproductive loops, and how often a person must take over.
Test whether the model keeps constraints, finds evidence, and completes work deep inside large repositories and documents.
Native vision is a frequent request, but input modalities remain unconfirmed and require a model card plus real requests.
Evaluate time to first token, end-to-end speed, capacity, error rate, and peak-hour 429 responses.
Include token use, retries, failed runs, and human correction instead of comparing list prices alone.
There is no verified GLM 5.5 API, price, or test result yet, so teams should not delay a project that can ship on GLM-5.2 today.
If delivery matters now, establish a real baseline on the documented and callable GLM-5.2 route.
Upgrade only when your workloads show a verified improvement in completion rate, reliability, or cost per accepted task.
Keep the current model behind EvoLink's unified API, then add GLM 5.5 after validation without rebuilding another provider integration.
Check the release evidence and decide whether to wait or use GLM-5.2 now.
No official Z.ai announcement or model card was found as of July 27, 2026. The name and timing are based on third-party reporting.
Z.ai has not confirmed the final name. All three names appear in current media or community reporting, so this page treats GLM 5.5 as a search label rather than a settled product name.
No. EvoLink has not published a callable route, model ID, pricing, or production support claim for GLM 5.5.
Some reports cite an August 2026 analyst forecast, but Z.ai has not confirmed an exact date.
No official request model ID is published. Do not infer one from the page slug or GLM-5.2.
Pricing is not published. This page will use EvoLink's live pricing module only after the route and SKUs are approved.
That is not confirmed. GLM-5.2's license does not prove that a future release will use the same terms.
Native vision is a frequent community request, but Z.ai has not confirmed the input modalities for its next model.
No. Keep the supported GLM-5.2 route until GLM 5.5 has comparable facts and passes offline, shadow, canary, and rollback gates.
A notification after EvoLink verifies the official release, model ID, pricing, route behavior, and access state.