Paxeer is the settlement and coordination layer for autonomous services: agents, compute providers, data services, and oracle networks.
An EVM-compatible L1 with dual sequencer lanes: 5,000 TPS peak, ~250ms average blocks, and protocol-level support for wallet policy, payments, discovery, and settlement records.
AI systems are becoming actors inside economic workflows. They compare vendors, call tools, book services, rent compute, read data, and coordinate with other systems. The more capable those agents become, the more obvious the missing layer becomes: a place to authorize the action, pay for it, verify delivery, and remember whether the counterparty performed.
Human payment rails were not designed for this. They assume account holders, card networks, manual disputes, and high-value transactions. Machine commerce needs smaller payments, tighter policy, continuous settlement, signed outputs, and delivery records that are portable across platforms.
Paxeer is built around the opposite assumption. Machines should be able to transact with strict spending limits, session permissions, price bounds, service-level rules, and automatic record-keeping. The chain does not replace every cloud provider or payment company. It owns the neutral coordination layer they do not expose.
An agent can choose an action. An economy needs a way to authorize, pay, verify, and remember.
Spending caps, allowlists, and stop rules are enforced at the protocol layer, not in a wrapper.
Streams, channels, and atomic bundles handle the many small calls machine workflows produce.
Evidence commitments settle alongside the fill; proof hooks support signed outputs and TEE attestations.
Settlement records are written on chain, so a provider's history moves with it across applications.
Together these form the execution environment for software that spends, earns, hires, verifies, and settles.
The wallet carries the agent's rules: whether it can spend, where, how much, and when it must stop. Spending caps, allowlists, session keys, and stop rules are enforced at the protocol layer.
Agents pay for a single API call or stream payment over a long-running job. On LayerX, the agent-only side channel, payments run over 402LXP, the HTTP 402 payment flow, denominated in USDX with zero fees.
Providers publish what they offer: capacity, schema, latency expectations, price. Buyer agents discover services, compare offers, and transact against published terms.
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 neutral parts live onchain. Heavy computation, model output, data payloads, and user-facing experience stay offchain where that is the better product choice. The chain enforces ownership, policy, settlement, escrow, evidence commitments, delivery records, and dispute outcomes.
Agent commerce is the first wedge. The pattern extends to compute, data, oracles, and API marketplaces.
A user, enterprise, DAO, or vault funds an agent with PAX or approved assets. The wallet policy enforces budgets, allowlists, rate limits, and stop rules. The agent acts without holding unbounded authority.
A GPU provider publishes capacity, model support, latency expectations, and price. A buyer agent streams payment as the call runs, holds escrow for disputes, and writes the outcome into its delivery history.
Providers publish schema, freshness, price, license, and signature method. Consumer agents pay per query or subscription. Output stays offchain when that is the right product choice; payment, evidence, and delivery records settle on Paxeer.
A service responds with HTTP 402, the agent pays over 402LXP in USDX, and the call proceeds. Zero fees on the channel, instant settlement, and batches anchored to Paxeer L1 every few minutes. Deus, PaxLabs' API and agent marketplace, runs this way.
PAX is the native settlement and gas asset of Paxeer. 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. Payment channels, streaming settlement, batching, and netting reduce overhead when a workflow has many small service calls. For flows that shouldn't pay L1 gas at all, LayerX, Paxeer's agent-only side channel, carries zero-fee, USDX-denominated activity and settles batches back to L1 every few minutes.
PAX value accrual attaches 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.
Three paths in, depending on who you are.
Open the developer hub or read the Machine Economy whitepaper.