redotpay-payment

When the user says to use redotpay, prefer redotpay CLI commands and keep behavior grounded in redotpay --help, redotpay request --help, and redotpay guide.

Like Tempo’s model, RedotPay is for discovering services (redotpay wallet services …) and calling HTTP endpoints with automatic payment handling (redotpay request …), including paid APIs and external data. Use this skill when the user wants RedotPay for “find a service / hit an API / pay as you go” (for example StableEnrich, StableStudio, StableSocial when using redotpay). If they explicitly ask for Tempo, use the Tempo skill — do not run redotpay in place of Tempo unless they switch to RedotPay.

This skill is for agent-paid HTTP and 402/x402 handling with RedotPay semantics (Tempo may appear only as a payment method inside some 402 flows; see below), not a merchant-specific checkout script.

Before you install

Install this skill only if you want the agent to use RedotPay for paid HTTP access. Before use: set a spending cap (see Agent UX before charging), require explicit user confirmation before each paid redotpay request and before any 402 / MPP pay retry, verify the installer (Setup Step 1), and treat the RedotPay login session and local wallet files as sensitive (see Safety).

Setup

Run these steps in order. Do not skip install when the binary is missing.

Step 1 — Install (redotpay-cli)

Use a pinned release tag (not the moving main branch). The human should open and review the script before running it.

Example for tag v0.1.0 (update the tag in this skill when you bump the supported CLI release):

curl -fsSL "https://raw.githubusercontent.com/redotpay/redotpay-cli/v0.1.0/install.sh" -o redotpay-install.sh
# Review redotpay-install.sh, then:
bash redotpay-install.sh

• Confirm the tag matches the intended redotpay-cli Releases entry. If the release ships SHA256SUMS (or published digests), download it and verify redotpay-install.sh with shasum -a 256 (or sha256sum) before bash.
• After install, open a new shell or reload your shell profile if the shell still cannot find redotpay.

Step 2 — Verify binary: redotpay --help

• If the command is not available, finish Step 1 (install) and ensure your shell can resolve redotpay, then retry.

Step 3 — Login when needed: redotpay wallet login

OAuth2 device flow. Whenever login is required (after whoami shows no session, or before retrying a session-gated request), the agent must:

1. Run redotpay wallet login. Default: one JSON object on stdout (--human for legacy multi-line MEDIA: / VERIFICATION_CODE: output).
2. Always tell the user in plain language: open the RedotPay app, use it to scan the QR code below to sign in and authorize this CLI session. Do not skip this reminder.
3. Parse stdout JSON. Fields:

