Agility Robotics Begins Nasdaq Trading as AGLT After Churchill SPAC Merger

Agility Robotics began trading on Nasdaq as AGLT on November 5, 2026, completing its business combination with Churchill Capital Corp XI. The Salem, Oregon company bills itself as the first U.S. publicly listed pure-play humanoid robotics firm with active commercial deployments, not merely laboratory prototypes.

The deal and related financings brought roughly four hundred sixty-five million dollars in gross capital before expenses, while customer commitments for Digit 5 exceeded three hundred million dollars across multi-year orders subject to milestones. Agility cited nearly sixty-five thousand operational hours across real-world deployments—a metric public-market investors can track alongside quarterly revenue.

Shares were volatile out of the gate. StockAnalysis data showed AGLT closing at $9.90 on November 6, down nearly fourteen percent in the session after debuting near $11.51 on day one. After-hours quotes hovered around $9.87 into November 7, reflecting skepticism as much as excitement about humanoid unit economics.

The humanoid category competes with well-funded private rivals and divergent form factors—wheeled logistics bots, teleoperation-first systems, and software-only autonomy stacks. Agility's bet is that bipedal manipulation wins in warehouses with human-scale aisles and mixed SKU handling.

Investors should read SPAC-era warrants and milestone-heavy order books carefully. Multi-year Digit commitments are promising but not guaranteed revenue; deferral clauses tied to performance and feature delivery matter.

Safety and labor narratives will follow every public humanoid. Agility must demonstrate incident rates, maintenance downtime, and workforce transition plans to avoid the backlash that hit earlier automation waves.

For technology strategists, AGLT is a liquid marker on physical AI—a complement to the model-layer financing headlines dominating the same week. Capital markets now price both bits and bolts.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.

Quarterly reviews should pair vendor roadmaps with your own risk register entries, not slide decks.

Documentation beats memory when regulators ask how automated tools were supervised.

Treat model policy changes like firewall rule changes: ticketed, reviewed, and reversible.