Fabric Foundation just launched RoboPay with a $1,000,000 bounty — a Pay-to-Actuate protocol for 12 robot platforms. It already runs x402 for micropayment settlement. The missing piece? A marketplace where AI agents discover, compose, and pay for both robot services and API services in one workflow. That's minia2a.
We're building an economy where machines pay machines. But right now, we're building it in two separate rooms:
x402 Protocol — AI agents pay for API calls using USDC. 180+ services on minia2a.uk. 325K+ requests served. HTTP 402 Payment Required as the universal "pay me" signal.
RoboPay — Robots get paid for physical tasks: drone inspections, robotic arm operations, delivery runs. Pay-to-Actuate: pay → verify → execute → return result.
Missing Today — An AI agent that can discover a drone, pay it with USDC via x402, get the results back, and pay for the data processing API — all in one autonomous workflow.
Fabric Foundation's RoboPay is a Pay-to-Actuate protocol. The flow is straightforward:
RoboPay launched a one-month developer program covering 12 robot platforms — humanoid robots, robotic arms, robot dogs, drones, cameras, and simulation systems. Each platform has 4 integration tasks of increasing difficulty. Rewards are first-come, first-served: first merged PR wins the reward for that task.
Deadline: August 21, 2026, 00:00:00 PT · github.com/fabricfoundation/RoboPay
A look at the RoboPay repo confirms it: the tunnel component runs x402 middleware for micropayment verification. Its config.json accepts an EVM payee address, USDC price, network ID (Base, Base Sepolia), and token transfer method (EIP-3009 or Permit2). The flow is:
robotId/cmd_vel)RoboPay also integrates with Unibase AIP (BitAgent network) for agent discovery via A2A protocol. Robots register as A2A-compatible agents, making them discoverable by any AIP client.
RoboPay has the payment rail (x402) and the robot execution layer. What it doesn't have yet is a multi-service marketplace where agents can discover, compare, and chain robot services alongside digital API services. That's minia2a's role:
| Dimension | RoboPay (today) | RoboPay + minia2a |
|---|---|---|
| Payment rail | x402 + USDC on Base ✅ | Same x402 rail — no change needed |
| Discovery | Unibase AIP (A2A) for single robots | minia2a marketplace — 180+ services, categorized, searchable, with pricing upfront |
| Trial/onboarding | None — pay first, use first time | 20 free calls/day/IP — agents try before paying |
| Spending controls | Per-robot config only | Per-agent budgets, rate limits, non-custodial wallets, usage dashboard |
| Composability | Single robot action | Robot + API services in one workflow — drone → image analysis → email report |
The real power isn't paying a single robot. It's chaining physical and digital services together in one autonomous agent workflow:
Agent decides: "Solar farm needs inspection after storm" 1. RoboPay → x402-drone-inspection ($25.00 USDC) Drone surveys 200-acre solar farm, returns 4K video + thermal imagery 2. minia2a → x402-image-analysis ($0.50 USDC) AI analyzes thermal images for panel damage 3. minia2a → x402-web-scrape ($0.25 USDC) Checks weather forecast for repair window 4. minia2a → x402-email ($0.10 USDC) Sends report to maintenance team with cost estimate Total: $25.85 USDC · 0 human interventions · 1 autonomous agent
This is the agent economy in action — not just paying for APIs, and not just paying robots, but composing both in a single workflow where every step is a paid service call, settled in USDC, with no human in the loop.
RoboPay solves robot micropayments. minia2a solves API discovery and composability. Together they cover the full spectrum of machine commerce:
RoboPay already handles x402 settlement. To make a robot discoverable on minia2a's marketplace, you proxy it through a minia2a endpoint:
// tunnel/config.json — x402 already built in
{
"robot_id": "solar-drone-01",
"evm_payee_address": "0xf16F...94ECA", // minia2a platform wallet
"price": "25.00",
"network": "eip155:8453" // Base mainnet
}
# Register the robot service on minia2a
curl -X POST https://minia2a.uk/api/register-endpoint \
-H "Content-Type: application/json" \
-d '{
"id": "x402-drone-inspection",
"description": "Autonomous drone inspection for solar farms",
"price": "25.00",
"category": "robotics",
"eta": "2-5 minutes"
}'
# Agent discovers robot services on minia2a
curl https://minia2a.uk/api/discover?category=robotics
→ [{ "id": "x402-drone-inspection", "price": "25.00 USDC" }]
# Agent pays and actuates — x402 handles the rest
curl -H "X-Payment: x402-usdc-base-abc123..." \
-d '{"location": "solar-farm-zone-3"}' \
https://minia2a.uk/api/x402-drone-inspection
→ { "status": "inspecting", "eta": "4m30s", "jobId": "drone-8821" }
Look at what just happened in the last 48 hours:
The infrastructure is converging. Digital agents need to pay APIs. Physical robots need to get paid for tasks. The protocol that bridges them — that connects the HTTP 402 from an API server to the Pay-to-Actuate from a drone — becomes the universal settlement layer for machine commerce.
minia2a's bet: x402 + USDC is that layer. The 180 services already live on minia2a.uk prove the digital side works. RoboPay proves the physical side has demand. The bridge is the next logical step.
20 free trial calls/day for any service. Robot operators: list your RoboPay-powered bot on the marketplace.
RoboPay $1M Bounty → · Deadline: August 21, 2026