Documentation / API reference

Wallet

Status and balances are safe to read from anywhere. Everything that moves funds signs on the node, never in the browser, and is curl-only in the playground.

Wallet status

GET/v1/walletBearerTry it →

The payout address, the chains and the settlement asset. Returns configured: false when there is no wallet — a normal state for a node that only consumes, not an error.

Balances

GET/v1/wallet/balancesBearerTry it →

GET/v1/wallet/historyBearerTry it →

Native and token balances, and the movement history read from the explorer.

Send funds

POST/v1/wallet/send/quoteBearer

POST/v1/wallet/sendBearer

Two steps on purpose: quote estimates gas and returns the exact fields, and send signs and broadcasts those same fields. Re-reading the form between the two would open the door to reviewing one thing and sending another.

Mainnet requires explicit confirmation. Send confirmar: "MAINNET" in the body. This moves real money and cannot be undone. The node signs, never the browser — the seed never leaves the process that opens it.

Not executable in the playground — this route moves real funds out of the node's wallet. See what the playground restricts for the generated curl.

Other wallet routes

Route	Description
`POST /v1/wallet/create`	Create a wallet (empty body) or import one (`{ frase }`). Returns the 24 words once for a new wallet
`POST /v1/wallet/network`	Switch network. No hot-swap: it saves and asks for a restart. Mainnet needs `confirmar: "MAINNET"`
`POST /v1/wallet/tokens`	Watch an ERC-20: `{ address, symbol, decimals }`
`DELETE /v1/wallet/tokens`	Stop watching a token

All four are curl-only in the playground: they create key material, change what network the node talks to, or edit what it watches.