Arbitrum has added two ways for software agents to pay for services and settle transactions without leaving an application flow. Its July 8 announcement says Coinbase's hosted x402 facilitator supports Arbitrum, while Offchain has published an open-source implementation of the Machine Payments Protocol, or MPP.
The pitch is simple: an agent that calls an API, buys data or executes a strategy needs a payment primitive as much as it needs a wallet. If the payment step requires a person to leave the application, the automation breaks at the point where it is supposed to create value.
Two payment patterns
x402 places a payment requirement inside the normal request-and-response pattern used by web services. A server can respond with a challenge, and a client can return payment credentials programmatically before receiving the data or service it requested. Coinbase's hosted facilitator handles operational pieces of the flow, so developers do not have to operate their own settlement infrastructure first.
MPP takes a more explicit client-server route. The open-source TypeScript package lets a server define a challenge, a client produce a signed authorization and the server validate, submit and confirm settlement. Arbitrum's implementation uses USDC transfers, with Permit2-compatible tokens available through a one-time approval.
Why Arbitrum wants the traffic
Arbitrum is positioning the support as more than an SDK integration. The network has low-cost execution, EVM compatibility, stablecoin liquidity and a deep DeFi base, all of which matter if agents move from one-off API payments to recurring financial actions.
That is also the competitive argument. Agent payments can be routed through many chains, so the network that wins will be the one that combines a reliable payment handshake with the liquidity, permissions and monitoring needed once agents handle larger balances.
The first evidence will be usage
Arbitrum calls x402 and MPP early steps and says the standards and dominant use cases are still forming. The announcement gives developers working paths, not proof of sustained transaction demand. The meaningful milestones will be live services, repeat agent payments, clear authorization boundaries and data showing that settlement costs remain sensible at high request volumes.
