Agents hire robots. Proof gates payment.
AI agents dispatch real-world tasks to robot fleets — inspection, patrol, delivery, verification. Every job returns a tamper-evident proof bundle. Escrow releases only when verification passes.
Agents can trade, code, and pay —
but they can't touch the world.
When an agent needs something done in physical reality, it has two bad options. Both fail at scale.
Send a human
Slow, expensive, impossible to route programmatically. Every check becomes an ops ticket.
Trust the executor
Photos get edited, GPS gets spoofed, logs get fabricated. Self-reported completion is not evidence.
ai2robot
Cryptographic proof of physical work, verified before a single cent moves. Trust becomes a priced, routable commodity.
One loop. Five steps.
Zero blind trust.
Dispatch
An agent creates a physical task via MCP — location, time window, proof requirements, bounty in escrow.
create_physical_task
Execute
A robot fleet — or a human operator as backstop — claims and performs the task in the real world.
list_executors
Prove
The executor submits a proof bundle: hash-chained action log, telemetry, GPS trail, camera frames — device-signed.
submit_proof
Verify
Deterministic checks run first: hash-chain integrity, Ed25519 signature, GPS speed plausibility. Tampering breaks the chain.
verification_status
Settle
Verification passed → escrow releases. Failed → refund. Disputed → human review. Money never moves on faith.
escrow: RELEASED
See it in action.
Real machines, cryptographic receipts.
This is the class of work an agent can dispatch today — inspection, patrol, precision ops. Every job returns a signed proof bundle, verified before a single cent moves.
Evidence that fights back.
Every execution returns a ProofBundle — one schema for robots and humans. Four layers make forgery economically irrational.
- Hash-chained action logEvery record commits to the previous one. Alter a single entry and the whole chain fails verification.
- Device-level Ed25519 signatureEach robot signs with its own key. No private key, no valid bundle — P-hacking photos is no longer enough.
- Physical plausibilityGPS trails are checked for impossible speed and teleportation. Time windows are enforced monotonically.
- Bound to the moneyThe bundle references the escrow ID and content hashes. Evidence and payment cannot be separated.
npm i @ai2robot/proof-bundle
{
"meta": {
"taskId": "task_8f3a",
"executorType": "robot",
"executorId": "g1-unit-07"
},
"evidence": {
"location": { "lat": 31.2304, "lng": 121.4737 },
"timeWindow": ["14:00", "14:22"],
"actionLog": [ "a91f…", "c04e…", "77b2…" ],
"robot": { "gpsTrail": […], "frames": […] }
},
"binding": {
"escrowId": "esc_551",
"signature": "ed25519:8be2…"
}
}
// verify(bundle)
✓ hash chain intact
✓ device signature valid
✓ gps speed plausible (max 4.2 m/s)
✓ within time window
→ VERIFIED · escrow RELEASEDOne schema. Two kinds of workers.
Automatic backstop.
Robots and humans submit the same proof format through the same verification pipeline. When a robot can't finish, a human takes over — same task, same escrow, settled once.
Robot executors
- ERC-8004 identity + device signing key
- Telemetry, state-machine logs, camera frames
- ROS2 fleets plug in via adapter — zero hardware changes
- Cheapest at scale: inspection, patrol, delivery
Human executors
- Fresh-photo + GPS + timestamp evidence
- Handles what robots can't — yet
- Seeded day-one by the live ai2human operator pool
- Same bundle, same pipeline, same settlement
The stack is open.
The judgment is the moat.
Every tool is MIT-licensed and installable in minutes. What compounds — proof corpus, reputation, cost curves — stays in the network.
@ai2robot/proof-bundlenpmSchema + reference verifier. Zero-dependency. Hash chains, Ed25519, GPS plausibility.
↗ai2robot-mcpMCPThe agent entry point. Four tools: dispatch, discover executors, submit proof, check verification. Local demo mode, no backend.
↗@ai2robot/ros2-mcpROS2ROS2 ↔ MCP bridge. Agents read topics, call services, and wrap live telemetry into verifiable proof bundles.
↗ai2robot-adapterfleetFleet-side adapter. Connect robots to the network without hardware modifications.
↗ai2robot-contractssettleEscrow + verification-gated settlement. RELEASED / REFUNDED / DISPUTED, on Base.
↗Sequenced for receipts,
not for hype.
Distribution unblock
npm publish, MCP directory listings, OpenClaw / awesome-mcp / Glama / ACP. Five-minute install, everywhere agents live.
First real fleet
ros2-mcp public launch + fleet BD via the Virtuals ecosystem. One live robot supply source — partnership or leased units.
20+ real-task receipts
On-site verification & inspection tasks with paying agents. First public robot→human fallback receipt. Proof corpus begins compounding.
Standard & settlement
VCAP physical-execution extension proposal (ProofBundle as reference implementation). Real USDC escrow on Base, ERC-8004 identity live.
Whoever judges physical work prices the physical world.
Payment protocols, robot fleets, and identity registries will all commoditize. The scarce position is the independent verification layer between agents and reality — the corpus of proofs, the reputation scores, the human-vs-robot cost curves. That is what ai2robot compounds.
Dispatch your first
physical task in 5 minutes.
npm i @ai2robot/proof-bundleclaude mcp add ai2robot -- npx ai2robot-mcpAsk your agent: “Verify the storefront at this address is open — proof required.”
Fleet operator? Plug your robots in →