1X

A company developing general-purpose humanoid robots for tasks like security patrols, basic logistics, and home assistance.

shipped 2 avr. 2026aifreemium

Pourquoi c'est important

1ai

Stork Quadrant

Sleeping Giant· 33/100

Has a real moat but invisible to agents. Add an MCP and you'd climb.

“1X has real defensibility because the core value is hardware + embodied execution, not software alone. An LLM can't patrol your building or move a box. The regulatory moat (safety certification, liability for autonomous systems) and the data moat (real-world sensor logs from deployed units) compound over time. The trust moat is critical — you're betting your security or logistics on a robot that must not fail catastrophically. This is not replaceable by an agent.”
— Claude Haiku 4.5, scored 2026-05-26

Defensibility · 60/100

Physical-world coupling
Regulatory moat
Network liquidity
Proprietary refreshing data
High-trust catastrophic workflows
Multi-party coordination
Brand / community / taste

An LLM alone could replace

Generating task plans or decision trees for robot behavior
Simulating or visualizing patrol routes or logistics workflows
Analyzing security footage or sensor data to flag anomalies

Agent-Readiness · 0/100

Verified MCP
Listed on agent surfaces
Usage-based pricing
Headless agent auth
Public OpenAPI
Active changelog
llms.txt

How to defend

Keep shipping units and accumulating real-world operational data that trains the next generation. Lean into the liability story — own the insurance and certification burden so customers don't have to. Build the two-sided logistics network where enterprises and venues compete to deploy your robots, creating network effects around utilization and uptime.

Ship an MCP server and list it on Stork — biggest single point gain (+25).
Get listed in the Anthropic MCP registry, Cursor, or Claude Desktop (+20).
Add a usage-based or per-call tier; per-seat-only pricing dies when agents replace seats (+15).
Expose API-key auth with a self-serve sandbox tier; remove sales-call gates (+15).
Publish an OpenAPI spec at /openapi.json or /.well-known/openapi (+10).

How this score is computed →See the full quadrant How to defend

overview