Human-only commands

These commands still exist with their old spellings and human output only. With --output json each returns output_not_supported (exit 2) before doing anything: no configuration is loaded, no database is touched, nothing is sent. Their canonical names are already reserved and will be used when they gain JSON output.

CLI command	Reserved `command`	What it does
`rate`	`order.rate`	Rate the counterparty after a successful trade
`dispute`	`dispute.open`	Open a dispute on an order
`listdisputes`	`dispute.list`	List open disputes
`disputechat`	`dispute.chat`	Read the dispute conversation with the solver
`getdmuser`	`chat.history`	Read both sides of the peer chat of an order
`dmtouser`	`chat.send`	Send a peer chat message
`senddm`	`message.send`	Send a direct message to a user
`restore`	`account.restore`	Ask the node for your active orders and disputes
`getuserinfo`	`account.info`	Your reputation as the node holds it
`getlasttradeindex`	`account.trade-index`	Ask the node for your last trade index and store it
`getlasttradeprivkey`	`account.trade-key`	Print the last trade private key
`conversationkey`	`account.conversation-key`	Print a conversation key
`getadmindm`	`admin.message-list`	Latest direct messages (admin)
`admcancel`	`admin.cancel`	Cancel an order (admin)
`admsettle`	`admin.settle`	Settle a hold invoice (admin)
`admaddsolver`	`admin.add-solver`	Add a dispute solver (admin)
`admtakedispute`	`admin.take-dispute`	Take a dispute (admin/solver)
`admsenddm`	`admin.message-send`	Admin direct message
`sendadmindmattach`	`admin.message-attach`	Admin message with encrypted attachment
`admsetmaintenance`	`maintenance.set`	Toggle the daemon’s maintenance mode (operator, gRPC)
`admmaintenancestatus`	`maintenance.status`	Maintenance status (operator, gRPC)
`admcancelpending`	`maintenance.cancel-pending`	Cancel a pending order as operator (gRPC)

mostro-cli --output json getlasttradeprivkey

{
  "schema_version": "1",
  "command": "account.trade-key",
  "status": "error",
  "data": null,
  "error": {
    "code": "output_not_supported",
    "message": "This command does not support JSON output."
  },
  "warnings": [],
  "meta": {
    "publication": "not_attempted",
    "daemon_acceptance": "unknown",
    "persistence": "not_attempted",
    "snapshot": null
  }
}

general/output_not_supported_secret · exit 2 · fixture

Note the stages not_attempted / unknown / not_attempted: the command was resolved but not executed.

A wrapper that needs one of these today has to run it in human mode and treat its output as text for a person, not as data. Do not scrape it; its wording is not a contract.

Keyboard shortcuts

mostro-cli JSON Interface

Human-only commands