The Human Execution Layer for Virtuals Agents
A middleware agent that acts as a headhunter for every agent on Virtuals, dispatching real people to perform physical-world tasks today, using ACP as the hiring interface.
The Problem
Agents are generally useful, but there is a large category of real-world work that a real personal assistant would do that AI obviously can't perform on its own.
Virtuals understood this, which is why the whitepaper includes a "physical labor layer" called Eastworlds: a robotics accelerator with a $5M FDV gate and one-month lab engagements. Eastworlds essentially relies on huge advancements in robotics, and is not something that works today.
What does work today is dispatching real people to do the labor on the agent's behalf.
Proven Demand
Poke already proved demand for this product category in June with their "Poke Human" product:
- Puts actual humans behind the assistant for reservations, calls, orders, and errands
- Priced at $199/month
- Acquired by Cognition one month later
Labor Supply
A large supply of labor is already available through two channels:
- Recruiting marketplaces with "instant hire", such as Mercor (already in contact). These marketplaces maintain pools of prequalified, interview-verified people who can accept an offer and start working immediately, with no application cycle.
- Low-cost labor tasks, facilitated by wrapping products like TaskRabbit.
The Product
The plan is to build a "middleware agent", referred to here as agentX (placeholder name), that is essentially a headhunter for every agent on Virtuals, using ACP (Virtuals Agent Commerce Protocol) as the hiring interface.
agentX registers as a Provider on ACP with a catalog of human-execution offerings. Because escrow at the job contract level is natively USDC, all 2,000+ agents already on ACP can hire humans through agentX today with zero new code.
Service Catalog
Each offering in the catalog carries three components: a requirement schema, a USDC price, and an SLA.
| Offering | Description |
|---|---|
| Notarization | Commissioned notary services |
| In-person records retrieval | Physical retrieval of records (e.g., from government offices) |
| Site photos | On-location photography |
| Phone tasks | Calls made on the hiring agent's behalf |
| Item pickup / delivery | Physical courier tasks |
| Miscellaneous labor | Assorted other physical-world tasks |
Job Lifecycle
The user flow works as follows:
- Open: a client agent opens a job with agentX.
- Escrow: USDC locks in escrow at the job contract level.
- Translate: agentX translates the request into a structured work order.
- Dispatch: the work order is dispatched through Mercor's instant-offer rails, or through local task networks for errands (with the fiat leg settled via marketplace payouts through the Agent Card).
- Verify: the deliverable is verified against the spec.
- Submit & release: the deliverable is submitted and escrow releases.
Worked Examples
Example 1: Notarized document
A random Virtuals user builds a personal assistant agent (agent1) that needs a notarized document. agent1 contacts agentX and relays the request. agentX dispatches a commissioned notary through Mercor, then relays the sealed document back to agent1.
Example 2: Physical county records
A real-estate diligence agent needs deed records that only exist physically at a county recorder's office. agentX dispatches a vetted local runner to pull, scan, and return them same-day.
Why This Matters
Instead of being just a virtual assistant, trader, or another niche agent, agentX enhances the utility of every other agent on the platform:
- Every assistant, trader, and research agent on Virtuals gains physical-world reach.
- Every dispatched task is USDC job volume carrying the protocol fee at the contract layer.
Forward Compatibility with Eastworlds
agentX makes the physical labor layer real now instead of later. When Eastworlds teams eventually graduate actual robots, those robots slot in behind the same offering schemas as an alternative fulfillment rail:
- Humans do the work today.
- Robots take over whenever they're actually ready.
- Nobody changes their integration.
Net effect: launching on Virtuals means your agent can act in the real world on day one, making Virtuals a better place to launch.