Ecosystem

Plug in what you already run

Paxeer X speaks the payment and agent protocols your software already uses, bridges to nine chains, and works with the wallets, runtimes and tools builders reach for first.

Nothing here asks you to learn a new protocol. Each adapter turns a request your stack already makes into a payment the user signed and a receipt anyone can check.

Six protocols, one network

A seller charging per request, a checkout waiting on a payment, an assistant that needs a wallet. Each arrives through a protocol it already knows and leaves with a signed receipt.

Bring funds from nine chains

Lock PAX on any of these chains and it is released on Paxeer X once independent attestors agree; send it back the same way. SID moves between Paxeer X and Solana, its other home.

Treasury on Ethereum, agents on Paxeer X: a transfer in, a month of per-request payments, a transfer out, each step with its own receipt.

How the bridge works
  • EthereumPAX
  • BasePAX
  • ArbitrumPAX
  • OptimismPAX
  • BNB ChainPAX
  • PolygonPAX
  • AvalanchePAX
  • HyperEVMPAX
  • SolanaPAX and SID

Works with the runtimes you build agents in

Install the MCP server and any of these can hold PAX, pay for a tool and hand you the receipt, within the limits you set.

Around the chain

Where to hold PAX, where to look things up, and where to check that everything is running.

Read further

Bring your protocol, runtime or service

If you run a payment protocol, an agent runtime or a service agents should pay for, tell us what you need from the network and we will help you plug in.