1X NEO

• livium.com/humanoids/neo69 values
• aparobot.com/robots/neo62 values
• 1x.tech/neo59 values
• robotoverflow.com/en/robot-database/1x-neo/43 values
• roboatlas.ai/en-US/products/1x-neo40 values
• humanoid.guide/product/neo/34 values
• humanoid-robots.io/robot/neo-by-1x-technologies33 values
• robotsatlas.com/robots/1x-neo31 values
• humanoidapplications.com/robot/1x-neo/29 values
• robozaps.com/products/neo27 values
• humanoidpress.jp/1x-technologies-neo/26 values
• 1x.tech/discover/neo-home-robot26 values
• 1x.tech/order20 values
• 1x.tech/discover/neo-factory19 values
• biorobot.ai/en/robot/1x-neo19 values
• robotico.market/1x-technologies/neo19 values
• 1x.tech/discover/neos-hands16 values
• humanoid-world.com/roboter/1x-neo/15 values
• humanoidrecord.com/robots/1x-neo/9 values
• guijicankao.com/products/1x-neo6 values
• 1x.tech/2 values
• 1x.tech/2 values
• 1x.tech/legal2 values
• 1x.tech/about2 values
• 1x.tech/discover/1x-humanoid-robot-neo-featured-in-nvidia-gtc-keynote1 value
• 1x.tech/privacy-policy1 value

A value below no longer shows on the page — it was superseded, or withdrawn after review. Kept here, not deleted, with the reason it was withdrawn.

• Charge time: 6 min2026-09-27

  This was a RATE, not a duration. 1X's own words are "Quick charge 6min per hour runtime": six minutes of charging buys one hour of running, so the 6 is the numerator of a ratio whose denominator is the runtime. This field is the time to charge the robot fully, and livium states the same vendor fact completely — "can fast-charge to full in about 24 minutes (6 minutes per hour of runtime)" — which is the value four independent sources give and the one this key now shows.

• Battery capacity: 842 Ah2026-09-27

  This field holds a charge capacity in Ah or mAh, and its own rules exclude an energy figure in Wh — which is what this number is. 1X publishes "Capacity 842 Wh", restated by nine directories and stored under battery energy. livium copied that same 842 into a column headed mAh, so the quote reads "Battery Capacity 842000 mAh" and the value became 842 Ah — roughly 42 kWh, about fifty times the pack 1X publishes, in a 30 kg robot. No source states any charge capacity in Ah or mAh for NEO.

• Field service: Remote2026-09-27

  The quote is about TELEOPERATION, which this row's own REJECT names: "on-site or remote said of something else (on-site training, remote teleoperation, a remote operator) — the page must say the SERVICE or repair is on-site / depot / remote". Re-gated with the production gate() against this same cached page, the statement now FAILS enum:not-in-quote: not one of the REMOTE option's six declared aliases (remote support, remote service, remote diagnosis, online support, 远程支持, 远程协助) is in the quote. It only ever passed because a long option CODE counted as its own spelling, the hole closed on 2026-09-25 whose three measured removals were exactly these. Control: "remote diagnosis and remote service are included for every NEO owner" still PASSES as REMOTE, so the rule is not refusing the concept.

• Field service: Remote2026-09-27

  The quote is about TELEOPERATION, which this row's own REJECT names: "on-site or remote said of something else (on-site training, remote teleoperation, a remote operator) — the page must say the SERVICE or repair is on-site / depot / remote". Re-gated with the production gate() against this same cached page, the statement now FAILS enum:not-in-quote: not one of the REMOTE option's six declared aliases (remote support, remote service, remote diagnosis, online support, 远程支持, 远程协助) is in the quote. It only ever passed because a long option CODE counted as its own spelling, the hole closed on 2026-09-25 whose three measured removals were exactly these. Control: "remote diagnosis and remote service are included for every NEO owner" still PASSES as REMOTE, so the rule is not refusing the concept.

• Field service: Remote2026-09-27

  The quote is about TELEOPERATION, which this row's own REJECT names: "on-site or remote said of something else (on-site training, remote teleoperation, a remote operator) — the page must say the SERVICE or repair is on-site / depot / remote". Re-gated with the production gate() against this same cached page, the statement now FAILS enum:not-in-quote: not one of the REMOTE option's six declared aliases (remote support, remote service, remote diagnosis, online support, 远程支持, 远程协助) is in the quote. It only ever passed because a long option CODE counted as its own spelling, the hole closed on 2026-09-25 whose three measured removals were exactly these. Control: "remote diagnosis and remote service are included for every NEO owner" still PASSES as REMOTE, so the rule is not refusing the concept.

