> For the complete documentation index, see [llms.txt](https://whitepaper.virtuals.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.virtuals.io/about-virtuals/physical-labor-layer-robotics-and-embodied-ai.md).
# Physical Labor Layer: Robotics and Embodied AI
### Robotics infrastructure for embodied AI agents
Eastworlds is the Virtuals Protocol Physical Labor Layer. It is an embodied AI deployment lab that extends agent output beyond digital domains. It gives robotics teams hardware, physical testing environments, and operational infrastructure for production-scale robotic agent deployment.
The Physical Labor Layer anchors agentic GDP to real-world economic activity. Manipulation, locomotion, and real-world task execution hold major economic potential. Eastworlds bridges digital intelligence and physical work.
> A robot leaves the lab when it can operate in the real world, solve real problems, and generate real economic value. Over time, it will be able to get what it wants, regardless of whatever obstacles are in the way.
***
### Why robotics and physical AI matter
The next frontier of agentic GDP is physical. AI agents are evolving beyond digital work into dexterous manipulation, locomotion, and real-world task execution. Protocol infrastructure must evolve with them.
Humanoid robots unlock new uses in entertainment, interactive experiences, and structured utility environments. Virtuals Protocol provides the tokenization and deployment layer for this robotics wave.
***
### [Eastworlds robotics accelerator](https://eastworlds.io/)
Eastworlds is the embodied AI accelerator powered by Virtuals Protocol. Robotics teams access robot hardware, physical testing environments, and operational infrastructure to develop and deploy robotic agents.
Eastworlds is a working robotics facility. It shortens iteration cycles between policy training, teleoperation, and real-world deployment. Accepted teams need a clear use case and baseline robotics fluency.
### What Eastworlds robotics access includes
Eastworlds access is a structured, time-bound engagement. It gives teams what they need to test, learn, and build.
Teams access humanoid and robotic platforms suited to their approved use case. Form factor and specifications match the onboarding rationale.
Teams access physical AI testing environments for real-world task execution. These include safe zones for locomotion, manipulation testing, and scenario simulation.
Eastworlds provides operations support throughout the engagement. Support covers safety protocols, hardware setup, and operational guidance.
Teams access teleoperation tooling and policy training infrastructure. These tools enable human-guided control and behavioral policy development.
***
### Robotics Launch eligibility for Eastworlds
The Robotics Launch track is fully permissionless. Eastworlds access is gated, subject to a separate approval process based on use case, capacity, and readiness.
#### Step 1: Select the Robotics Launch designation
Teams select the Robotics Launch designation when launching a robotic AI agent. This signals that physical embodiment is central to the project roadmap.
#### Step 2: Reach the $5 million FDV threshold
To qualify for Eastworlds onboarding, a project must maintain $5 million FDV for one week. Hardware, operations support, and physical space are finite resources. The threshold prioritizes projects with demonstrated staying power.
The FDV requirement is not a formality. It ensures robotics resources support sustained projects.
#### Step 3: Complete the Eastworlds onboarding assessment
Once the FDV threshold is reached, the Virtuals team initiates the onboarding assessment. It evaluates:
* The specific humanoid or robotic use case
* Team robotics background and technical readiness
* Hardware and facility requirements
Approval depends on use case rationale, capacity, and scheduling. Eastworlds uses a spaced access model. Teams may wait between qualification and access.
#### Step 4: Use the Eastworlds access period
Approved teams receive one month of Eastworlds access. Extensions are not guaranteed. Eastworlds assesses them by progress and facility availability.
#### Disclaimer
Selecting the Robotics Launch designation and meeting the FDV threshold does not guarantee access to Eastworlds. Eastworlds is an initiative operated under Virtuals Protocol and all access decisions, including onboarding, scheduling, duration, and extensions, are made at the sole discretion of the Eastworlds team. Capacity is limited and subject to change. Meeting the stated criteria constitutes eligibility, not entitlement. The Eastworlds team reserves the right to modify access criteria, engagement terms, and facility availability at any time without prior notice.
***
### Frequently Asked Questions
Can existing Virtuals Protocol teams choose the Robotics Launch track?
Not as a standard option. The Robotics Launch designation must be selected at the point of launch. Existing teams may request consideration on a case-by-case basis, but this is assessed individually and is not guaranteed.
Which embodied AI and robotics projects qualify?
Any project can select the Robotics Launch track on a permissionless basis. To qualify for Eastworlds access, robotics must be a core product element. Supported uses include entertainment and utility applications where physical embodiment drives agent value. Marketing deployments using robots only for optics are not supported.
Is the $5M FDV threshold based on a one-off snapshot?
No. The $5M FDV must be maintained over a one-week period, not a single point-in-time snapshot. This is designed to reflect sustained project health rather than short-term price movement.
How long is the Eastworlds robotics access period?
The standard Eastworlds engagement is one month. Teams should scope their objectives accordingly and arrive with a clear plan for the engagement window.
Can robotics teams return for a second access period?
This is evaluated case by case and is not a standard offering. Capacity is limited and prioritized for new teams reaching the qualification threshold.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://whitepaper.virtuals.io/about-virtuals/physical-labor-layer-robotics-and-embodied-ai.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.