Protocol

The protocol for agent commerce

Policy-bound wallets, HTTP 402 payments over 402LXP, zero-fee settlement on LayerX, and onchain records of every fill. A place for software to spend, earn, and settle.

Network architecture

Paxeer is an EVM-compatible L1. Dual sequencer lanes carry 5,000 TPS peak at ~250ms average blocks. Deterministic finality and full EVM compatibility form the base the rest of the protocol runs on.

EVM chain ID

125

Throughput

5,000 TPS

peak, dual sequencer lanes

Average block time

~250ms

measured at the block

Finality

Deterministic

at the block, no reorgs

Public RPC

https://public-rpc.paxeer.app/rpc

What the protocol does

Policy-bound smart wallets

Identity and spending control for agents

An agent transacts from a smart wallet that carries its own rules: whether it can spend, where, how much, and when it must stop. The rules live in the wallet at the protocol layer, not in application code around it.

Spending caps, daily limits, and absolute budgets
Service allowlists and capability scoping
Session keys with time-bounded permissions
Stop rules on drawdown, error rate, or quality drop
Recovery, revocation, and rotation paths

402LXP payments

HTTP-native payment for machine services

402LXP is the HTTP 402 payment flow on LayerX. A service responds with HTTP 402, the agent pays inside the request flow, and the call proceeds. Payments are denominated in USDX and work per call or as a stream over a long-running job.

Standard HTTP 402 request and response flow
Per-call payment for single API requests
Streaming payment for long-running work
Denominated in USDX on LayerX
Zero fees on the LayerX channel

LayerX settlement

Agent-only side channel, anchored to L1

LayerX is Paxeer's agent-only side channel: zero fees and instant settlement for agent transactions. Batches settle to Paxeer L1 every few minutes, so high-frequency agent traffic never pays L1 gas but still anchors to the chain. Deus, PaxLabs' API and agent marketplace, runs on LayerX.

Zero fees for agent transactions
Instant settlement on the channel
Batches anchored to Paxeer L1 every few minutes
USDX as the settlement currency
Home of the Deus marketplace

Onchain settlement records

Delivery history any counterparty can check

Every settled service call leaves a record on chain: what was paid, to whom, and how delivery went. Wallets and agents can read a provider's history before transacting, and a provider carries that history across every application on the network.

Settlement and delivery history written on chain
Readable by wallets and agents before a trade
Portable across applications and marketplaces
Usable as an input to allowlists and stop rules
Inspectable on PaxScan like any other state

What the network gives you

Finality inside the interaction window

~250ms average block time, finality deterministic at the block. Agents settle inside a normal interaction window.

Fully EVM compatible

Native EVM execution on chain ID 125, gas paid in PAX. Foundry, Hardhat, ethers, wagmi, and viem all work out of the box.

LayerX agent channel

The agent-only side channel: zero fees and instant settlement. Batches settle to Paxeer L1 every few minutes; Deus, PaxLabs' agent marketplace, runs here.

Explore LayerX →

Neutral coordination

Transparent records and neutral rules, no privileged operator. The chain owns the parts the market should not.

By the numbers

~250ms

Avg block time

5,000

TPS peak, dual lanes

USDX

LayerX settlement currency

125

EVM chain ID

Native asset

Settlement and gas asset

PAX

PAX pays for execution, registry writes, escrow, and settlement-record updates on L1. It is the native gas token on chain ID 125, with 18 decimals.