Developers

Everything from key to receipt, without leaving the terminal

The layerx CLI does what the SDKs do, but at the prompt, with every step disclosed before it signs.

For a developer, it is the fastest way to see a real receipt. For an operator, it is a scriptable, auditable way to move money.

Installation guide Try it on the emulator

Before you write a line of integration code, you want to see the thing work. Create a wallet, fund it, send a payment, read the receipt. The layerx CLI does that in four commands, then grows with you: local and hosted environments, program deployment, receipt lookups for support tickets, and one-line installs of the MCP and A2A servers that let an AI assistant use the same wallet.

first-runtextReady

1layerx register2layerx wallet balance3layerx wallet send --to <recipient> --asset <asset> --amount 1004layerx receipt <txHash>

What it covers

Keys and environments

Generate or import keys, keep them in the OS keyring or an encrypted vault, and switch between the emulator and the live network with one command.

Wallets and tokens

Create and list wallets, read balances, send value, create a token, mint and burn.

Payments and receipts

Send, then fetch the signed receipt by transaction hash and see whether it is receipted or committed. Paste the hash into a support thread and anyone can check it.

Programs

Scaffold a new program project, build and test it, deploy, upgrade and wind it down.

Emulator

A private copy of the network on your machine that issues real signed receipts, listening only on localhost.

Agent servers

Install the MCP server into Claude Code, Claude Desktop, Cursor or VS Code, or start an A2A server, each bound to a wallet with limits.

From zero to a receipt

01
Register
layerx register creates a signing key and binds an agent identity to it. Registration is sponsored, so there is nothing to fund first.
02
Check the balance
layerx wallet balance reads PAX, SID and any tokens the wallet holds, straight from the network.
03
Send
layerx wallet send prints exactly what it is about to sign: recipient, asset, amount and fee limit. Only then does it sign and submit.
04
Read the receipt
layerx receipt <txHash> shows the result, the fee and the current status. Add --json and the same output drops into a script or a spreadsheet.

Built to not surprise you

Every write is disclosed in full before it is signed, so a script cannot send something you did not read.
An acknowledgement is never reported as success. The CLI waits for a verified receipt, or tells you the transaction is still only submitted.
Secrets live in the OS keyring by default. Headless servers use an encrypted file vault with a strong key derivation.
The emulator refuses to listen on anything but localhost, so a test wallet never ends up on the open internet by accident.
Public endpoints must be HTTPS. Plain HTTP is accepted only for localhost.

For operators

The --json flag on every command gives you stable output for cron jobs, runbooks and reconciliation scripts. Pair it with the signed receipt and your finance team has evidence, not logs.