All coverage
Milestone note Jul 28, 2026

The US bans new Chinese humanoid robots — a national-security wall around the robot buildout

The Trump administration, via an FCC order after an interagency national-security review, barred imports of new Chinese humanoid and quadruped robots (and grid/data-center power inverters), citing risks of disruption, data theft and cyberattacks to the US AI supply chain. It reshapes the humanoid market just as Chinese makers were sweeping global funding and deployment rankings.

The Trump administration barred imports of new Chinese humanoid and quadruped robots, along with connected power inverters used in grids and data centers, in measures released by the FCC after the White House convened an interagency national-security panel. Officials framed it as protecting the US AI supply chain from disruption, data theft and cyberattacks — and as pressure to reshore manufacturing of industries slated for explosive growth. The order lands the same week Chinese startups swept a global humanoid funding-and-deployment ranking.

Why it matters

This draws a security border straight through the humanoid market, and the two sides fall out immediately. Chinese leaders — Unitree, AgiBot — lose access to the US market just as they were scaling and heading for IPOs; US and allied makers (Figure at BMW, Tesla's Optimus, Apptronik) get a protected home market for the multi-trillion-dollar buildout forecasters keep sizing. The "inverters" half is the quieter tell: the same national-security logic that walled off telecom gear is now being applied to the physical layer of the AI economy — robots and grid hardware — meaning supply-chain provenance, not just capability, becomes a gating factor. The risk is cost and speed: cutting off the cheapest, most advanced hardware could slow US deployment even as it protects it.

What to watch

The order's scope and enforcement detail (what counts as "new," component-level rules), Chinese makers' response and any WTO challenge, and whether US/allied supply can fill the gap without blowing up deployment timelines.

Who's involved