Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Command index

Every JSON-capable command, with what it touches. “Identity” means the local mcli.db must already exist; no JSON command creates it.

CLI pathcommandKindNetworkIdentityLocal write--yesStatuses
schemaschemaofflinenonenononook, error
order listorder.listpublic readreads relaysnononook, error
order infoorder.inforequest1 signed requestyes (read)nonook, error
message listmessage.listprivate readreads relaysyes (read)nonook, error
order syncorder.syncprivate read + local writereads relaysyesorder rowsnook, error, uncertain
order neworder.newwrite1 signed requestyesindex + rowyesok, error, uncertain
order take-sellorder.take-sellwrite1 signed requestyesindex + rowyesok, error, uncertain
order take-buyorder.take-buywrite1 signed requestyesindex + rowyesok, error, uncertain
order add-invoiceorder.add-invoicewrite1 signed requestyesstatusyesok, error, uncertain
bond add-invoicebond.add-invoicewrite1 signed requestyesnoneyesok, error, uncertain
order fiat-sentorder.fiat-sentwrite1 signed requestyesstatus (+ index)yesok, error, uncertain
order releaseorder.releasewrite1 signed requestyesstatus (+ index)yesok, error, uncertain
order cancelorder.cancelwrite1 signed requestyesstatusyesok, error, uncertain

All of them need MOSTRO_PUBKEY and RELAYS except schema, which needs nothing.

Which key signs what

CommandSigned with
order infoIdentity key (index 0)
order new, order take-*A new trade key at the next trade index (reserved locally first)
order add-invoice, bond add-invoice, order fiat-sent, order release, order cancelThe trade key stored with the order’s local row (hence order_unknown when the row is missing)

Command page layout

Each page has the same sections: a summary table, Invocation, Input, Behavior, Success data, Outcomes, Errors, Warnings, Examples and Next. The input and output schemas quoted are in schemas/<command>.input.json and schemas/<command>.output.json.

Input schemas

The discovery document gives an input_schema per command, generated from the argument parser: one property per long option (fiat-amount, yes…). All values are typed as strings because they are command-line tokens; boolean flags appear as "true"/"false". A wrapper can use it to build forms or LLM tool definitions, then turn the object into argv: {"order": "…", "yes": "true"} → --order … --yes. Repeatable options (order info --order) are given once per value.