What teams buildon Paxeer X.
Six scenarios, each mapped to the parts of the network that make it work: agents that pay, services that get paid, markets that settle, and the controls that keep a person in charge.
- AgentsAgent payments
Agents that payinside your limits.
An agent gets its own wallet, a funded budget and a key that expires. The network refuses anything past the cap.
Agent SDK, MCP adapter
- PaymentsPaid inference
Inference, paidby the call.
A model provider prices each request or each second of compute. Payment settles with the work, not thirty days later.
Payment middleware, streams
- PaymentsPaid APIs
One API call,one receipt.
A data provider sells per request over plain HTTP. No accounts, no invoices, no card on file.
402LXP, x402 middleware
- MarketsTrading
Markets thatfail closed.
Hyperpax perps and spot markets run inside the LayerX kernel, with matching, margin and liquidation settled in one batch.
Agent SDK, exchange precompile
- MarketsToken launch
Launch a tokenin one call.
The bonding-curve launchpad on the Paxeer X chain mints a fixed supply and opens a market with no liquidity deposit.
Launchpad precompile, SDK
- OperationsTreasury
Approve and auditevery agent move.
Finance and operations teams set limits, approve held actions with a passkey and export statements that verify offline.
Human control plane, passkeys
What every use case stands on.
The scenarios differ. The parts underneath are the same four, and each has its own write-up on the blog.
Signed receipts
Every activity returns a receipt signed by the sequencer, with the state root before and after. Anyone holding it can check it offline.
A receipt for every activityGrants that only narrow
Eight authority kinds, from owner to timelock. A session key can be amended to do less, never more, and one revocation bump retires every old grant.
Session keys that can only do lessPayment inside the request
402LXP answers an unpaid call with a price. The handler runs only once a LayerX receipt verifies against the exact offer.
Paying per call over plain HTTPTwo domains, one network
An EVM chain on chain ID 125 and LayerX, the agent domain, under one network identity, with evidence crossing between them.
One network, two execution domainsBuild the next one.
The limited beta is open to approved developers. Tell us what you are building and we will get you an allocation.