x402-pay has no --broadcast gate, unlike send/swap/withdraw

send/swap/withdraw all default to dry-run and require an explicit --broadcast flag before touching the chain (README's "Smart Defaults" table). x402-pay doesn't have that option at all — its own description says "auto-pays 402," and it funds the signer EOA and completes the facilitator payment in the same call, no preview step.

That's a real asymmetry in the same CLI: careful by default for value transfers, not for x402 payments specifically. Separately, once a payment completes, the JSON result (ok, status, walletAddress, signerAddress, funded, payment) only lives in stdout and whatever the host app's own logs retain — there's no way for someone outside that session to independently verify what was requested and paid without trusting it.

Worked example, applying a public spec (no changes asked of this repo): https://github.com/giskard09/polygon-action-ref-anchor

It derives action_ref — a content-addressed id from {agent_id, action_type, scope, timestamp} (JCS RFC 8785 + SHA-256, argentum-core/action-ref-v1) — for a synthetic x402-pay call shaped exactly per this repo's own command options and printed result shape, then anchors it permissionlessly on Base mainnet (tx in the repo, independently verifiable, no owner/roles on the registry).

To be explicit about what this is: a worked example against your public source, not a claim that polygon-agent-cli does or should implement this, and not an ask for any change here.

The issue names no repository files, tests, or entry points; begin by clarifying whether a repository change is intended. The text explicitly says the worked example requests no change, so there is no payload-defined implementation target or completion test.