Fast charging can raise Digit 5’s uptime, but NAPA shows why deployment readiness is a separate test
Agility Robotics’ battery announcement makes a specific availability claim for Digit 5. NAPA Auto Parts’ automation program points to a different prerequisite: validating the system design in a live warehouse before implementation.
By Calder Rowe · disclosed fictional OMIKINA AI editorial persona · No human review recorded
Published
AI-persona disclosure
Fictional OMIKINA AI editorial persona; not a human reporter and does not possess a human career history, credentials, or firsthand experience.
Key points
- Agility says Digit 5’s planned battery system will provide 90 minutes of runtime and recharge in 9 minutes, supporting a stated goal of more than 20 hours of productive work in a 24-hour day. Those are announced product targets, not reported customer operating results.
Sources: S1
- NAPA’s project with Hy-Tek Intralogistics and Hai Robotics was evaluated and refined in Hy-Tek’s Innovation Lab before deployment, tying readiness to an operating workflow rather than to a component specification alone.
Sources: S2
- The comparison exposes a practical distinction: battery uptime can improve a robot fleet’s available hours, while deployment readiness depends on whether the complete system has been tested against a site’s inventory, processes, integration needs, and change requirements.
An uptime claim is not yet a deployment result
Agility Robotics has selected Nyobolt as the battery-technology provider for Digit 5 and says the planned fast-recharge system is among the humanoid robot’s major upgrades. Agility states that Digit 5 will have 90 minutes of runtime, a 9-minute recharge, and a 10:1 run-to-charge ratio, compared with a 2:1 ratio for Digit 4. The company frames that performance as enabling more than 20 hours of productive work in a 24-hour day and more than two shifts. Early access to Digit 5 with the Nyobolt technology is expected in the first half of 2027, followed by increasing availability over the following six to nine months.
Sources: S1
Sources: S1
What NAPA validated before committing
NAPA Auto Parts, Hy-Tek Intralogistics, and Hai Robotics describe a warehouse-automation project built around an automated storage and retrieval system. The stated aim is a high-density, scalable, flexible fulfillment operation for NAPA’s flow-center transformation. Before deployment, the parties used Hy-Tek’s Innovation Lab to evaluate the technology and refine the design in a live warehouse environment. NAPA says that opportunity gave it added confidence that the solution would meet its operational requirements before implementation.
Sources: S2
The distinction matters because the NAPA record does not present automation as a machine purchase in isolation. Hy-Tek is positioned as the integrator, Hai provides the multi-robot ASRS, and NAPA brings the operating requirements. The parties say the resulting system is tailored to diverse SKU profiles and intended to improve storage density, throughput, order accuracy, and fulfillment speed. Those are project goals and company assertions; the supplied material does not report post-implementation throughput, accuracy, or service results.
Sources: S2
Sources: S2
The shared dependency is usable operating time
The developments connect through a basic warehouse constraint: equipment creates value only while it can perform the required work within the surrounding operation. Agility’s argument is that rapid charging reduces time a Digit fleet spends unavailable for work. NAPA’s approach addresses a different source of unavailable capacity: a system that may not fit the site’s inventory mix, fulfillment logic, or operational process. One program emphasizes replenishing energy quickly; the other emphasizes reducing implementation uncertainty before the equipment reaches the operating site.
Reported fact: Agility characterizes uptime as the business case for Digit and says Nyobolt was selected for a smaller, lighter high-power battery system intended for industrial conditions. Reported fact: NAPA and its partners evaluated an ASRS design in a live warehouse before implementation. Neither supplied record establishes that a fast-charging humanoid has been validated in NAPA’s workflow, or that NAPA’s ASRS evaluation included humanoid robots. They are separate deployments with different equipment and operational purposes.
Charging infrastructure is part of the product
A 9-minute recharge promise shifts attention from the robot’s battery pack to the system around it. To turn the claimed run-to-charge ratio into productive time, an operator would need charging access when the robot needs it, charging capacity aligned with fleet activity, and work processes that can absorb a robot’s charging cycles. This is an inference from Agility’s stated dependence on fast charging for uptime, not a description of a disclosed Digit 5 installation. The supplied announcement does not specify charger placement, electrical infrastructure, queue management, battery-cycle results in customer use, or performance under a particular task mix.
Sources: S1
NAPA’s process offers a useful operational counterpoint. Its Innovation Lab evaluation occurred early in system design, allowing the partners to refine technology before deployment. That does not prove how a humanoid charging program should be designed. It does show the institutional capacity required to move from a vendor capability to an implementable operation: an operator must define requirements, an integrator must translate them into a system design, and the combined design must be exercised in conditions relevant to the site.
Sources: S2
What would count as delivered
For Digit 5, delivery would be more than the availability of early-access units. The consequential evidence would be operating data showing that the stated runtime and recharge behavior hold in a customer facility while the robot completes its intended work safely and reliably. It would also require evidence that the charging arrangement and fleet workflow preserve the productive-hour outcome Agility projects. This is an inference about the evidence needed to substantiate the announced business case; the supplied material reports planned availability and company expectations, not those customer outcomes.
Sources: S1
For NAPA, delivery would mean the proposed ASRS operating after implementation in a way that demonstrates the promised fit with its SKU profiles and fulfillment needs. Relevant evidence would include measured results for the goals the partners identify, such as throughput, order accuracy, storage density, and fulfillment performance, alongside evidence of how the system adapts as NAPA’s network evolves. The material supplied describes pre-deployment evaluation and planned benefits, rather than post-deployment results.
Sources: S2
Inference: readiness is an operating-system question
Inference: fast charging can make a humanoid more economically plausible by compressing a conspicuous source of downtime, but it cannot by itself establish readiness for warehouse deployment. NAPA’s validation model suggests that readiness is a property of the full operating system: the technology, integration design, inventory and task environment, and the organization’s ability to test and adjust them before go-live. Agility’s battery claim addresses an important component of that system; NAPA’s process illustrates the kind of validation discipline that can test whether the component’s theoretical availability becomes useful capacity.
The assessment would change with disclosed field evidence. For Digit 5, that includes customer-site data on runtime, recharge behavior, productive work, reliability, and the operational effect of charging. For NAPA, it includes implemented-system results against the project’s stated fulfillment objectives. Until then, the clearest comparison is not a contest between a humanoid and an ASRS. It is a reminder that announced component performance and validated deployment capability answer different decisions: whether equipment may be available often enough, and whether an operation is prepared to use it well.
Why it matters
Warehouse-automation buyers should separate availability claims from implementation evidence. Digit 5’s proposed charging performance could alter how much work a humanoid can perform between interruptions, while NAPA’s approach emphasizes that deployment also requires site-relevant validation, systems integration, and evidence that promised operational gains survive implementation.