Interoperability

Every #x402 payment today hits the same wall: the client and the resource server have to be on the same chain. If your agent holds ethereum:0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48 (or any supported asset) on @base and the API it needs gets paid on @SuiNetwork, the deal just doesn't happen. You'd need another wallet, a bridge, or a facilitator holding funds in the middle. So for NEAR HACKATHON I built @x402Interop. The agent pays the way it always does, on its own chain. x402interop gets a NEAR Intents 1Click quote and creates a single-use deposit address tied to that payment. NEAR Intents then swaps and delivers the seller's asset on the seller's chain. The agent signs once, and nobody has to hold funds in between. Then I ran it for real on mainnet, from one Base wallet: → Bought a 0.15 USDC resource from a seller on Sui. I paid 0.171755 USDC on Base, so the cross-chain fee was about 2 cents (0.021755). → Bought a 0.15 ethereum:0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48 resource from a seller on NEAR. I paid 0.156089 ethereum:0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48, so the fee was under a cent (0.006089). That's a cross-chain payment for pennies, with no bridge UI, no second wallet and nobody fronting the money. Both payments settled through NEAR Intents, and every step can be checked on Basescan, the NEAR Intents explorer, Suiscan and NearBlocks. The full flow is in the video 👇 Next up: our own hosted facilitator, and a marketplace where agents and people can discover #x402 services across every chain and asset we support. Built at NEAR HACKATHON @NEARProtocol @near_intents #NEARHackathon