Sidiora Labs
Build on Paxeer X Try Gideon

A network for the era of the machines.

Paxeer X

Paxeer X is one network: an EVM-compatible chain at chain ID 125 with the LayerX agent domain running inside it. Agents hold funds in wallets with policy rules, pay for work over 402LXP and leave a signed record of what they did.

Start buildingRead the docsSee Centra AI
Paxeer X, execution and exchange infrastructure: crossing blue beams

Available today

Mainnet is live. LayerX, 402LXP payments and USDX settlement are available today. The service registry is growing as providers come onboard.

Who it is for

The user and the job.

01

Agent builders and frameworks

Authorize activity inside rules you set. Spending caps, allowlists and stop conditions live in the wallet and are enforced by the network, so the agent never holds the keys to everything.

02

Compute, inference, data and oracle providers

List a service on the registry and get paid per call over 402LXP while the call runs. Every settled call adds to a delivery record buyers can check before they hire.

03

Operators and treasuries

Account for payment and inspect what happened. Receipts verify offline against chain state, and funds move between chain custody and the agent domain through one audited path.

How it fits together

Where each responsibility lives.

Not every agent action settles identically. An activity executes on LayerX and returns a receipt immediately; its batch is committed to the chain a few minutes later; a withdrawal from custody needs a receipt in a finalized checkpoint.

  1. Your runtime

    Agent or application

    Holds a policy-bound wallet, signs activity envelopes and calls services over HTTP.

  2. Execution and receipts

    LayerX agent domain

    Sequenced execution, sequencer-signed receipts with state roots, 402LXP payments in USDX. About a tenth of a cent per activity.

  3. Custody and settlement

    Paxeer Chain

    EVM chain ID 125. The custody vault holds funds; checkpoints, challenges, withdrawals and forced exits are enforced here.

  4. Counterparties

    External systems

    Services answering HTTP 402, explorers reading settlement records, bridges to other chains.

Components

  • Agent wallets with policySpending caps, allowlists and stop conditions enforced by the network.
  • 402LXPThe HTTP 402 payment flow on LayerX: a challenge, a signed receipt and a settled call in one exchange.
  • USDXThe dollar-denominated settlement currency on LayerX.
  • PAXThe native gas and settlement asset of the chain.
  • Service registryDiscovery with reputation built from onchain settlement records.
  • Receipts and replayEvery activity returns a sequencer-signed receipt that can be re-executed and byte-compared.
  • Custody vaultFunds held on the chain with a single exit path and forced exit if checkpoints stop.
  • SDKs, CLI and adaptersPython and TypeScript SDKs, the LayerX CLI and adapters for existing agent frameworks.
  • PaxScan and network statusA Blockscout-based explorer and live status for the RPC, sequencer and indexing services.

Products

What is available, and what is coming.

All products
Paxeer X · InfrastructureMainnet · live

Paxeer Chain

The EVM-compatible Layer 1 inside Paxeer X that holds custody, anchors checkpoints and settles agent activity.

Availability
EVM-compatible mainnet with a public RPC endpoint, the PaxScan explorer and a published network status page.
Learn morePaxeer X Network
Paxeer X · InfrastructureLive on Paxeer X

LayerX

Where agents run and pay: signed activities, signed receipts and per-call payments for a fraction of a cent.

Availability
The agent domain running inside Paxeer X. Activities execute with signed receipts and batches settle to the chain every few minutes.
Learn moreLayerX on Paxeer X

How it works

A paid call, from request to receipt.

A layered cobalt loop sculpture

Environment

Paxeer X mainnet, chain ID 125, as described in the public developer documentation and feature specifications.

A dated recording is used in meetings and is attached here once approved. The steps are the static equivalent.

  1. 1

    Request

    Input
    An agent calls a priced API.
    Behaviour
    The service answers HTTP 402 with a payment envelope naming the asset, amount, recipient and required commitment level.
    Result
    The agent holds a quote it can accept or refuse under its wallet policy.
  2. 2

    Policy check and payment

    Input
    The agent selects an alternative and pays in USDX on LayerX.
    Behaviour
    Wallet rules are enforced by the network. The activity executes once and returns a sequencer-signed receipt, or the request is refused.
    Result
    An accepted activity with a receipt, or a rejected one with a result code.
  3. 3

    Verification

    Input
    The service receives the receipt or a signed grant draw.
    Behaviour
    It verifies the evidence against its configured network authority before releasing anything. Missing evidence never downgrades a request.
    Result
    The call completes with a settlement reference bound to the receipt digest.
  4. 4

    Inspection

    Input
    A receipt digest.
    Behaviour
    Anyone holding the receipt can check the sequencer signature and state roots offline. The batch is later committed to the chain and visible on PaxScan.
    Result
    A record that follows both the agent and the provider.

  5. What this does not show

    A receipt proves execution on LayerX. Chain finality follows the batch commitment, and withdrawal from custody requires a receipt in a finalized checkpoint. A retry with the same idempotency key returns the first receipt rather than paying twice.

Docs and status

Documentation, source and live status.

Research

The questions behind the work.

All papers

Next step

Build on the network, or ask for a walkthrough.

The quickstart states prerequisites and the expected result. For partnerships or a walkthrough, write to the team.

Start buildingTalk to the team