@catena/cli 0.10.0 → 0.11.0

package/README.md

@@ -181,9 +181,10 @@ npx @catena/cli mpp --url https://api.example.com/paid \
 
 The CLI recognizes structurally valid EVM `evm/charge` and `usdc/charge`
 challenges and leaves network and canonical USDC support to the connected
-server. Current support includes Base and Base Sepolia. Payments use the agent's
-normal send capability, counterparty allowlist, spend limits, and approval flow.
-The recipient must already be a saved counterparty wallet rail.
+server. Base and Base Sepolia are supported where enabled. Arc support is
+rolling out. Payments use the agent's normal send capability, counterparty
+allowlist, spend limits, and approval flow. The recipient must already be a
+saved counterparty wallet rail.
 
 The command accepts the same request-body, header, output, profile, and JSON
 flags as `x402`; run `mpp --help` for details. If approval is required, approve
@@ -333,6 +334,38 @@ To check whether a transfer completed, run `intents get <id>` with the returned
 intent id. A separate invocation without an explicit key is a new transfer, even
 when its inputs match an earlier command.
 
+### Sends that cross chains
+
+A `send` to a counterparty wallet on the other side of the Base and Arc lane is
+an ordinary `send`. When the account cannot pay it from its balance on the
+rail's network, the send crosses chains under the same intent: the first
+signature burns the amount toward the account's own address on the other chain,
+and `intents continue` signs the send to the counterparty once the funds land.
+One intent covers the whole payment, so policy, spend limits and any approval
+are evaluated once. Gas on both legs is paid by Catena.
+
+```bash
+npx @catena/cli send --rail cprl_... --amount 250.00 --method on-chain
+npx @catena/cli intents get int_...
+npx @catena/cli intents continue int_...
+```
+
+The result carries `crossChain` when the send crossed. Its `nextStep` says what
+to do: `wait` and poll `intents get`, `continue` and run `intents continue`,
+`done`, or `blocked` with `failureReason` set. A network the provider does not
+sponsor yet answers `wallet_send_action_not_yet_enabled` rather than charging
+the agent; on `intents continue` the intent stays at `continue`, so try again
+later.
+
+### `intents continue`
+
+Sign the second leg of a send that crossed chains, once `intents get` shows
+`crossChain.nextStep` as `continue`. Optional: `--idempotency-key`.
+
+```bash
+npx @catena/cli intents continue int_...
+```
+
 ### `accounts balance`
 
 Read an account balance through the policy engine.