Bedrock serves Z.ai's 753B-parameter GLM 5.3 to eligible enterprise customers
Amazon Bedrock now offers Z.ai's 753B-parameter mixture-of-experts GLM 5.3 as a managed API, available only to eligible enterprise customers. Coding-agent teams can call a model that size without running inference hardware of their own.
The Engineer · Build desk
What happened
- Requests go to a source Region the caller picks, using the us.zai.glm-5.3 or global.zai.glm-5.3 cross-Region profile, and Bedrock routes them for processing.
- Prompt caching is implicit by default, and AWS recommends explicit cache controls, available on the Responses and Chat Completions APIs.
- Z.ai reports a 50% improvement over GLM 5.2 on its own internal coding benchmark.
Why it matters
- What it limits constraint Smaller teams cannot build on GLM 5.3 through Bedrock until AWS confirms they qualify as eligible enterprise customers.
- Who has to decide decision Picking the us. or global. profile ID sets how widely Bedrock may route each request, so the choice belongs with whoever owns data-residency policy.
- What it costs cost Moving production agents from GLM 5 to GLM 5.3 needs an in-house evaluation budget, since Z.ai's published gains are measured against GLM 5.2 on revised tests.
Next story · Build · 6h ago
Reflection's 501B-parameter Beam coding model launches on SageMaker JumpStartConfirmed2 publishers
An IAM policy for GLM 5.3 has to cover two resources: the base model and the target inference profile [17]. The actions listed in the prerequisites are bedrock:InvokeModel, bedrock:InvokeModelWithResponseStream and bedrock:CallWithBearerToken [17].
Caching matters most for agent loops. An agent resends its system prompt and repository context on every turn, and AWS says caching that repeated input reduces both latency and input cost [5]. For a coding agent with a large, stable repository prefix, I would set the explicit controls AWS recommends, so the team decides in code which prefix gets cached [4]. The part of this release I'd credit most is API parity. AWS says the OpenAI-compatible Responses and Chat Completions APIs now match Invoke and Converse more closely than they did for GLM 5 [16].
On public suites, Z.ai claims competitive performance on DeepSWE, Terminal Bench 3.0 and FrontierSWE [9]. The post says Z.ai's benchmark tests were themselves updated after the GLM 5.1 announcement because the improvements were so large [11]. Replacing the test because the model outgrew it is an unusual way to lose a baseline. For the 50% figure to carry over, a team's repositories and task lengths would have to resemble Z.ai's internal benchmark [10]. GLM 5 has been on Bedrock since earlier this year [12], so teams already running it can compare the two models on their own agent traces.
The CyberGym number is also Z.ai's own. It measured a leading 84.5 at release [13]. AWS's worked example runs an authorized security test of the reader's own application with Strix, an open-source AI penetration testing agent [14]. That demo needs Docker and Strix installed with its bedrock extra [14].
Service tiers set price against latency. Flex optimizes cost for less time-sensitive work, Priority costs more for latency-critical requests, and Standard is the default balance [15]. The post does not say which customers count as eligible enterprise customers, and it does not include prices for any tier [2].
What to watch
- AWS stating what makes a customer eligible for GLM 5.3, or widening access beyond eligible enterprise customers.
- Published per-token prices for the Flex, Standard and Priority tiers, including any separate rate for cached input.
- DeepSWE, Terminal Bench 3.0 or CyberGym results for GLM 5.3 from someone other than Z.ai.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence62
- Adoption
- Not scored
- Hype gap+25
- Incentives75
- Confidence68
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
GLM 5.3 from Z.ai (Zhipu AI) is now available on Amazon Bedrock.
- [2]
Access to GLM 5.3 on Bedrock is available to eligible enterprise customers.
- [3]
GLM 5.3 is available through US cross-Region inference (us.zai.glm-5.3) and Global cross-Region inference (global.zai.glm-5.3) profiles; requests are sent to a source AWS Region of the caller's choice and Amazon Bedrock routes each request for processing.
- [4]
GLM 5.3 supports implicit (automatic) prompt caching by default, and explicit cache controls (recommended) on the Responses and Chat Completions APIs.
- [5]
For agentic workloads that resend large system prompts or repository context every turn, caching reduces both latency and input cost.
- [6]
On Amazon Bedrock, GLM 5.3 is used through fully managed APIs with cross-Region inference, prompt caching and service tiers, and customers do not manage any infrastructure.
- [7]
Meeting coding and agentic demands with open-weight models has historically meant provisioning and operating your own inference infrastructure.
- [8]
GLM 5.3 can be invoked through the OpenAI-compatible Responses and Chat Completions APIs, or the Amazon Bedrock Invoke and Converse APIs.
- [9]
Z.ai claims competitive performance on coding benchmarks including DeepSWE, Terminal Bench 3.0 and FrontierSWE.
- [10]
Z.ai reports a 50% improvement over GLM 5.2 on its own internal coding benchmark.
- [11]
Direct comparisons to GLM 5 were not reported because the magnitude of improvements led to updating the benchmark tests themselves since the GLM 5.1 announcement.
- [12]
GLM 5 arrived on Amazon Bedrock earlier this year.
- [13]
Z.ai measured a leading score of 84.5 on the CyberGym benchmark at release.
- [14]
The AWS post demonstrates running an authorized security test of your own application with Strix, an open-source AI penetration testing agent; the optional demo requires Docker and Strix installed with the bedrock extra.
- [15]
Service tiers: Flex optimizes cost for less-time-sensitive workloads, Priority prioritizes latency-critical requests in return for a higher price, and Standard is the default balance between price and speed.
- [16]
Compared with GLM 5, the Bedrock integration for GLM 5.3 adds improved feature parity of the OpenAI-compatible Responses and Chat Completions APIs alongside Invoke and Converse.
- [17]
Callers need IAM permissions to call the base model and the target inference profile: bedrock:InvokeModel, bedrock:InvokeModelWithResponseStream and bedrock:CallWithBearerToken.
- [18]
GLM 5.3, as published on Hugging Face Hub, is a 753B-parameter mixture-of-experts model optimized for coding and long-horizon agentic tasks.
Sources
2 independent publishers whose own reporting we read for this story.
- aws.amazon.comGLM 5.3 by Z.ai is now generally available on Amazon Bedrock
2 articles · October 5, 2026
- runtimewire.comZ.ai adds GLM-5.3 to Amazon Bedrock for enterprise coding agents
1 article · October 5, 2026
Topics and entities
Topics
- Agentic Coding and Long-Horizon Tasks
- Managed hosting of open-weight models
- AI security testing