# Agent Robotics > 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. The next frontier of agentic GDP is physical. As AI agents mature from purely digital actors into systems capable of dexterous manipulation, locomotion, and real-world task execution, the protocol layer must evolve alongside them. Virtuals Protocol is building the tokenization and deployment layer for this wave through Eastworlds, its embodied AI accelerator initiative. *** ### Why Robotics, Why Now The next frontier of agentic GDP is physical. As AI agents mature from purely digital actors into systems capable of dexterous manipulation, locomotion, and real-world task execution, the protocol layer must evolve alongside them. Humanoid and robotic form factors unlock an entirely new class of use cases, from entertainment and interactive experiences to utility applications in structured environments. The window to build foundational robotic agents is now. Virtuals Protocol is building the tokenization and deployment layer for this wave. *** ### [Eastworlds](https://eastworlds.io/) Eastworlds is the embodied AI accelerator powered by Virtuals Protocol. It is a purpose-built environment where robotics teams gain access to real robot hardware, physical testing environments, and the operational infrastructure needed to develop and deploy robotic agents. Eastworlds is not a showcase. It is a working facility designed to compress the iteration cycle between policy training, teleoperation, and real-world deployment. Teams accepted into Eastworlds should arrive with a clear use case and a baseline level of robotics fluency. The facility exists to accelerate, not to introduce. ### What [Eastworlds](https://eastworlds.io/) Access Includes Eastworlds access is a structured, time-bound engagement designed to give teams the minimum viable surface they need to test, learn, and build. Hardware access to humanoid and robotic platforms suited to the team's approved use case. Form factor and specifications are matched to the use case rationale submitted during onboarding. Physical space with dedicated testing environments configured for real-world task execution, including safe zones for locomotion, manipulation testing, and scenario simulation. Operations support from the Eastworlds team throughout the engagement period, covering safety protocols, hardware setup, and operational guidance. Software access to teleoperation tooling and policy training infrastructure to enable human-guided control and develop behavioral policies.
*** ### Robotics Launch - How Teams Qualify The Robotics Launch track is fully permissionless. Eastworlds access is gated, subject to a separate approval process based on use case, capacity, and readiness. ![](https://4242579099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Frrll8DWDA3BJwEBqOtxm%2Fuploads%2FxaPiLJftAU8Dtt14kdM2%2Funknown.png?alt=media\&token=cd6ef2d3-06be-45a6-ba47-7dfe6f3a405a) #### Step 1: Robotics Launch Designation Teams indicate their intent to build a robotic agent at the point of launch by selecting the Robotics Launch designation. This signals to the protocol and the Eastworlds team that physical embodiment is a core part of the project roadmap. #### Step 2: FDV Threshold To be eligible for Eastworlds onboarding, a project must reach and maintain $5M FDV over a one-week period. Hardware access, operations support, and physical space are finite resources. The threshold ensures they are allocated to projects with demonstrated staying power, not a single point-in-time snapshot. The FDV requirement is not a formality. Hardware access, operations support, and physical space are finite resources. The threshold ensures they are allocated to projects with demonstrated staying power. #### Step 3: Virtuals Team Outreach Once the FDV threshold is reached, the Virtuals team will initiate contact to begin the onboarding assessment. This includes evaluating: * The specific humanoid or robotic use case * Team robotics background and technical readiness * Hardware and facility requirements Approval is based on use case rationale, available capacity, and scheduling. Teams should expect a delay between qualification and access commencement, Eastworlds operates on a spaced access model to ensure each team receives adequate support and facility time. #### Step 4: Access Period Approved teams receive one month of Eastworlds access. This is the standard engagement window. Extensions are not guaranteed and will be assessed case by case based on 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 teams on the protocol 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.
What types of projects qualify? Any project can select the Robotics Launch track on a permissionless basis. However, to qualify for Eastworlds acccess, projects must have a robot form factor as a core product element, not as an accessory. Supported use cases are entertainment and utility applications where physical embodiment drives the agent's value. Marketing-oriented deployments that use robots for optics rather than capability will not be 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 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 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.