Skip to main content
All Moneda CLI commands follow the pattern moneda <group> <command> [options]. Use moneda <group> --help to see available commands in any group.
Manage your CLI session.
View your account details and settings.
Browse, categorize, and export your transactions.
Manage your Moneda and external contacts.
Send money and check payment status.
Payments initiated via the CLI always require confirmation in the Moneda mobile app before they are executed.
Check your points balance and activity.
Manage your referral program.
Search the Moneda knowledge base.
Manage saved bank accounts.
Manage saved external wallets.
Read-only access to your sub-accounts (nested Safe smart accounts).moneda vault is an alias for moneda sub-account.These commands only propose: each creates a request you approve (and sign, when money moves) in the Moneda app. They need the write:sub_accounts scope.To pay someone from a sub-account, use moneda payment send --from sub-account:<UUID>.
Creating, closing, unfreezing and managing members of a sub-account stay in the Moneda mobile app.
Read-only access to social recovery contacts and ZK email-based recovery.
Recovery initiation, guardian invitation, and recovery execution are passkey-signed flows that live in the mobile app.
Read-only checks on your tokenized-equity (dShares) brokerage status.
There are no write commands here on purpose. Brokerage disclosures and personal attestations are accepted by you in the Moneda app, having seen the actual document — never relayed through a CLI session, API key, or agent.
List your passkeys and rename them.
Use a key with --api-key (or moneda config set api_key mnd_…) to run the CLI without logging in — handy in CI. A key can never carry more access than the credential that created it, and never covers payments.
Registering, replacing, or removing a passkey needs a WebAuthn ceremony on the device, so those flows live in the mobile app. The label is cosmetic and carries no security weight.
Current rate quotes.
Spending breakdowns over a time period.
summary is the odd one out: it reports fiat totals and takes --period 7d\|30d\|90d. Every other breakdown is denominated in the stablecoin actually held, so --currency is required and takes USDC, EURC, CHFAU, CADD or MXNB with a 1d\|1w\|1m\|1y window.
Read-only access to in-app notifications.
Mark-as-read / dismiss / clear-all are tied to the active mobile push session and stay in the app — they’re not exposed via the CLI.
Browse, search, upload, and manage transaction receipts and their parsed line items.
Read-only access to the accounts-payable queue. Bills are the invoice-shaped sibling of receipts; paying / uploading / linking is handled in the mobile app.
Read your balance-pay subscription charge history and generate ZUGFeRD plan invoices (PDF/A-3 with embedded EN 16931 XML). The invoice generator is idempotent — the first call renders + uploads, subsequent calls return a fresh 1h presigned download URL.
Beyond moneda payment send / status (above), the payment group exposes route discovery and quoting:
Read access, pause/resume, and proposing a recurring payment. Activate / cancel / edit / renew are NOT exposed: they need the user’s passkey signature on a Smart Sessions install UserOp, which is mobile-app only. A proposal waits for the user to activate it in the app.
Read and cancel crypto limit, stop-loss, take-profit and trailing-stop orders. Creating an order is app-only: it needs your passkey to sign. cancel needs the write:trades scope.
Read access plus pause/resume/revoke for scoped autonomous agent sessions. Create / execute and the passkey-bound install are not exposed via the CLI. Both scopes (read:agent_sessions, write:agent_sessions) are opt-in.
List the devices and clients signed in to your account plus your connected agents, and sign other devices out. read:sessions is a default scope; the terminate commands need the opt-in write:sessions scope.
Redeem a completed top-up payment to Moneda for prepaid AI usage credits, and manage your monthly spend limit. The purchase amount is read from the confirmed payment and granted once (idempotent on the hash). The write:usage_credits scope is opt-in.
Manage CLI settings.
Make raw HTTP requests to the Moneda REST API.This is useful for accessing endpoints that don’t have a dedicated CLI command, or for scripting and debugging.
api-schema (aliased schema) asks the deployment what it actually serves, rather than what these docs say. It needs no login, so it also works before you authenticate.
Both commands exit non-zero when the request fails, so they compose in scripts: moneda api GET /v1/balances || echo "unreachable".

What’s next?

CLI Examples

See common workflows and scripting patterns.

CLI Authentication

Set up and manage your CLI credentials.

API Endpoints

See the full REST API endpoint reference.

Scopes

Understand which permissions each command uses.