Hacki
About the project
Robotics-as-a-service is sold like enterprise software in 2005: an annual contract, a minimum fleet size, an invoice at the end of the quarter. That prices out the warehouse needing four hours of picking in November, and gives the fleet owner no way to sell idle capacity.
CanAgile bills a robot the moment it moves. A task is a paid HTTP resource. The buyer asks for picking, receives a real 402 Payment Required, signs a stablecoin authorisation, and only then does the arm move. Picking a 2 kg box costs $0.0007 an amount no card network could settle profitably.
Two properties make it more than a checkout:
Payment buys an unlock, not a promise. Each payment covers exactly one task, and the authorisation's nonce is burned on use so it cannot buy a second. Work is proven, not asserted. Each robot is a BIP-44 account derived from the operator's seed and signs its own EIP-712 TaskCompleted. The marketplace holds no robot key, so it cannot fabricate a completion. How it works Three genuinely separate parties, three separate seeds, none trusting the others:
Warehouse (buyer) — holds USD₮0, signs EIP-3009 authorisations, never broadcasts a transaction, holds zero ETH. Fleet operator (seller) — issues the 402s, prices labour by phase and weight band, receives every payment, commands the robots. Facilitator — verifies and settles in-process on a WDK wallet, and pays the gas. One order becomes three machine-to-machine payments picking, packing, delivery each to a different robot, none approved by a person. A robot only moves after its own payment clears, and the next is not commanded until the previous reports finished.
The physical layer is a Webots warehouse fleet driven through a Flask connectivity layer.