Skip to content
Botlero

Corrections

Every value Botlero has stopped publishing is kept, not deleted, with the reason that was recorded when it was withdrawn and a link to the page that published it. Newest first, across every robot.

An entry says a value stopped being published and why. It does not say what replaced it: often nothing did, and where something did, the replacement is on the robot's own page with its source and its date.

Two kinds of recorded change are not withdrawals, and are not listed here. A robot going live is a publication rather than a value being taken away, so those are listed by month below, under “robots added”. And where a value was withdrawn but the old value itself was never recorded, the reason is kept but there is nothing to show, so no entry is made for it.

RSS feed of new robots and corrections

683 withdrawn values · 485 recorded reasons · newest 2026-09-30

2026-09-2377 values, 75 reasons · 42 on this page

  1. audit cleanup: cross-product — Agree. Same footer link, but the citing page is unitree.com/cn/go2/battery — a page about the Go2 quadruped's battery pack. Citing it in G1's evidence popover misattributes provenance. The identical value survives on support.unitree.com/home/en/G1_developer (a G1 page) and on cn/terms (#5, kept).

    1. Unitree G1Vulnerability disclosure link2026-09-23 · specification

      https://security.unitree.comunitree.com

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  2. audit cleanup: third-party-url — humanoid.guide's own WordPress upload (/wp-content/uploads/2024/07/).

    1. Unitree G1Logo2026-09-23 · specification

      https://humanoid.guide/wp-content/uploads/2024/07/Unitree-300x90.pnghumanoid.guide

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  3. audit cleanup: third-party-url — aparobot.com's own Webflow CDN copy.

    1. Unitree G1Logo2026-09-23 · specification

      https://cdn.prod.website-files.com/67e2a642c1cc92a3140c2707/67e6e5a19082776d20e74805_Unitree%5B1%5D.svgaparobot.com

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  4. audit cleanup: third-party-url — The value is humanoid-robots.io's own Webflow CDN copy of the Unitree logo (cdn.prod.website-files.com/68835962…). registry logoUrl ACCEPT: 'URL of the maker's logo image, copied exactly from the vendor page'. Unitree's own logo survives (support.unitree.com/assets/LOGO_en-a45e0c50.png) and stays the column value.

    1. Unitree G1Logo2026-09-23 · specification

      https://cdn.prod.website-files.com/68835962f272eff6d5e9270e/6923c6cf9ad3d806d19879b5_Unitree%20Robotics.svghumanoid-robots.io

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  5. audit cleanup: subject-mismatch — Same value on the G1 developer page, whose rendered table shows 'Arm Span | About 0.45M | About.45M' for both variants. Same reasoning as #12. This statement carries variantId = G1.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  6. audit cleanup: twin of a listed defect — CN twin of #12/#13, not in the cleanup list. Verified live: active, rank PREFERRED, source VENDOR, num=450, variantId=null. Page context shows '* 小腿+大腿长度 0.6M 0.6M' immediately above '* 手臂臂展 约0.45M 约0.45M', and the same table's 手臂最大负载 is 约2Kg — it is Unitree's single-arm row. registry armSpanMm NOT is literally 'single arm length'; 450 mm fingertip-to-fingertip is impossible on a 1320 mm robot who

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  7. audit cleanup: subject-mismatch — Unitree's own G1 table prints 'Calf + Thigh Length 0.6M' directly above 'Arm Span About 0.45M', and the same table's H×W×D gives a 450 mm body width. A 450 mm fingertip-to-fingertip span is impossible on a robot whose shoulders alone are 450 mm wide and which stands 1320 mm tall — it is one arm, mislabelled in Unitree's English column. registry armSpanMm ACCEPT: 'fingertip-to-fingertip span with a

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  8. audit cleanup: subject-mismatch — humanoid.guide's table pairs 'Degrees of freedom, overall | 23' with 'Degrees of freedom, hands | 14' — 14 is both hands. Unitree's own page states 'Single Hand Degrees of Freedom … 7'. registry handJointCount ACCEPT: 'DoF of ONE hand'; NOT: 'DoF of both hands added'. Vendor 7 survives and remains the column value.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  9. audit cleanup: number-wrong — Same, G1 developer page.

    2 values · recorded by audit-cleanup:2026-09-23 · link to this reason

  10. audit cleanup: number-wrong — Same, English page.

    2 values · recorded by audit-cleanup:2026-09-23 · link to this reason

  11. audit cleanup: number-wrong — 1320 stored as depth. registry example: '1320x450x200mm -> depth 200 mm'; 20 cm is already stored and survives.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  12. audit cleanup: number-wrong — 1320 is the HEIGHT of the H×W×D string, stored as width. The registry example for this very string is '1320x450x200mm -> width 450 mm', and the correct 450 mm (45 cm) is already stored and survives.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  13. audit cleanup: number-wrong — aparobot's own spec list reads 'Length - 200 mm / Width - 4550 mm / Height (ResT) - 690 mm / … / Height (Max) - 1320 mm' — 4550 is aparobot's typo for 450 (its own Intro sentence on the same page says '450 mm wide'). Stored as 455 cm, a 4.55-metre-wide G1 is live today. (The list's reason text misattributes the typo to humanoid.press; the URL and the page are aparobot's.)

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  14. audit cleanup: number-wrong — Same defect, G1 developer page.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  15. audit cleanup: number-wrong — Same defect, English page.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  16. audit cleanup: number-wrong — heightCm is a RANGE key, so the parser read '1320x450x200mm' as the range 1320–450 and stored 45–132 cm: 'G1 is between 45 cm and 132 cm tall'. The registry example for this exact string is '1320x450x200mm -> width 450 mm'. The correct height (132 cm) is stored by a separate statement from the same table and survives, so heightCm stays 132.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  17. audit cleanup: price-basis — 'base price of around $16,000' — 'around'. registry NOT: 'an estimate or target price'.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  18. audit cleanup: price-basis — 'estimated $16,000-20,000' — the word 'estimated' plus a range.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  19. audit cleanup: price-basis — '$16,000–$30,000 depending on configuration' — a range plus 'depending on'; the span mixes G1 and G1 EDU with no variantId.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  20. audit cleanup: price-basis — '$30,000+ G1 EDU' is a different variant's price stored with variantId=null, so it renders as the base G1's. registry NOT: 'a different model or accessory'. G1 EDU is a declared variant, so the fix is re-extraction with a variantId, not keeping it unlabelled.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  21. audit cleanup: price-basis — 'Price: $13,500–$73,900' is a third-party range spanning base to top configuration; 'price from' cannot be read off it as a list price. The same 13,500 survives from Unitree's own 'Price from $13.5K' and from three directories quoting a plain base price.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  22. audit cleanup: price-basis — 'Price (est.) $16,000' — the directory's own field label says estimate. registry priceFromUsd NOT: 'an estimate or target price'.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  23. audit cleanup: price-basis — 'target price of ~USD 20,000.' — 'target' plus '~'.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  24. audit cleanup: price-basis — DISAGREE with 'review' — close it. In context humanoid.press prints '**Pricing** - $130,000' with no basis and immediately follows it with its own heading 'Figure AI has NOT published:'. Figure publishes no price; the other three directories say ~$20,000 target / $50,000–150,000 estimated / ~$20,000 target. Because #38–#40 close, keeping this one makes a single unsourced directory figure the sole,

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  25. audit cleanup: price-basis — 'Price $50,000 - $150,000 Estimated' — labelled Estimated, and a 3× range.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  26. audit cleanup: price-basis — The quote contradicts itself as a price: 'Figure has stated a target consumer price around $20,000 at production scale, with enterprise deployments potentially reaching $100,000, but no official MSRP has been confirmed.' registry NOT: 'an estimate or target price'. This is the PREFERRED statement behind Robot.priceFromUsd = 20000.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  27. audit cleanup: subject-mismatch — The quote is one bullet in a battery-attributes list on a battery-development post: 'Fast Charge: 2 kW fast charge with active cooling', alongside 'Run Time', 'Mass & Volume Efficiency', 'Battery Management System'. registry coolingType ACCEPT: 'joint/body cooling method'; NOT: 'cooling of a charger'. Only statement → key disappears.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  28. audit cleanup: subject-mismatch — The quote is the standard consent-to-policy sentence in the first paragraph of Figure's website privacy policy ('Last updated: January 21, 2026'); it says nothing about training. It matched only because 'consent' is an OPT_IN alias. registry trainsOnCustomerData ACCEPT: 'whether customer data is used to train the AI'. Only statement → key disappears, which is correct: Figure publishes no such stat

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  29. audit cleanup: enum list corrected — Confirmed against the page. aparobot's Software Package field reads: 'Safety compliance software certified to ANSI B11.0, ISO 12100, ISO 13849, ANSI B11.19, ISO 10218, and ANSI/RIA R15.08.' Stored enumList is ['ISO_10218','ISO_13849','ISO_TS_15066']; ISO/TS 15066 is never mentioned. It entered through the registry alias bug (registry.txt:203 writes 'ISO_TS_15066=iso/ts 15066/ts 15066' and '/' is t

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  30. audit cleanup: price-basis — 'Price: around $250,000.' — 'around'.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  31. audit cleanup: price-basis — 'Price | $250K' from livium's Digit V2 quick-stats table — a different generation (the same table gives height 175 cm, weight 64.8 kg, model year 2023).

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  32. audit cleanup: price-basis — 'US$ 50,000-100,000' — a range, and from originofbots' OLD Digit page (a different generation).

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  33. audit cleanup: price-basis — Context is decisive: originofbots prints 'Enterprise pricing, typically custom-quoted; likely >$100,000 per unit' and labels the whole field 'Estimated · Typical range for commercial humanoid robots in this class' — a class-level guess, not a Digit price.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  34. audit cleanup: price-basis — 'Price RaaS subscription (~$250,000 purchase equivalent)' — registry NOT: 'rent, lease or subscription per month'; plus '~' and 'equivalent'. Not a purchase price at all.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  35. audit cleanup: price-basis — 'Price (est.) ~$250,000' — '(est.)' and '~'. PREFERRED statement behind Robot.priceFromUsd = 250000.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  36. audit cleanup: subject-mismatch — Same value from the 2023 launch press release ('Agility Robotics is excited to unveil the next generation of Digit'), which is the v4 machine, not today's Digit 5. Same reasoning. Close together with T3, the third copy of the same value.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  37. audit cleanup: subject-mismatch — The quote is the video page's own title line: 'The Next Generation of Digit: Enabling Humans to be More Human | Agility'. registry generation ACCEPT: "the robot's generation as printed ('third-generation', 'Gen 3')" — 'next generation' names no generation and cannot be rendered as one. Four statements survive, incl. the vendor's 'our fifth generation humanoid' and 'Digit® 5'; closing this moves Ro

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  38. audit cleanup: twin of a listed defect — Third copy of the same unusable value, not in the cleanup list. Verified live: active, rank NORMAL, source DIRECTORY. Context: livium prose about task-specific hands — 'The 2023 "next generation" model features newly designed end effectors'. Same defect as #24/#25: registry generation ACCEPT is "the robot's generation as printed ('third-generation', 'Gen 3')", and 'next generation' names no genera

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  39. audit cleanup: number-wrong — 'a vertical reach of 0 to 1,670 mm' — the LOW end of a range stored as the value, so the live spec card reads 'Reach 0 m'. Three statements survive giving 2.2 m.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

  40. 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.

    1 value · recorded by audit-cleanup:2026-09-23 · link to this reason

40 reasons per page. A robot's own withdrawals are listed on its page, under “Corrected values”. How a value gets published.