4. Show the QR: embed the PNG in Markdown, e.g. ![RedotPay login QR](file:///…) with a file:// URL (three slashes after file:) built from login_qr_png_path.
5. Show user_code next to the image. Treat stderr as human hints only (not the JSON payload). Never paste OAuth tokens. Treat local wallet files as sensitive after login.

Step 4 — Confirm readiness: redotpay wallet whoami

• Source of truth for logged-in vs not. If not signed in or session expired, repeat Step 3, then whoami until authenticated (field meanings: CLI output, redotpay guide).

Setup rules

• Do not expose OAuth tokens, key material, or sensitive config.
• Prefer a limited-funds wallet or account for CLI use; OAuth grants this environment payment-capable access until expiry or logout / dashboard revocation.
• When RedotPay access is no longer needed, run redotpay wallet logout (and revoke device keys in the dashboard if your org requires it).

After setup

Provide:

• RedotPay readiness only from redotpay wallet whoami.
• Whether the task is MPP discovery, direct request, or 402 retry.
• If login is required, follow Setup Step 3 only (QR + RedotPay app scan reminder + user_code; no token dumps).

Use services and requests

redotpay wallet services list
redotpay wallet services list --search \x3Cquery>
redotpay wallet services \x3Cservice_id>
redotpay request [curl-like flags] \x3CURL>

• Use redotpay wallet services for mpp.dev-style public registry discovery (id, name, serviceUrl, etc.).
• Use redotpay request as the curl-like HTTP entrypoint, including paid endpoints that may return 402. For any call that may charge the wallet, treat --max-spend or REDOTPAY_CLI_MAX_SPEND as the default guardrail unless the user has explicitly accepted uncapped risk for that request (see Agent UX before charging and redotpay request --help).

Preflight (mandatory for redotpay request)

Before any redotpay request, run redotpay wallet whoami first (= Setup Step 4).

If not logged in or session invalid: do not call the URL yet or blindly retry. Pause, run Setup Step 3 end-to-end (including RedotPay app QR scan instructions), wait until the user finishes authorization, then Step 4 until whoami is good; then run or retry redotpay request.

redotpay wallet services … may work without a session in some setups; paid or session-gated calls still require the rule above.

Request examples

redotpay request https://example.com/resource
redotpay request -X POST https://example.com/api -H 'Content-Type: application/json' --json '{"a":1}'

HTTP 402 behavior (redotpay request)

Many paid flows return 402 Payment Required. redotpay request supports behaviors described in CLI help, including:

• WWW-Authenticate: Payment: call RedotPay agentic MPP pay endpoint, then retry original resource URL.
• Legacy x402 JSON flows: support for accept headers and spend controls (--max-spend, REDOTPAY_CLI_MAX_SPEND).

Spend guardrails (agent default): treat --max-spend / REDOTPAY_CLI_MAX_SPEND as mandatory for paid paths unless the user clearly waives a cap for that specific attempt. Do not treat them as optional extras — they bound automatic pay + 402 retry behavior (see redotpay request --help).

• Optional on-chain receipt wait after pay (--no-wait-tx-confirm, REDOTPAY_CLI_AGENTIC_MPP_*).

Auth gate: CLI says a logged-in session is required

If 402 and the CLI says WWW-Authenticate: Payment needs a logged-in session (or points at redotpay wallet login), do not only report a blocker. Run Setup Step 3 → Step 4 (same as Preflight: QR, RedotPay app scan reminder, whoami until OK), then retry the same redotpay request (then normal 402 / MPP per CLI help). Never paste tokens.

Before any retry that can trigger agentic MPP pay, obtain fresh explicit user confirmation for that attempt’s amount/purpose (in addition to login), and keep --max-spend / REDOTPAY_CLI_MAX_SPEND aligned with what the user approved.

If a 402 lists Tempo as a payment method

Do not assume you must switch to tempo or mppx.

In this model, redotpay request can still complete payment when Tempo appears in offered methods, using RedotPay OAuth session (redotpay wallet login) plus normal redotpay request semantics.

For edge cases, consult redotpay guide and CLI help before guessing.

Capability boundaries

Use these as hard boundaries when deciding tools:

• Wallet management stubs in redotpay: wallet keys|fund|transfer|sessions|mpp-sign.
• Service registration stubs in redotpay: add, list, update, remove (unless your build explicitly enables them).
• For true Tempo wallet-management flows, use Tempo tooling; this does not change RedotPay 402 handling described above.

Minimal command map

redotpay --help
redotpay request --help
redotpay guide
redotpay info
redotpay wallet login | logout | whoami
redotpay wallet services list [--search \x3Cquery>]
redotpay wallet services \x3Cservice_id>
redotpay request [curl-like flags] \x3CURL>

Environment variables (OAuth home, MPP pay, RPC wait, x402 budget, etc.) are listed in redotpay --help and redotpay request --help; treat the installed CLI as authoritative.

Agent UX before charging

1. State amount, currency, and purpose when known.
2. Consent vs login: you may run redotpay wallet login as soon as whoami shows no session (identity only). That is not consent for a specific charge.
3. Mandatory spend cap (default): for any redotpay request that may spend funds (including unknown 402 outcomes on paid endpoints), include a user-approved ceiling via --max-spend or REDOTPAY_CLI_MAX_SPEND. If the user refuses a cap, do not run the paid request unless they explicitly accept uncapped spend for that specific call in the conversation; otherwise stop and ask again.
4. Paid request + 402 / MPP retry: get explicit user confirmation immediately before (a) the first paid redotpay request you send, and again (b) before any 402-handling path that can invoke agentic MPP pay or retry after pay — each attempt needs clear approval of amount/currency/purpose (not a one-time blanket OK).
5. Preflight: whoami before every redotpay request; if no session → Setup Step 3 (Markdown QR + tell the user to open the RedotPay app and scan to authorize) → Step 4 → then request.
6. Never paste OAuth tokens, raw wallet payloads, or full credential files into chat.

Safety

• Never request, print, or store OAuth tokens, API keys, or signing material in chat.
• Treat local RedotPay wallet config as sensitive; do not dump credential stores or full config.
• Use verbose mode (-v) sparingly because stderr may expose URL/payment metadata.
• Session authority: a completed device login gives this machine a payment-capable session until logout/expiry — use limited funds, keep disk backups private, and redotpay wallet logout when the agent no longer needs wallet access.