Build machine payments with Arcon

Arcon is payment infrastructure for autonomous machines. It connects three parts of a machine purchase without collapsing their trust boundaries:

1. A service describes an exact price with an HTTP 402 Payment Required response.
2. The machine evaluates those terms against its local payment policy and signs a single authorization.
3. An x402 facilitator verifies and settles the USDC payment before the service is fulfilled.

Start with Robot Pay

@arcon-network/robot-pay is the TypeScript SDK for the payer side of this flow. It is designed for robots, vehicles, edge agents, and other machines that must operate inside explicit recipient, asset, purpose, and budget limits.

bun add @arcon-network/robot-pay @x402/core @x402/evm

Continue with the quickstart to make a policy-bound paid request, or read the Robot Pay guide for its safety model and complete API surface.

Choose a path

• I am building a machine client: start with Robot Pay.
• I am operating a paid service: use an x402-compatible server and facilitator, then return fulfillment only after settlement succeeds.
• I am connecting physical hardware: keep settlement and actuator permission separate and enforce independent device-safety controls.

What Robot Pay enforces

• Deny-by-default allowlists for origins, purposes, recipients, networks, and assets.
• Per-payment and rolling-window spending limits in atomic token units.
• Idempotency protection so a completed or uncertain payment is not repeated.
• Resource URL matching and manual redirect handling to prevent authorization forwarding.
• An optional approval callback for operator or fleet-control authorization.

Payment proves that commercial terms were accepted. It does not authorize motion, docking, charging, or any other physical action.