Service discovery and data retrieval via CLI. Find, search, and request only — no purchase/buy flows.
Trigger when the user message combines RedotPay with a discovery or query action:
use redotpay to find/search/look up/request …request/find/search/look up … by/via redotpay用 redotpay 找/查/搜 …Trigger examples:
> "use redotpay to find running shoes under $150 with free shipping"
> "use redotpay to search flights SFO to Tokyo"
> "look up AAPL stock data by redotpay"
> "request weather data for NYC via redotpay"
RedotPay services are organized into these categories. Use them to guide keyword selection during service discovery:
Image, video, music, audio, TTS, transcription.
Chat completion, embeddings, inference.
Search, extraction, on-chain data, travel/maps-style lookups (per catalog).
Buy/order/purchase flows exposed via MPP (lottery, domains, mail, etc.).
> Note: This skill handles discovery and data retrieval across all buckets. Agent-commerce purchase flows are excluded — only listing/searching/looking up commerce services is allowed.
Steps A, B, C do not require login. Login is only needed at Step D before making a paid request.
redotpay wallet services list --search "<keywords>"
Extract 1–3 core keywords from the user's request. Match against the task buckets above:
| User Request | Bucket | Search Terms |
|---|---|---|
| ------------- | -------- | ------------- |
| Find running shoes under $150 | Data APIs | --search "shoes product search" |
| Search flights SFO→JFK | Data APIs | --search "flight travel" |
| Look up AAPL stock | Data APIs | --search "stock market finance" |
| Generate an image of a cat | Generate Media | --search "image generation" |
| Transcribe this audio file | Generate Media | --search "transcription audio" |
| Chat with GPT about history | Model APIs | --search "chat completion llm" |
If results are empty, try broader keywords. Output is JSON — focus on id, name, description, serviceUrl.
redotpay wallet services <service_id>
Get endpoint list, parameter schema, and pricing. Always inspect before calling.
After inspecting the service and mapping user constraints to parameters, before any request:
Login is only required at this step.
First, check login status:
redotpay wallet whoami
Then call the service:
redotpay request [flags] <endpoint_url>
Only execute after Step C confirmation and login check.
redotpay wallet services list [--search <q>] # Search services
redotpay wallet services <id> # Inspect service details
redotpay request [curl-flags] <url> # Send request
redotpay wallet whoami # Check login status
redotpay wallet login # Log in
redotpay wallet logout # Log out
redotpay --help # Help
redotpay request --help # Request help
redotpay guide # Usage guide
wallet login) does not require confirmation for a specific charge.redotpay request must:Set a cap via --max-spend or REDOTPAY_CLI_MAX_SPEND for any chargeable request. If the user refuses a cap, do not proceed.
Login is only required at Step D. Do not run whoami or login during Steps A, B, or C.
Only triggered at Step D when whoami returns "not logged in".
redotpay wallet login
login_qr_png_path and user_coderead whoami to confirm → continue-v sparingly (stderr may leak payment metadata)read tool on the PNG path, not !... markdown (blocked by browser security)For first-time setup only.
curl -fsSL "https://raw.githubusercontent.com/redotpay/redotpay-cli/v0.1.0/install.sh" -o redotpay-install.sh
shasum -a 256 -c SHA256SUMS --ignore-missing
bash redotpay-install.sh
redotpay --version
共 1 个版本