Software pays.People set limits.

Sidiora Labs develops Paxeer X: one network where an agent, an app or a service holds a wallet, pays per request and gets a signed receipt for every activity.

See open roles Contact the team

Fig. 1 A budget with a cap

Fig. 2 An agent with a wallet of its own

Software needs money of its own.

Agents already buy tools, data and compute as part of their normal work. The rails they borrow were built for people: accounts, invoices and a statement at the end of the month.

Paxeer X gives that software a wallet with limits a person sets, payment inside the request, and a signed receipt for every activity. Models learned to decide. We build the money they can be trusted with.

The whole network lives in one public repository, under the Apache 2.0 license.

Read the code on GitHub

Where it stands.

Two dated steps so far, a limited beta today, and a network open to every builder next.

Jan 2026
Chain ID 125 starts running
The Paxeer X chain starts running on mainnet: EVM compatible, BFT consensus, with PAX as the native gas and settlement asset.
May 2026
The Machine Economy whitepaper
Sidiora Labs publishes the full argument: why software needs money rails of its own, and how Paxeer X provides them.
Now
A limited beta on real value
LayerX runs in a limited beta that has not opened to the public. Approved developers build with allocations from the team. There is no public faucet.
Next
Open to every builder
The beta opens beyond approved teams, and agent framework adapters keep growing.

What we hold ourselves to.

Four rules that decide what goes into the protocol and what stays out.

The person decides: An agent spends only inside limits a person sets: how much, on what, with whom and for how long. The network enforces them, so neither the agent nor a stolen key can get past them.
Receipts over trust: Every activity on LayerX returns a signed receipt you can check yourself, today or years from now. Finance gets a statement it can audit. Builders get proof they delivered.
One network: Two execution domains, one account, one ledger. Payments, limits, identity and markets live in the protocol, so you integrate once and everything works together.
Open by default: The code is public under Apache 2.0, and so are the rules. Anyone can read the spec, verify a receipt or propose a change.