Wallets with limits
Give an agent a budget, a list of services it may pay and a key that expires on Friday. The network refuses anything outside those rules.
How wallets workMoney for softwarethat works on its own.
Paxeer X is an EVM network where agents and apps hold a wallet with limits you set, pay per request, and get a signed receipt for every payment.
- PAX price
- $10.43
- Gas price
- 0.88gwei
- Latest block
- 41,780,243
- Block time
- 434ms
- Transactions today
- 329,454
Software already does the work. Paxeer X gives it a way to pay for that work: a wallet the network holds to your rules, payment that travels inside the request, and a receipt anyone can check without asking you.
Pay per request
A service answers HTTP 402 with a price. The agent pays inside the same request and gets the answer back, with no account and no invoice.
Read about LayerXA receipt for every move
Every payment returns a receipt that names who paid whom, how much and under which rule. Anyone can verify it offline.
See how it settlesOne network, six parts.
Agents, the agent web, tool connections, paid requests, compute and chains of your own, settled on the same ledger.
One request, end to end.
A research agent asks a market-data API for today’s EUR/USD fix. This is the whole exchange.
- 01
The agent asks
An ordinary HTTPS request. Nothing about it is crypto-specific.
- 02
The service names a price
HTTP 402 carries the amount, the asset and where to pay. Agents built for x402 read it without custom code.
- 03
The wallet checks the rules
Inside the daily cap, on the allowlist, key still valid. The network signs off and the payment goes out with the retry.
- 04
The answer comes back with proof
The service releases the data as soon as the receipt checks out. The agent keeps the receipt.
research-agentHTTPS · chain 125
GET /v1/fx/eurusd/fix HTTP/1.1
Host: data.example.com
HTTP/1.1 402 Payment Required
price: 0.40 PAX network: paxeer:125
policy research-agent cap 40.00 / day used 24.80 ok
GET /v1/fx/eurusd/fix X-Payment: 0x8f3a…c21e
HTTP/1.1 200 OK { "pair": "EURUSD", "fix": 1.0842 }
receipt 0x41c9…7b02 0.40 PAX signed final
- Payer
- research-agent
- Payee
- data.example.com
- Amount
- 0.40 PAX
- Block
- #41,780,243
research-agentSession keyExpires Fri 18:00
Budget, today24.80 / 40.00 PAX
0Cap
Allowed services
- data.example.com
- search.paxeer.network
- gpu.example.ai
Held for your approval
Pay 42.00 PAX to a new service
Not on the allowlist
You set the limits. The network keeps them.
Rules live on the chain, not in a policy document. An agent cannot spend past them, even with a bug or a bad prompt.
- Period caps
- A budget per day, week or month. The payment that would cross it is refused.
- Allowlists
- Name the services an agent may pay. Everything else is held for you.
- Session keys
- Keys that can only do less than the owner, and expire on a date you pick.
- Approval holds
- Anything outside the rules waits until you approve it with your passkey.
Running now.
Paxeer X is running in mainnet beta. These numbers come straight from Paxscan, the network’s block explorer, and update while you read.
- Transactions, all time
- 3,989,767
- Addresses
- 36,172
- Transactions today
- 329,454
- Block time
- 434ms
Latest blocksPaxscan ↗
- 41,780,243Paxeer EU-East Berlin V31s ago
- 41,780,242Paxeer UK-East London V12s ago
- 41,780,241Paxeer UK-East London V12s ago
- 41,780,240Paxeer EU-East Berlin V32s ago
If it runs on Ethereum, it runs here.
Point viem, ethers, Foundry or Hardhat at chain 125 and you are connected. When you need the agent parts, one SDK call pays, waits for the receipt and hands it back.
npm install @sidiora/layerx-sdk viemSDKs for TypeScript, Python, Rust, Go, Java, Kotlin, .NET and Swift. The MCP server exposes the same calls to any assistant.
chain.ts
import { createPublicClient, defineChain, http } from 'viem'
export const paxeer = defineChain({
id: 125,
name: 'Paxeer X Network',
nativeCurrency: { name: 'Paxeer', symbol: 'PAX', decimals: 18 },
rpcUrls: { default: { http: ['https://api-mainnet-beta.paxeer.network/rpc'] } },
blockExplorers: { default: { name: 'Paxscan', url: 'https://paxscan.io' } },
})
const client = createPublicClient({ chain: paxeer, transport: http() })
await client.getChainId() // 125
await client.getBlockNumber()search.ts
import { WebSearchClient } from '@sidiora/layerx-sdk'
// A paid web search for a tenth of a cent. The request carries
// its own payment, and the signed answer comes back in one await.
const search = new WebSearchClient({
endpoint: 'https://search.paxeer.network',
network: 'layerx:paxeer',
nativeAsset, // PAX
assets, // what the agent may pay in, and the cap per request
payer, // the agent's wallet and its spending rules
})
const { results, receipt } = await search.search('EUR/USD fix today')
What gets built here.
Anything where software spends or earns money by the request.
All use cases
Agent paymentsAn agent gets its own wallet, a funded budget and a key that expires. The network refuses anything past the cap.
Paid inferenceA model provider prices each request or each second of compute. Payment settles with the work, not thirty days later.
Paid APIsA data provider sells per request over plain HTTP. No accounts, no invoices, no card on file.
TradingHyperpax perps and spot markets run inside the LayerX kernel, with matching, margin and liquidation settled in one batch.
Token launchThe bonding-curve launchpad on the Paxeer X chain mints a fixed supply and opens a market with no liquidity deposit.
TreasuryFinance and operations teams set limits, approve held actions with a passkey and export statements that verify offline.
From the team.
All posts
Thesis21 Oct 2026Software needs a wallet of its own
Agents already search, compare and call paid services for us. When it is time to pay, they borrow a person's card or a shared API key. Paxeer X gives software its own wallet, with limits a person sets and the network enforces.
7 min read
Agents30 Sept 2026Building an agent with the SDKs and MCP
From a local emulator to a model that can pay for what it uses. A practical walk through the Paxeer X SDKs, the layerx CLI, the agent daemon and the MCP server, and how each layer keeps the agent inside its limits.
8 min read
Developers9 Sept 2026Paying per call over plain HTTP
402LXP lets a service charge for a single HTTP request with no account, no invoice and no card on file. The service answers 402, the caller pays inside the request, and the handler runs only once a signed receipt verifies.
7 min readGive your software a wallet.
The network is running in mainnet beta. Tell us what you are building and we will get you an allocation.