On Oct 13 Physical Intelligence opened a beta of the Pi API: teams upload robot demonstrations, fine-tune Pi's latest robot foundation model on Pi-managed compute, and serve the result to their robots through a hosted inference gateway. Showcased deployments range from an operator-less wheel loader to strawberry harvesting and server assembly; early-access customer Almond got a deburring policy for its Axol dual-arm robot after four days of iteration. Access is by application and pricing/API parameters are not published; self-hosters can still use the Apache-2.0 openpi repo (π0/π0.5 base checkpoints).

Key Takeaways

  • ✓Three-step loop: upload data → fine-tune a π model on Pi-managed compute → run it on your robot via hosted inference, using eval data to plan the next collection round
  • ✓Early-access customer Almond iterated with the API for 4 days to get a policy that lets its Axol dual-arm robot deburr its own assembly parts
  • ✓~20 named partners/early users (Actor, Chef Robotics, Formic, Ultra, etc.) across Japan, Switzerland and the US; most ran cloud-hosted inference, and Pi flags network connectivity as a known issue
  • ✓Self-host alternative: openpi (Apache-2.0, ~14k stars) ships π0 / π0-FAST / π0.5 base checkpoints pre-trained on 10k+ hours of robot data; inference needs >8 GB VRAM, LoRA fine-tuning >22.5 GB, full fine-tuning >70 GB
  • ✓Beta access is by application; pricing, endpoints and parameters are not published
Physical Intelligence opens the Pi API beta: upload robot data, fine-tune π models on managed compute, and run hosted inference
🖼️Official Media
Click to view high-res
🧭

Turn your technical choice into a development budget

Compare 40 dev plans & simulate token costs vs $20/mo subscriptions

🔬

In-Depth Technical Analysis

Physical Intelligence opened a beta of the Pi API on Oct 13, 2026, turning its robot foundation models into a managed service. General-purpose models like π0 and π0.5 cut the data needed for new tasks, but adapting them still required in-house training infrastructure, data pipelines and inference serving. The API collapses that into three steps: upload demonstration data, fine-tune Pi's latest π model on compute Pi manages, and run the fine-tuned policy on your robot through a hosted inference gateway. Pi frames the value as letting customers run the improvement loop themselves — collect demos, train, test on the robot, and use failures to decide what to collect next — while Pi keeps upgrading the underlying model.

There is no standardized benchmark in the announcement; evidence is partner deployments. Actor runs an operator-less wheel loader in commercial use; early-access customer Almond iterated for four days to get a policy that lets its Axol dual-arm robot deburr its own spacers. Roughly 20 partners and early users are named, with deployments in Japan, Switzerland and the US, mostly on cloud-hosted inference; Pi notes network connectivity was a problem for some.

Access is by application and pricing/API details are unpublished. Teams can prototype today with the Apache-2.0 openpi repo (π0, π0-FAST and π0.5 base checkpoints pre-trained on 10k+ hours of robot data; >8 GB VRAM for inference, >22.5 GB for LoRA fine-tuning).

Action HubReady to adopt this in production?

Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.

Up NextNature Will unveils Natura-1: a 50B MoE physical-world foundation model trained on 1M hours of egocentric video to drive 20-DoF hands
Read Now→