Humanoid Service and Consumer Robots

Published October 18, 2026

Law checked through October 18, 2026.

A humanoid or service robot is governed principally by its functions, setting, users, data, and product classification. A machine working in a factory raises workplace rules; a consumer product may fall within CPSC jurisdiction; a device intended for medical purposes can raise FDA requirements. Texas product liability, negligence, disability access, privacy, and applicable TRAIGA provisions remain relevant. A humanlike appearance does not create a comprehensive separate legal code. [1; 2; 3; 4]

Begin with intended and actual use

A general-purpose platform can be sold with several capabilities but deployed for a limited task. The legal assessment should identify the actual task, permitted environment, payloads, users, and foreseeable interactions. A manufacturer describing a machine as an assistant does not decide whether its intended medical use makes it a device or whether its customary consumer use brings it within consumer-product law. [1, § 2052(a)(5); 3]

The same hardware can therefore require distinct deployment records. A warehouse humanoid lifting containers, a hotel robot delivering towels, and a household assistant interacting with children expose different people to different hazards. An approval limited to one setting should not be assumed to support all three. Product instructions, sales claims, configured functions, and the customer's actual use should be examined together.

Workplace applications

Covered employers retain duties under the OSH Act and applicable standards. Robot movement, tools, payloads, loss of balance, and servicing can create hazards requiring different controls. An industrial safety assessment should address the integrated application, not merely whether the robot's arm or leg passed a component test. Collaborative operation is a characteristic to evaluate, not an automatic exemption from safeguarding. [2; 5]

Training should explain permitted tasks, exclusion zones, recovery from a fall or malfunction, and who can authorize a new activity. A machine that can accept natural-language commands may need controls preventing an unreviewed instruction from expanding its task. Those are recommended deployment practices connected to the employer's actual hazards; they are not a claim that OSHA has enacted a universal humanoid staffing rule.

Public facilities and homes

A mobile service robot can interfere with accessible routes, exits, communication, and service animals. Texas Human Resources Code § 121.003 and applicable ADA requirements deserve independent review. Placing a robot in a lobby does not justify obstructing a required accessible route, and a voice-only interaction can be inadequate for some users. The relevant duties depend on the facility and service. [6; 7, §§ 36.211, 36.302, and 36.303]

For covered consumer products, the manufacturer, distributor, or retailer must consider CPSC reporting when information reasonably supports the conditions in CPSA § 15(b). A business should first determine jurisdiction, because the consumer-product definition excludes specified categories and does not cover every industrial machine. Reporting is not limited to products already involved in an injury, and a voluntary software change does not necessarily eliminate the reporting inquiry. [1, §§ 2052(a)(5) and 2064(b); 8]

Liability for autonomous actions

Texas Chapter 82 governs covered product claims and separately addresses design defects, nonmanufacturing sellers, indemnity, and compliance presumptions. A robot's unexpected behavior is not alone proof of a defect; the plaintiff must establish the applicable elements. The deployment can also raise independent questions about maintenance, task selection, supervision, premises conditions, and warnings. [4, §§ 82.001 through 82.005 and 82.008]

Post-sale changes deserve particular attention. A new tool, learned behavior, cloud model, or software update may change the risk, while control may be divided among manufacturer, integrator, and customer. The contract should identify who approves updates, tests changed behavior, delivers safety notices, and preserves evidence. The actual legal effect remains claim-specific; no general conclusion that all later software behavior is either solely a manufacturer defect or solely an operator fault is justified.

Cameras, conversations, and identification

Robots may collect interior maps, voices, faces, and location history. An ordinary image and a statutory biometric identifier are not interchangeable. CUBI's listed identifiers, commercial-purpose requirements, and current AI-related exceptions must be read together. TDPSA coverage and consumer-data rules require an additional analysis, particularly where a robot moves between a business, a home, and an employment setting. [9; 10]

TRAIGA can reach qualifying physical AI, but its prohibitions and disclosures depend on the actor, purpose, intent, and provision. A government reception robot and an AI-assisted health care interaction can raise specific disclosure duties. The Act should not be presented as a blanket private-sector labeling or humanoid licensing requirement. [11, §§ 551.001 and 552.051 through 552.057]

Standards and security restrictions

Consensus standards can assist assessment within their actual scope. ISO 13482 addresses personal-care robot safety within its stated boundaries, while industrial standards address different applications. The existence of a standard does not mean every humanoid has been certified to it or that it is a Texas statute. Proprietary clauses should be obtained before any detailed conformance claim is made. [12]

Equipment authorization and federal security listings can create a separate sourcing issue for particular foreign-produced robots. The actual Covered List entry and conditional approval control the product-specific result. A listing affecting new equipment authorization should not be described as a universal prohibition on ownership of every foreign robot. [13]