• Bluetooth: Bluetooth2026-09-27

  The row's REJECT names this exact shape too: "a 'Bluetooth: Yes / supported' cell — this key is the version number only". The stored quote is aparobot's Connectivity bullet "Bluetooth supported" and the stored value is the word "supported".

• Bluetooth: supported2026-09-27

  The row's REJECT names this exact shape too: "a 'Bluetooth: Yes / supported' cell — this key is the version number only". The stored quote is aparobot's Connectivity bullet "Bluetooth supported" and the stored value is the word "supported".

• Robot OS: Proprietary2026-09-27

  "Proprietary" is a non-disclosure, not an operating system, and this row's REJECT already covers the class: "a cell that says N/A, none or 'not published' — that is not a value". The key keeps three real values (1X OS, 1X OS (Nvidia Jetson Thor), Ubuntu Linux 24.04).

• Degrees of freedom: 752026-09-27

  A DERIVED value, which CLAUDE.md forbids storing as a spec: robozaps's own text is "Degrees of freedom 75 total, DERIVED FROM PUBLISHED JOINT COUNTS" — the page says it computed the number rather than reading it. The other seven statements of 75 are independent and stay, so the key and the shown value are unchanged.

• Torque density: 5.5 N·m/kg2026-09-27

  A dimensionless MULTIPLE stored as N·m/kg: guijicankao's "扭矩重量比5.5倍" is "torque-to-weight ratio 5.5 TIMES" (倍 = fold/times) — no unit at all. The row's ACCEPT is "a stated N.m/kg number"; compare unitree-h1's real "Peak Torque Density 189N.m/Kg". This is the same class as CLAUDE.md's RULE UNITLESS.

• Speaker power: 3 W2026-09-27

  A COUNT of speakers stored as watts: every one of these quotes counts loudspeakers — "3 stage speaker in pelvis and chest area", "3 speakers", "3-stage speakers", "3-stage speaker system". The row's unit is W and its ACCEPT is "speaker power in W"; compare unitree-g1's real "5W Speaker". 1X publishes no speaker wattage.

• Speaker power: 3 W2026-09-27

  A COUNT of speakers stored as watts: every one of these quotes counts loudspeakers — "3 stage speaker in pelvis and chest area", "3 speakers", "3-stage speakers", "3-stage speaker system". The row's unit is W and its ACCEPT is "speaker power in W"; compare unitree-g1's real "5W Speaker". 1X publishes no speaker wattage.

• Speaker power: 3 W2026-09-27

  A COUNT of speakers stored as watts: every one of these quotes counts loudspeakers — "3 stage speaker in pelvis and chest area", "3 speakers", "3-stage speakers", "3-stage speaker system". The row's unit is W and its ACCEPT is "speaker power in W"; compare unitree-g1's real "5W Speaker". 1X publishes no speaker wattage.

• Speaker power: 3 W2026-09-27

  A COUNT of speakers stored as watts: every one of these quotes counts loudspeakers — "3 stage speaker in pelvis and chest area", "3 speakers", "3-stage speakers", "3-stage speaker system". The row's unit is W and its ACCEPT is "speaker power in W"; compare unitree-g1's real "5W Speaker". 1X publishes no speaker wattage.

• Speaker power: 3 W2026-09-27

  A COUNT of speakers stored as watts: every one of these quotes counts loudspeakers — "3 stage speaker in pelvis and chest area", "3 speakers", "3-stage speakers", "3-stage speaker system". The row's unit is W and its ACCEPT is "speaker power in W"; compare unitree-g1's real "5W Speaker". 1X publishes no speaker wattage.

• Made in: United States2026-09-24

  exclusive family "country": "initial US shipments scheduled for 2026." proves availabilityRegions on its own alias; it says nothing about manufacturing, which this row's own NOT text forbids

• Made in: United States2026-09-24

  exclusive family "country": "initial US shipments scheduled for 2026." proves availabilityRegions on its own alias; it says nothing about manufacturing, which this row's own NOT text forbids

