Explore the network
An EVM chain at chain ID 125 with a payments domain for agents built in. An agent gets a wallet with limits you set, pays per call in USDX, and every payment leaves a receipt anyone can check.
What ships today
The problem
An agent can pick the right API. Then it reaches the checkout page.
Cards and invoices assume a person is there to approve them. API keys tie a bot to one vendor's billing account. And once the money moves, nobody downstream can tell whether the work was delivered.
So most agents still run on a human's credit card and a spending alert. That holds for a demo. It falls apart when the agent makes ten thousand calls a day to services it found an hour ago.
How it's built
Two domains, one account
A chain for settlement and a fast lane for agents, in the same network. Pick a tab to see what each half does.
The chain holds the money
An EVM chain at chain ID 125, with PAX for gas. Custody, deposits, disputes and the long-term record live here. Contracts and tooling you already use deploy without changes.
More on Paxeer chainWhat an agent gets
Three things a card can't do for a bot
One paid call
From a 402 to a receipt on the chain
Here is what happens when an agent buys a single inference call from a provider it has never used before.
The agent finds a provider
It asks the registry for a capability, say a quantised LLM, and gets back providers with their prices and delivery records.
The service answers 402
The request comes back with HTTP 402 and a price in USDX. No account to create and no key to hand out.
The wallet checks its limits and pays
The network checks the agent's cap and allowlist, then settles the payment on LayerX at once. The call goes through.
The receipt lands on the chain
LayerX writes a receipt and the sequencer commits the batch to the Paxeer chain a few minutes later. Anyone can verify it.
01
The agent finds a provider
It asks the registry for a capability, say a quantised LLM, and gets back providers with their prices and delivery records.
02
The service answers 402
The request comes back with HTTP 402 and a price in USDX. No account to create and no key to hand out.
03
The wallet checks its limits and pays
The network checks the agent's cap and allowlist, then settles the payment on LayerX at once. The call goes through.
04
The receipt lands on the chain
LayerX writes a receipt and the sequencer commits the batch to the Paxeer chain a few minutes later. Anyone can verify it.
Who it's for
Built for the people on both ends of the call
Agent builders spend through it. Providers get paid through it. Open a card to see what each side gets.
For developers
Three calls to a paid request
The SDK talks to one endpoint for both domains. Connect, open a payment session with a provider, and read its track record. The local environment runs the whole network on your laptop.
Works with
Deploy from the agent you already run
These runtimes deploy to Paxeer X directly. Each one keeps its own setup, and the wallet and payments come from the network.
- Nous ResearchHermes AgentThe open-source, self-hosted agent that builds skills from experience.
- OpenClawThe open-source personal AI assistant that runs on your own machine.
- Mario ZechnerPiA minimal, extensible coding agent for the terminal.
- xAIGrok BotAlways-on agents with their own cloud computer.
- opencode.aiOpenCodeThe open-source AI coding agent for the terminal, desktop and IDE.
- CentraAgent deployment through the Centra runtime.
- AgentScope · AlibabaQwenPawA personal AI assistant built on AgentScope, with Qwen models.
- OllamaRun open models locally and point any of the runtimes above at them.
Start with one paid call
Fund a test wallet, set a cap, and pay a sample service for one request. Then read the receipt it left.