Single-user backend example. Keep this host private. Production must attach every operation to the platform's verified login identity; do not reuse this anonymous demo session model. The generic multi-user host uses the same tools with trusted task and user bindings.
Open official wallet / spending authorization page
Inspect tools/list first. Paste exact contract arguments. Preview creation requires a stable client_request_id. Execute accepts only the original preview_id. This button can spend within valid user authorization; it does not add a per-payment wallet confirmation requirement.
For an interrupted original execute, enter its preview ID below. These explicit recovery actions first read the authority's startup state; unknown, missing or legacy records do not grant permission to send again. Resume can spend within the original authorization. Terminate only closes a never-admitted original and cannot cancel an accepted payment.
After interruption repeat the exact request to query its original journal record, or use original preview / purchase / operation query tools. Never generate replacement IDs to retry payments. If OAuth status is refreshing after interruption, explicitly Revoke then Connect; never replay the old refresh token. For interrupted exchanging, Connect starts a fresh authorization with new state/PKCE. Revoke tokens does not cancel an accepted payment or revoke on-chain allowance.
Not connected.