CLI Overview
The Amoeba CLI is the command-line surface for users who need repeatable market access without clicking through the web app.
It is useful for:
- checking market and settlement state;
- reading wallet, ledger, and purchase history;
- preparing exact collective-secondary routes and collective writer operations;
- signing with a local wallet;
- submitting reviewed transactions through the configured API or RPC path;
- inspecting collective writer, market, oracle, and settlement state;
- queueing AMBA staking, activating sAMBA after the wait, or cancelling the queue.
How it fits into Amoeba
Section titled “How it fits into Amoeba”The CLI does not replace the website. It gives the same system a scriptable interface.
| Layer | What the CLI uses |
|---|---|
| Web app parity | Both use the same market/oracle API; Petri currently implements collective plan validation and local signing while browser trade submission remains paused. |
| API and edge services | Versioned services provide market snapshots, route preparation, trade submission, ledgers, and settlement views. |
| Pure Lean | Maintained queries define economic admission, writer previews and deterministic plans, plus monthly provisioning selection. Planner output alone is not live authorization. |
| On-chain program | ameba_spread remains the source of truth for custody, supply, external OI, reserve, venues, oracle state, staking, settlement, and claims. |
Basic workflow
Section titled “Basic workflow”Most CLI use follows this sequence:
- configure the API URL, RPC, network, and signer;
- inspect markets and wallet state;
- prepare a trade, writer action, or other supported operation;
- review the route;
- sign with a local keypair;
- submit through the command’s configured API or RPC path;
- track ledger, operation, and settlement state.
Command families
Section titled “Command families”| Family | Use it for |
|---|---|
markets and contracts |
Discovering live markets and bounded contracts. |
trades and writers |
Preparing/submitting collective secondary swaps and current writer/Flat operations. |
liquidity |
Manager-liquidity JSON parity without public Petri signing or submission. |
wallet and history |
Reading balances, collateral, and indexed activity. |
staking |
Reading AMBA/sAMBA value, queueing AMBA, activating or cancelling the queue, and unstaking. |
settlements and oracle |
Inspecting settlement, evidence, rewards, and semantic drafts. |
config, mcp, update, and tui |
Managing user-safe settings, agent access, updates, and the interactive terminal. |
Reader rule
Section titled “Reader rule”If you only want to understand Amoeba, start with the site overview and options pages. Use the CLI section when you need to inspect live state, automate a workflow, or sign with a wallet outside the browser.
The CLI examples use placeholder keys, public keys, and transaction signatures. Do not paste private key material, seed phrases, API keys, or keypair JSON contents into documentation, chat, or terminal history.

