What is Paxeer X?

Paxeer X is a public network where software can hold money, pay for things, get paid, trade and run programs on its own, inside limits a person has set.

Underneath, it is a blockchain: a shared record of who owns what, kept by many independent computers rather than one company, so nobody can quietly rewrite it. It runs the same kind of programs as Ethereum, which means MetaMask works, Foundry and Hardhat work, and a developer who has written for Ethereum already knows how to write for Paxeer X. Wallets know it as chain 125.

What makes it different is who it was built for. Almost every payment system in the world assumes a person is at the keyboard, approving each purchase as it happens. Paxeer X assumes the opposite: that a program, say an AI agent, will be doing business by itself, thousands of times a day, and that the person who owns it wants to stay in charge without being in the loop on every transaction. LayerX is the name of the toolkit that makes this easy, and it is built into the chain rather than bolted on beside it.

Software already shops for us. It searches, compares, books, orders, and calls paid services on our behalf. When the moment comes to pay, though, it borrows. It borrows a person's card number, or an API key tied to one company's monthly bill. That works for a demo. It falls apart when an agent makes four thousand small purchases a day from services it discovered an hour ago.

A card cannot be told to spend at most twenty dollars a day on one vendor and nothing after Friday. An invoice cannot be settled for a tenth of one cent. An API key, once leaked, is a blank check. And when money does move, the seller rarely holds proof the buyer can check and the buyer rarely knows for sure the money arrived until a statement shows up days later.

Paxeer X puts the missing pieces into the network itself. Limits that the network enforces, not the agent. Payments small enough to price a single API call. A signed receipt for every transaction, back in milliseconds, final within about a second. Think of it as the difference between handing an intern your wallet and giving them a company card with a limit, an approved vendor list and an automatic expense report.

You do, and in a way that does not depend on the software behaving. When you fund an agent on Paxeer X you write down the rules: a budget for each day or week, the services it may pay, the hours it may operate, and how much any single payment may be. You then hand the agent a key that only works inside those rules and stops working on a date you pick.

The network checks those rules on every transaction. They are not a setting in the agent's own code, where a bug or a bad prompt could skip them. If the agent tries to spend past its budget, the payment is refused before it leaves. If you change your mind about the whole arrangement, one call revokes everything the agent was allowed to do, and the next thing it tries simply fails.

The same idea protects the person on the other side. A provider selling a service gets paid up to a ceiling the buyer agreed in advance, once per request and never past the cap. When two parties want more assurance, money can sit in escrow until the work is delivered, with a referee both agreed on before they started. Every agent also carries an identity tied to its owner, so a receipt names not just an address but who is responsible for it.

Very little, and you can choose who pays. Every transaction on the network costs a small fee, paid in PAX, the network's own coin, or in SID, the second coin. The fees are set by governance to stay near zero, so a payment of a tenth of one cent still makes sense. Paid web search on the network, for example, is priced at $0.001 per request and each request is paid separately.

If you are building an app for ordinary people, you can sponsor the fees yourself, up to a limit per user, so your customers never buy a coin or see the word gas. That is how most consumer apps on the network run. Anyone who prefers to pay their own way still can.

PAX also does two other jobs. Validators, the computers that keep the shared record, stake it to take part, and holders use it to vote on how the network changes. A vote takes about an hour, not a quarter. You can read more on getting PAX and SID.

Anything where software needs to move money without a person watching. An agent that researches a question and pays the sources it uses. A model provider that charges per inference and gets paid as each answer leaves the server. A subscription that streams payment by the second for as long as a job runs and stops the moment it ends. A marketplace that holds the buyer's money in escrow until the seller delivers.

The network also has markets of its own. Perpetual futures and spot trading run on the chain, with margin, funding and liquidation handled there, so an order fills in the same transaction that placed it. Anyone can launch a token that trades from the first minute. And small programs written in WebAssembly can hold money, call each other, and pay for data, which is how the network's markets for renting compute and for AI tasks are built.

For developers, there are SDKs in TypeScript, Python, Rust, Go, Java and Kotlin, .NET and Swift, a CLI, a local environment, and an MCP server that gives an assistant a wallet and the tools to use it. The whole codebase is open source under Apache 2.0, built by Sidiora Labs. If you want the full technical picture, the whitepaper has it.