Reference
Command-family map for operators and agents.
Surface Map
peer-cli spans protocol reads, state-changing operations, hosted services, and custody-separated Peer Cash tools.
| Domain | Groups | Read/Write |
|---|---|---|
| Quotes and payees | quote, payee, taker | mixed |
| Deposits | deposit | mixed |
| Protocol reads | pv, indexer | read-only |
| Intents and hooks | intent, intent-hook | mixed |
| Stake and protection | stake | mixed |
| Vault and delegation | vault, delegate, undelegate, oracle | mixed |
| Market intelligence | market | mostly read; key management writes |
| Funds operations | transfer, balance | mixed |
| Checkout | checkout | mixed |
| Local runtime | config, mcp | local state and server bootstrap |
| Peer Cash | peer_cash_* MCP tools | reads plus unsigned transaction preparation |
How To Navigate The Surface
- Use Quotes, Payees, and Taker State when the job starts from pricing or user routing.
- Use Deposits for liquidity inventory, payment method setup, oracle configuration, and deposit mutations.
- Use Protocol Reads and Intents for intent visibility and fulfillment flows.
- Use Staking and Dispute Protection for StakeVault state, shared stake, live risk windows, and matured releases.
- Use Vaults and Delegation for operator-controlled pricing and manager-level behavior.
- Use Market, Funds, and Checkout for analytics, direct transfers, and checkout lifecycle actions.
- Use MCP when the caller is a tool-using agent rather than a shell.
- Use Peer Cash for custody-separated crypto-to-fiat order preparation and recovery.
- Use Catalogs when you need machine-readable schemas and code lists.
Exact Schemas
Run peer --help, query the MCP server, or use the tagged generated catalogs.
They are generated from the runtime registries and own exact flags, schemas, and
error codes.