Paxeer X Network

Agent-ready
Sub-cent
One account

Works with

EVM · Chain ID 125
402LXP

Chains built for people make an agent bolt on everything else.

Custody code, budgets, API keys, invoicing and reconciliation for every agent you run is a headache you don’t want.

Paxeer X puts identity, payment, discovery and settlement into the protocol, so an agent transacts inside the rules you set and nowhere else.

Paxeer X handles all of this for you, inside the protocol.

Wallets with rules, payments over 402LXP, a service registry and settlement records, all reachable through one endpoint.

You build the agent. The network handles the money.

Agent wallets
402LXP payments
LayerX settlement
Service registry
Session keys
Settlement records

Settled activities / min

148.6

Sample data, for illustration.

Spending caps, allowlists and stop conditions travel with the money and are enforced by the network itself.

A service answers HTTP 402, the agent pays in USDX on LayerX, and the call completes. No invoices, no keys to rotate.

Every settled call leaves a verifiable record that wallets and registries read before routing new work.

Learn more about Paxeer X Read the docs

Here’s what runs on Paxeer X today:

LayerX

The agent domain inside Paxeer X: about 1/10 of a cent per activity, instant settlement, batches committed to the chain every few minutes.

402LXP

The HTTP 402 payment flow on LayerX. A service answers 402, the agent pays in USDX, and the call completes.

USDX

The dollar-denominated settlement currency on LayerX. What agent services price in, invoice in, and settle with.

One account

An EVM address and its agent identity resolve to a single account, with both halves on one explorer page.

PaxScan

Blockscout-based explorer with live network stats, verified contracts, and onchain settlement records.

Paxeer DAO

Onchain governance for protocol parameters, registry spam controls, slashing conditions, and attestation methods.

Build portal

Templates, scaffolds, and reference implementations for agent commerce, providers, and 402LXP integrations.

Network status

Live uptime and performance for the L1 RPC, the LayerX sequencer, and indexing services.

Compute and inference

GPU capacity, model serving, batch jobs. Stream payment as the call executes and settle with a record.

Data and oracles

Signed queries, subscription feeds, freshness-bounded references. Payment, evidence, and reputation settle on Paxeer.

Agent automation

Browsing, scraping, transformation, and tool-use primitives that agents call against published policies.

Verification

TEE attestation networks, proof systems, and evidence commitments that services and agents call before they pay.

Start building Read the docs

Direct deployment integrations. Give any of these runtimes a Paxeer X wallet and it can pay for work, settle on LayerX and leave a record, with no custody code of its own.

How Paxeer X saves the people running agents time, money and development resources.

Agent frameworks

Smart wallets with policy baked in, per-call payments, and a registry your agents query and settle against.

The policy lives in the wallet, not in your code. Spending caps, allowlists and stop conditions are enforced by the network, so an agent can pay for work on its own without holding the keys to everything.

Build with the SDK

Wallets with rules, payments over 402LXP, a service registry, and a record of every job, on the Paxeer chain and the LayerX agent domain, behind one account.

Start building Read the docs

Chain ID 125 · 1/10 of a cent per LayerX activity

Chains built for people make an agent bolt on everything else.