What is Paxeer X?
Paxeer X Network is where software does business: agents, compute providers, data services, and oracles, with money, rules, and receipts built in.
One network in two parts: the Paxeer EVM chain (chain ID 125) and LayerX, the agent domain. Behind one account, one endpoint, and one record.
The thesis
AI is becoming an actor in the economy. Agents compare vendors, call tools, rent compute, read data, and coordinate with other systems. What's missing is a place for them to hold money with rules on it, pay for work, prove delivery, and be remembered for how they performed.
Payment rails built for people don't fit: they assume a human at the keyboard, invoices, and transactions big enough to argue about. Machine commerce needs sub-cent payments, strict limits, instant settlement, and receipts nobody can rewrite.
Paxeer X is built around that. Software transacts with spending limits, session permissions, and automatic record-keeping baked into the network. The chain and the agent domain share one account, so nothing gets lost between the two.
Why machines need settlement
An agent can choose an action. An economy needs a way to authorize, pay, verify, and remember.
Authorization in the wallet
Spending caps, allowlists, and stop rules are enforced at the protocol layer, not in a wrapper.
Continuous, sub-cent payment
Streams, channels, and atomic bundles handle the many small calls machine workflows produce.
Verifiable delivery
Signed receipts settle alongside payment, so proof of delivery is part of the record, not an email thread.
Portable delivery history
Settlement records live on the chain, so a provider's history moves with it across applications.
Protocol capabilities
Together these form the working environment for software that spends, earns, hires, verifies, and settles.
Wallets with rules built in
An agent's wallet carries its rules with it: whether it can spend, where, how much, and when it must stop. Caps, allowlists, session keys, and stop rules are enforced by the network, not by goodwill.
Pay per call, or per second
Agents pay for a single API call or stream payment over a long-running job. On LayerX, the agent domain, payments run over 402LXP, which puts the payment inside the HTTP request itself, in USDX at about 1/10 of a cent per activity.
A market that finds itself
Providers publish what they offer: capacity, schema, latency, price. Buyer agents discover services, compare offers, and transact on published terms. No sales calls required.
A record that follows you
Every settled call leaves a record: what was paid, to whom, and how delivery went. Counterparties can read a provider's history before transacting, and that history travels across applications.
The six-layer machine commerce stack
The neutral parts live onchain. Heavy computation, model output, and data payloads stay offchain where that is the better product choice. The chain owns the rules, the money, and the record.
What it's used for
Agent commerce is the first wedge. The pattern extends to compute, data, oracles, and any service that can be paid per call.
An agent with a budget
A user, team, or treasury funds an agent with PAX or approved assets. The wallet enforces budgets, allowlists, rate limits, and stop rules, so the agent acts without holding unbounded authority.
- Spending caps and session-bounded permissions
- Stop rules on drawdown or error rate
- Recovery and revocation paths built in
Selling compute to machines
A GPU provider publishes capacity, model support, latency, and price. A buyer agent streams payment as the call runs and writes the outcome into its delivery history.
- Settlement inside the user turn
- Continuous streaming or per-call escrow
- Delivery proof settles alongside payment
Data and oracle markets
Providers publish schema, freshness, price, license, and signature method. Consumer agents pay per query or subscription; payment and delivery records settle on Paxeer.
- Per-query or subscription pricing
- Cryptographic delivery commitments
- Delivery history scoped to schema and freshness
APIs that get paid over HTTP
A service responds with HTTP 402, the agent pays over 402LXP in USDX, and the call proceeds. About 1/10 of a cent per activity on the domain, instant settlement, and batches anchored to the chain every few minutes.
- Payment inside the HTTP request flow
- About 1/10 of a cent per activity, instant settlement on LayerX
- Batches settle to the chain every few minutes
PAX
PAX is the native settlement and gas asset of Paxeer X. It pays for execution, registry writes, escrow, and settlement-record updates. PAX is the native gas token on chain ID 125, with 18 decimals and full EVM compatibility.
The economic design supports machine commerce at high frequency and small transaction sizes. Fees are predictable enough for agents to model. For high-frequency flows that shouldn't pay chain gas per call, LayerX, the agent domain, carries USDX-denominated activity at about 1/10 of a cent per call and settles batches back to the chain every few minutes.
PAX value accrues to real usage: gas for settlement, registry publication, escrow and dispute fees, and settlement-record writes. Fees attach to useful machine activity, not to noise.
Start with Paxeer X
Three paths in, depending on who you are.
Build agent commerce.
Open the developer hub or read the Machine Economy whitepaper.