Wallet & On-Chain Actions
How the embedded wallet works, what on-chain actions Neo can perform, LayerX for agent payments, and the spend safety layers that protect your funds.
Matrix gives every agent a built-in wallet that can read and write on the Paxeer chain. You do not need to install a browser extension or manage private keys yourself. The wallet is embedded at the network layer, with custody and key material handled by the Paxeer Embedded Wallet service.
Your agent wallet
When you first interact with the chain, Neo provisions an embedded wallet for your agent. This wallet:
- Has a Paxeer address that can receive and send PAX and ERC-20 tokens.
- Signs transactions server-side; private keys never touch agent code.
- Is governed by a spend policy (
PaxeerSpendPolicy) enforced at the wallet layer, not trusted to the agent.
You can check your wallet at any time:
you: What's my wallet address?
Neo calls
wallet_infoand returns your embedded wallet address and chain details.
What Neo can read
Neo has full read access to the Paxeer chain and its ecosystem of services:
| Capability | What it does |
|---|---|
| Balances | Native PAX and ERC-20 token balances for any address |
| Transactions | Transaction history, details, and receipt data via PaxScan |
| Token data | Token metadata, top holders, trending tokens, and prices |
| Portfolio | PnL, rank, and performance tracking via the Argus indexer |
| Contracts | Read-only eth_call against any contract, with ABI-encoded method calls |
| Chain state | Chain ID, head block, sync status, and network statistics |
| Oracles | Validator prices, oracle-relative prices, and clearing computations |
| Streams and jobs | Payment stream status and scheduled job details |
All read operations are free and require no wallet authorization.
What Neo can write
When you ask Neo to perform an on-chain action, it escalates to the rigorous MCL pipeline, which produces a typed plan for your review. Once approved, Neo signs and broadcasts the transaction through the embedded wallet.
Supported write operations:
| Action | Description |
|---|---|
| Transfer | Send native PAX or any ERC-20 token to an address |
| Approve | Authorize a spender contract to move your tokens |
| Contract write | Interact with any smart contract: DEX swaps, vault deposits, protocol calls |
| Payment streams | Open, settle, close, or update the rate of a continuous payment stream |
| Scheduled jobs | Schedule a transaction for a future block, cancel, or reschedule it |
| Staking | Delegate, undelegate, or redelegate PAX to validators |
| Message signing | Sign an EIP-191 message for identity proof or off-chain verification |
Every write operation is gated twice. First, a per-call spend ceiling is enforced at plan time before any side effect. Second, the Paxeer Embedded Wallet enforces its own spend policy at signing time. Without wallet authorization, chain access is read-only.
LayerX: agent-to-agent payments
LayerX is a settlement layer for instant, gasless agent-to-agent payments. It holds USD-denominated balances (USDX) that are escrow-backed and spendable across the agent economy.
How it works
Deposit USDL (the Paxeer stablecoin) into LayerX via the vault contract. Neo handles the approve-and-deposit flow for you, including the claim credential that credits your balance.
Send USDX to another agent by their DID (decentralized identifier). Payments are instant and gasless; the sequencer signs a receipt on the spot.
Every payment produces a signed inclusion receipt with a Merkle proof and the Paxeer anchor transaction. Receipts are publicly verifiable.
Burn USDX to release real USDL from the vault to your mapped Paxeer payout address. Optionally swap to another asset on the way out.
LayerX tools
| Tool | Description |
|---|---|
layerx_balance | Check your spendable USDX balance, escrow-bound funds, and mapped payout address |
layerx_deposit | Get the deposit parameters (vault address, claim credential) to fund your balance |
layerx_pay | Pay another agent instantly by DID |
layerx_receipt | Fetch the signed inclusion receipt for a payment |
layerx_withdraw | Burn USDX and withdraw real assets to your Paxeer wallet |
layerx_settle | Force-settle the current window and anchor the Merkle root to Paxeer immediately |
Durable actions
Some wallet operations (LayerX deposits, approve-then-call sequences) are handled as durable actions: they are executed across multiple on-chain steps, confirmed server-side, and are idempotent. If a step fails or the process restarts, the action resumes from where it left off rather than starting over or double-executing.
Each durable action returns an action_id that you can poll for status, transaction hashes, and error details.
PAX: the usage unit
PAX is the Paxeer Network unit that Matrix uses to price LLM usage in the credit ledger. Every metered model call is priced against a versioned rate card and debited from your PAX balance.
- Auditable. Every ledger row records the rate-card version that priced it, so historical costs stay reproducible even after rate changes.
- Free tier. A per-day PAX allowance covers a whitelist of default models. Beyond that, you bring your own provider key or top up your balance.
- Agent economy. PAX is also the unit used for on-chain transactions, staking, and LayerX deposits on the Paxeer chain.