German tech outlet Dr. Web reported on October 6, 2026 that Zhipu AI earns revenue from each GLM 5.3 call on Amazon Bedrock even though the company and affiliates are on the U.S. Commerce Department’s Entity List. The article explains that AWS runs its own copies of the model so prompts and outputs stay with Amazon while Zhipu receives a share of Bedrock revenues.
This article aggregates reporting from 3 news sources. The TL;DR is AI-generated from original reporting. Race to AGI's analysis provides editorial context on implications for AGI development.
The Dr. Web piece highlights a subtle but important development: a Chinese frontier‑model lab on the US Entity List is now monetizing directly through a major American cloud. Because export controls focus on the flow of technology and data rather than payments, AWS can legally host GLM‑5.3 in its own accounts and remit a per‑call revenue share to Zhipu while keeping customer prompts and outputs inside Amazon‑controlled infrastructure. That arrangement turns sanctions compliance into an implementation detail rather than an absolute barrier.
From an AGI‑race perspective, this shows how market and regulatory logics can diverge. Washington wants to slow China’s military‑aligned AI progress; AWS customers want access to high‑performing, relatively cheap open‑weight models; Zhipu wants foreign currency and real‑world workloads. Bedrock stitches those incentives together in a way that gives Zhipu global demand signals and cash flow without direct access to Western user data. The article also notes that other clouds and Chinese providers are cutting similar revenue‑share deals, meaning GLM‑5.3 could become a de facto standard for coding and security agents across multiple jurisdictions.
For U.S. labs, the competitive implication is clear: even under tight export rules, Chinese open‑weight models can reach Western enterprise workflows through compliant intermediaries. That raises the bar for closed U.S. models on cost, latency and flexibility, especially in agentic and coding workloads where GLM‑5.3 is explicitly positioned.


