1X Technologies
1X Technologies (formerly Halodi Robotics) is a Norwegian-American humanoid robotics company building general-purpose bipedal robots designed to live and work alongside people. Founded in 2014 in Norway by Bernt Øyvind Børnich, the company is now headquartered in Palo Alto, California with R&D and manufacturing presence in Moss, Norway and a new vertically integrated NEO factory in Hayward, California. 1X is backed by the OpenAI Startup Fund, EQT Ventures, Tiger Global, Samsung NEXT, and others through Series A2 ($23.5M, 2023), Series B ($100M, 2024), and a $1B raise reported in 2025. Its commercial robots are EVE — a wheeled upper-humanoid deployed in industrial and security settings since 2022 — and NEO, a bipedal home humanoid that began pre-orders October 28, 2025 at $20,000 (or $499/month) with consumer deliveries in 2026. 1X also acquired Kind Humanoid (Jan 2025) and announced a partnership to deploy up to 10,000 NEO robots into EQT portfolio company factories and warehouses between 2026 and 2030. Unlike most humanoid robotics vendors, 1X publishes meaningful open-source artifacts: the EVE ROS2 API (custom WholeBodyTrajectory and DrivingCommand message types) and the halodi-messages package on GitHub under Apache-2.0, plus the 1X World Model Challenge with 100+ hours of vector-quantized EVE observations and GENIE baseline models released on Hugging Face. There is no public REST/HTTP developer API or hosted developer portal — the developer surface is ROS2 messages, robot models in URDF, and the world-model dataset/model artifacts.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles 1X Technologies the way a machine reads it — 2 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — 1X Technologies scores 13.5/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile 1X Technologies
Each block below is one kind of artifact we hold for 1X Technologies. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
1X Robotics Context
JSON-LDSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for 1X Technologies — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Company 8
The organization behind the API
Scroll within the panel for all 8 ·
Other 9
Properties that don't map to a standard resource type
Scroll within the panel for all 9 ·
← All providers · Data indexed from github.com/api-evangelist/1x-robotics · machine-readable index on apis.io