Prompt an agent. Hardware settles and moves.
0xBS is the machine-payable control plane for physical AI. Claude, ChatGPT, and any x402 client discover MCU-class devices, settle USDC, and invoke motors, sensors, robotics, and UAV payloads — globally, per call.
Quickstart
Discover a device contract and settle a call.
Claude & ChatGPT
Prompt an agent. Hardware executes.
Firmware SDK
wrap() — MCU-class silicon as a merchant.
What 0xBS is
An operator flashes an ESP32 (or any MQTT device) and wraps existing functions — drive forward, read a probe, arm a payload. Each function becomes a service with a USDC quote. AI agents fetch the public contract and call it over x402. Paid services challenge with HTTP 402; settlement clears to the operator wallet on Base or Solana; then the MCU fulfills. The agent never sees MQTT. The silicon never holds a wallet.
Why it exists
- Physical AI needs a payment rail. Inference already has APIs. Motors, sensors, and UAVs did not. 0xBS is that rail.
- MCU-class merchants. Commodity ~$3 ESP32 boards become globally addressable endpoints. No acquiring bank, no on-device signer, no firmware rewrite of the payment plane.
- Telemetry as inventory. Sensor readings are metered primitives. Agents purchase a sample from any jurisdiction the public internet reaches; operators capture micropayment yield per poll.
- Standard, not proprietary.
x402-fetch, AgentKit, MCP — the same adapters used for software APIs.
The loop
- Prompt: “Move the car forward two seconds” or “Purchase greenhouse #4 soil moisture.”
- The agent loads
GET /public/device/{deviceId}and reads argument schemas, price, and payout rail. - It POSTs to
/quote/device/{deviceId}/service/{serviceId}. Free → result. Paid →402; the x402 adapter settles USDC and retries. - The control plane relays over private MQTT. The wrapped function runs. The agent receives the result plus a settlement receipt.
Where to start
API base in examples: https://device-controller.0xbs.org