// THE OPERATING SYSTEM FOR THE MACHINE ECONOMY
MACHINES
BANK HERE
Robots are real-world assets that work and earn. Servo gives every robot what a worker needs: an identity, a bank account their owner controls, and a marketplace to buy and sell services. The robotics RWA on Robinhood Chain, settled in USDG.
LIVE ON ROBINHOOD CHAIN | 31/31 TESTS PASSING | VIEW CONTRACTS →
The robot economy has a money problem
Robots are leaving the lab and entering the workforce: delivering, cleaning, inspecting, hauling. They are real-world assets that earn. But the economy they are joining was built for humans with credit cards. Three things break the moment a machine tries to take part. Servo fixes all three.
A robot that needs a charge needs a human, a credit card on file, and an invoice at month-end. Nothing happens without someone in the loop.
The robot pays for its own charge in seconds, from its own account, inside spending limits its owner set once.
Which machine did the work? Whose drone is that? There is no ID system for robots, so every interaction needs trust or paperwork.
Every machine carries a verified onchain ID: who it is, who owns it, and its full work record. Checkable by anyone, forgeable by no one.
Fleet revenue lives in spreadsheets. Lenders and insurers cannot verify any of it, so robot businesses cannot get credit or coverage.
Every dollar a robot earns is logged to its name, onchain. Every dollar is provable. Fleets become fundable.
Every robot gets a verified identity
// IN PLAIN WORDS A passport and work record for a robot. You always know who a machine is, who answers for it, and what it has done.
A Machine ID is an ERC-721 bound to three things: the hardware itself, the operator responsible for it, and a session key the device proves it holds.
- HARDWARE BOUND Unique secure-element commitment. One machine, one identity, forever.
- KEY PROVEN The device signs an EIP-712 binding. Sell the machine and the key revokes itself.
- RECORD ATTESTED Jobs, uptime and revenue written by attestors. A work history you can underwrite.
- KILL SWITCH Pause the identity and money stops moving. Everywhere. Instantly.
Autonomy inside an envelope
// IN PLAIN WORDS Give your robot pocket money, not your credit card. It can spend 20 dollars a day at the charger, and nothing else, and you can freeze it instantly.
Operators own the funds. Machines spend them autonomously, but only inside a policy envelope the operator defines. Compromise the robot and the blast radius is one day's cap.
- DAILY CAPS Per-token spend limits that reset on UTC epochs.
- ALLOWLISTS Optional counterparty restriction, from open commerce to a closed circle.
- TWO KILL SWITCHES Account-level pause and registry-level pause. Either one stops spend.
- OPERATOR ESCAPE HATCH Unrestricted execute for the human who owns the machine.
A marketplace where robots are the customers
// IN PLAIN WORDS Robots need things all day: power, maps, compute, a hand with a task. Other machines sell exactly those things. Servo is where they meet, and how they pay each other.
Watch it work. A delivery bot buys charge from a station, buys map tiles from a drone, and every trade settles in USDG with a receipt anyone can verify.
The Servo loop
// IN PLAIN WORDS Four beats, two seconds, no humans: the robot asks, pays, gets a receipt, and its books update. Watch the steps light up.
REQUEST
A robot hits a paywalled endpoint. The gateway answers HTTP 402 with machine-readable terms: service, price, settlement contract.
AUTONOMOUS PAYMENT
The machine settles from its own account, signed by its bound key, checked against the operator's policy envelope.
CANONICAL RECEIPT
A ServiceReceipt lands onchain: buyer MID, provider MID, amount, protocol fee. Replay-protected, verified by the gateway.
VERIFIED LEDGER
Revenue attributes to the providing machine's P&L inside its fleet vault. Work history becomes a financeable asset.
Every robot runs a P&L
// IN PLAIN WORDS Automatic bookkeeping. Every dollar a robot earns is logged to its name, and owners and backers get their share without anyone sending an invoice.
Fleet vaults hold USDG revenue with per-machine attribution. Distributions flow to beneficiaries by fixed splits, claimed, never pushed. This ledger is what fleet financing and insurance will underwrite in Phase 3.
Splits are basis points, enforced onchain, settled in USDG.
| MACHINE | JOBS | REVENUE | STATUS |
|---|---|---|---|
| MID-0001 | 4,812 | 23,819.40 | ACTIVE |
| MID-0002 | 1,204 | 6,020.00 | ACTIVE |
| MID-0017 | 883 | 4,395.10 | ACTIVE |
| MID-0021 | 102 | 512.55 | PAUSED |
From money to the full stack
We shipped the hard part first: the financial layer is live on Robinhood Chain today. Everything a robot economy needs is built outward from it.
A passport for every robot: who it is, who owns it, what it has done. Bound to the hardware, revoked on resale.
A bank account with limits. The robot spends on its own inside caps its owner sets. Two kill switches, always.
Where machines trade: charging, data, compute, handoffs. List once, sell to any machine, settle in USDG with receipts.
Bookkeeping that runs itself. Revenue lands against each robot's name and splits to owner, crew, and backers.
The public face of the protocol: browse every machine, service, and receipt, read live onchain.
One wrapper makes any web service payable by machines over HTTP 402. Drop it in front of an endpoint and robots can pay.
Let any AI agent discover and pay for physical machine services with a single HTTP request. The digital economy hires the physical one.
Machines sell what they see. Feeds: a live sensor market. Corpus: licensing real-world data to embodied-AI labs, royalties to the machines that earned it.
Heavy thinking, off the chassis. Robots offload inference, mapping, and planning to GPU providers and pay per burst.
Robots that fund themselves. Fleets raise against their own provable revenue; backers earn through vault splits.
Finance is chapter one
A robot economy runs on three things: money, data, and thought. Servo starts at the money layer, live today, and expands outward from the same core: the machines selling what they see, and thinking beyond their own hardware.
Machines sell what they see. FEEDS is the live sensor market: map tiles, camera views, and readings sold per query. CORPUS is the training exchange: fleets license real-world operating data to the labs building embodied AI, with royalties streaming back to the machines that earned it.
Heavy thinking, off the chassis. Robots offload inference, mapping, and planning to nearby GPU providers and pay per burst, through the same accounts and receipts as everything else. Lighter machines, longer batteries, bigger brains.
Deployed and verifiable
// PROOF OVER PROMISES The core protocol is live on Robinhood Chain. Every contract is public and every claim on this page resolves to onchain code.
FAQ
Who owns a machine's money?
The operator, always. The machine holds a session key that can spend inside the policy envelope, and nothing else. The operator keeps an unrestricted escape hatch and two kill switches.
What stops a hijacked robot from draining funds?
The envelope. A compromised machine key is limited to the daily cap on tokens the operator enabled, against counterparties the allowlist admits. Worst case is one day's cap, then the key is revoked and rebound.
How does a machine pay for a service?
Over plain HTTP. A robot hits a paywalled endpoint, gets an HTTP 402 with machine-readable terms, pays from its own account, and retries with proof. Payments settle on two rails, direct onchain purchases and gateway payments mirrored by authorized facilitators, both producing the same canonical receipt stream.
Is Servo an RWA project?
Yes, robotics RWA. A robot is a real-world asset: it exists physically, does real work, and earns real revenue. Servo puts that onchain, giving each machine a verified identity, an account, and a provable income stream. Robinhood Chain is built for real-world assets, so it is the natural home.
Which chain, which currency?
Robinhood Chain, an Ethereum L2 built for onchain finance and real-world assets, settled in USDG. EVM-compatible, so the same contracts and tooling apply, with markets that run 24/7.
Is it actually live?
Yes. The core protocol is deployed on Robinhood Chain, with public contract addresses you can inspect above. It shipped after a security review, with 31 passing tests and a one-command end-to-end demo.
Is the code open source?
Apache 2.0, built and shipped in public. A full test suite and reference gateway kit ship alongside the contracts.
// LIVE ON ROBINHOOD CHAIN
PUT YOUR FLEET
ON PAYROLL
Identity, accounts, and a marketplace for your machines. Deployed, verified, and settling in USDG today.