DOBOT lists Atom as a biped humanoid platform. The manufacturer's product listing is the source for retained characteristics; independent task success evidence needs separate measurement.
Does the Atom product listing mean I can buy one today?
A model appearing on a manufacturer's website may be a demonstration, enterprise lead or commercially supplied robot. Check whether the requested hardware revision has a written quotation, delivery region, support agreement, training tools, spare parts and service conditions. The catalog status 'listed by manufacturer' is intentionally different from confirmed retail availability.
After watching a product demonstration, buyers still need to establish whether a commercial version exists, what operating software is supplied and which functions require human control.
Testing an Atom task rather than a static pose
For a biped part-transfer trial, require a fixed payload, known floor, repeatable route and timed object placement. Count falls, human corrections, rejected placements and charge interruptions. Publish the complete trial set before comparing it with industrial stationary arms, whose narrower workspace may produce a much higher throughput for the same task.
Atom's development interface is a procurement issue
An engineering team should distinguish high-level task-control APIs from joint-level interfaces. Model names, hand types, cameras and software access can vary by Atom configuration. Ask for the supported controller example and its safety limits before planning an in-house learning policy.
What a factory Atom trial would need to report
Choose one actual part and fixture, specify the required reach and placement tolerance, then log first-attempt success, corrections, rejected assemblies and operator intervention. The vendor's product listing is an initial source for capabilities, while a customer-site acceptance log would be needed to establish sustained production performance.
What would a buyer need before ordering a DOBOT Atom?
DOBOT lists Atom as a humanoid platform, while the catalog retains manufacturer-listed status rather than confirmed online retail availability. For a procurement decision, ask for the exact orderable variant, price basis, warranty, spare joints, battery support, controller API and supported deployment region. A marketing product page may not specify delivery lead time or the revision represented in a public video.
Ask for a live demonstration of the precise task being purchased and a recorded trial log. An enterprise robot contract should specify acceptance criteria, training obligations and service response. The physical robot, software license and any teleoperation service may have different contract terms.
Can one Atom policy work on a different robot's hardware?
A learned behavior depends on the source robot's joint mapping, actuator response, sensor placement and action frequency. Reusing it on another humanoid may require retargeting, retraining and physical safety tests. Before assuming cross-robot compatibility, request the description of the policy interface and check whether demonstrations used a single robot or several hardware variants. A policy video cannot by itself establish transfer performance.
Which software rights matter when an institution buys Atom?
The product price may be only one part of a research deployment. A university needs to know whether it can inspect joint commands, collect raw observations, install custom policies and keep recorded datasets. Ask for the software license, SDK version, external sensor support and hardware maintenance arrangements for the exact Atom configuration.
For a laboratory exercise, define a reference manipulation task and require a live demonstration with the software tools that will be delivered. A closed demonstration application can produce good footage while providing little scope for independent research. Service availability and replacement parts need written confirmation before the institution commits its teaching schedule.