Ship in the language your team already writes
Every SDK gives you the same three calls, send, receipt and verify, and the same idea of what a payment is.
Pick the package for your stack. The names differ, the behavior does not, so a Python buyer and a Rust seller agree about every payment down to the byte.
You should not need a blockchain team to charge an agent per request. The SDKs turn a payment on Paxeer X into something your existing code already knows how to do: call a function, get a result, keep the receipt. Install the package for your language and you are sending real value within the hour, with the signing, nonce handling and receipt checks done for you.
The same three calls everywhere
A write on Paxeer X is a standard signed transaction. You send it, you get back a signed receipt in milliseconds that tells you exactly what happened, and a moment later you can confirm it is final. The Python client below does all three against the network's single URL.
The receipt carries the result, the logs, the fee and who paid it, and the transaction's exact position in the global order, all signed by the network's receipt key. Each SDK ships a verifier that checks that signature offline, so your bookkeeping never has to trust the endpoint it just talked to.
Pick your stack
| Language | Package | Also ships |
|---|---|---|
| TypeScript | @sidiora/layerx-sdk | Browser entry, Express and Next adapters, buyer and seller middleware |
| Python | layerx-sdk | FastAPI integration for paid endpoints |
| Rust | layerx-sdk | The reference verifier and the agent daemon |
| Go | Go module | Receipt verification and program calls |
| Java and Kotlin | com.sidiora.layerx:layerx-sdk | Spring Boot starter, Android library |
| .NET | LayerX.Sdk | net8.0, streaming and verifier |
| Swift | LayerXSDK | SwiftPM package and iOS mobile payments |
What you get beyond the wire
- Budgets, grants and per-call draws for metered services
- Pay-exactly-once sends keyed by your invoice reference
- Streaming payments you can start, change and stop
- Gas sponsorship so your users never see a fee
- Perpetuals, spot markets and token launches
- Bridge deposits and withdrawals to nine chains
- Paid web search and fetch for agents
- Typed errors with a plain reason for every refusal
Every one of these is a typed call with a result you can test against the local environment first. The examples folder covers budget-constrained spending, HTTP 402 settlement, offline receipt verification and a full service lifecycle, in both TypeScript and Python.
Your existing tools still work
Paxeer X is chain ID 125 and speaks standard Ethereum JSON-RPC. viem, ethers, web3.py, Foundry, Hardhat and MetaMask work without a plugin. Use the SDK where it saves you work, such as receipts, budgets and paid calls, and your usual libraries for everything else. See JSON-RPC for the endpoint details.
Related
Send your first payment
The quickstart takes you from install to a verified receipt in one sitting.