• Hand DoF: 222026-09-24

  exclusive family "handdof": the same quote on the same page proves handActiveJointCount more specifically

• Sensors: Stereo camera2026-09-24

  list-subset: the same quote also states IMU, STEREO_CAMERA, of which this is a subset

• Sensors: IMU2026-09-24

  list-subset: the same quote also states IMU, STEREO_CAMERA, of which this is a subset

• Applications: Manufacturing2026-09-24

  list-subset: the same quote also states LOGISTICS, MANUFACTURING, RETAIL, of which this is a subset

• Applications: Logistics2026-09-24

  list-subset: the same quote also states LOGISTICS, MANUFACTURING, RETAIL, of which this is a subset

• Applications: Retail2026-09-24

  list-subset: the same quote also states LOGISTICS, MANUFACTURING, RETAIL, of which this is a subset

• Price from (USD): $2002026-09-24

  exclusive family "price": the same quote on the same page proves depositUsd more specifically

• Price from (USD): $2002026-09-24

  exclusive family "price": the same quote on the same page proves depositUsd more specifically

• Price from (USD): $2002026-09-24

  exclusive family "price": the same quote on the same page proves depositUsd more specifically

• Run-to-charge ratio: 62026-09-24

  the pinned gate no longer accepts this quote for runToChargeRatio

• Peak payload: 69.85 kg2026-09-24

  exclusive family "load": the same quote on the same page proves liftLoadKg more specifically

• Peak payload: ≥ 68.04 kg2026-09-24

  exclusive family "load": the same quote on the same page proves liftLoadKg more specifically

• Peak payload: ~70 kg2026-09-24

  exclusive family "load": the same quote on the same page proves liftLoadKg more specifically

• Payload per arm: 25 kg2026-09-23

  audit cleanup: subject-mismatch — robotoverflow's sentence reads 'its tendon-driven design delivers a 70 kg payload and 25 kg carrying capacity' — the quote contains no per-arm wording at all, and 25 kg is the whole-robot carry (1X's own page: 'Carry 55 lbs' = 24.95 kg). registry loadPerArmKg ACCEPT: 'payload of ONE arm'; NOT: 'total payload of both arms or of the whole robot'. Four loadPerArmKg statements survive, including the v

• Price from (USD): $20,0002026-09-23

  audit cleanup: price-basis — robotoverflow's lede: 'Price: estimated ~$20,000 for consumer pre-order, early-access at $2,000,000.' A 100× typo (the same sentence's own estimate two clauses earlier is $20,000), live today as a $2,000,000 offer row.

• Price from (USD): $2,000,0002026-09-23

  audit cleanup: price-basis — robotoverflow's lede: 'Price: estimated ~$20,000 for consumer pre-order, early-access at $2,000,000.' A 100× typo (the same sentence's own estimate two clauses earlier is $20,000), live today as a $2,000,000 offer row.

• Data generated: Location2026-09-23

  audit cleanup: subject-mismatch — Context: the quote sits under 'Information collected automatically … about you, your computer or mobile device, and your interaction over time with our website … using cookies'. registry dataTypesGenerated NOT names this case verbatim: 'what the vendor's WEBSITE or app collects from visitors (cookies, IP address, browser data in a website privacy policy)'; ACCEPT is 'kinds of data the ROBOT itself

• Max joint torque: 3.5 N·m2026-09-23

  audit cleanup: subject-mismatch — Full sentence on the page: 'Peak torques reach 3.5 Nm at the thumb CMC and 2.6 Nm at the finger MCP joints, with distal flexion forces up to 45N. The wrist delivers 17.75 Nm of torque.' registry maxJointPeakTorqueNm ACCEPT: 'highest joint torque of the WHOLE robot (usually a knee, hip or other leg joint)'; NOT: 'torque of a finger, thumb, hand or wrist joint (use jointPeakTorqueNm)'. 3.5 Nm is the

• Degrees of freedom: 122026-09-23

  audit cleanup: subject-mismatch — The directory's own row reads 'DOF: 12 DoF arms + hands' and its Payload row reads '~5 kg per arm', so 12 is explicitly arms+hands only. registry jointCountTotal NOT: 'a DoF count of one hand or arm only'. Three surviving statements give 75.