QwenCloud Payment
Manage QwenCloud account payment method status, card binding, and spending limits.
Prerequisites
- QwenCloud CLI >= 1.3.0 must be installed. Verify with:
If not installed, run:
bash
npm install -g @qwencloud/qwencloud-cli
Node.js >= 18 required.
- All billing commands require authentication. See Authentication Flow below.
Authentication Flow (for Agents)
The CLI auto-detects non-TTY environments and degrades safely.
TL;DR — 3-step auth path
qwencloud auth status --format json
qwencloud auth login --init-only --format json
qwencloud auth login --complete --format json
If
on step 1, proceed directly to payment commands.
For full details on the two-phase login flow (init-only → complete), refer to the
skill or
skill documentation.
Payment Status Commands
Payment Method Status
bash
qwencloud billing payment-method list --format json
Response fields:
- — list of payment methods
- — only items with status are considered active
Present the count of valid payment methods and their types.
Spending Limit
Query or display the current spending limit configuration.
bash
qwencloud billing limit --format json
Returns the configured spending limit and current consumption against it. When status is
, inform the user that no spending limit is currently configured.
Number formatting: Use K = 1000, M = 1000000 when displaying large values (e.g., $5K, $1.2M).
Bind Card
This command opens the official web console page. It does NOT perform transactions within the conversation.
Confirmation Flow
Before executing bind-card, the agent MUST:
- Show impact — explain what the action will do (open a web page for card binding)
- Wait for explicit user confirmation — return status if not confirmed
- Execute only after confirmation
States
| State | Meaning |
|---|
| Action pending user confirmation — do NOT execute |
| User explicitly agreed — proceed with command |
Steps
- User requests bind card
- Agent presents: "This will open the official card-binding page in your browser. Proceed?"
- If user confirms → execute the command
- If user declines or does not respond → return , take no action
Execute
bash
qwencloud billing payment-method bind --format json
Opens the official card-binding page in the user's browser. No card data is submitted via CLI.
Output and Agent Display Rules
CLI commands return JSON by default in agent/pipe environments.
Always pass , parse the structured response, then present a human-readable summary.
How to present output
- Parse the JSON and extract relevant data for the user's question
- Present a human-readable summary — do not dump raw JSON
- Add analysis AFTER the summary — clearly separated with
Error Handling
- Auth failure: Return the original CLI error message. Do NOT retry login in a loop.
- After successful login: Retry the failed command exactly once.
- Network error: Report the error and suggest the user check connectivity.
- Unknown error: Return the raw CLI stderr output for debugging.
Result Status
| Status | When |
|---|
| Command executed and full data returned |
| Command executed (exit 0) but some expected fields are missing or — e.g., returns items but a field is , or returns with some fields absent. Present available data and note that the user should verify details in the web console |
| Command executed but no data (e.g., no payment methods bound) |
| Bind-card action awaiting user confirmation |
| Command failed — include error details |
NEVER
- ❌ Execute without explicit user confirmation
- ❌ Perform actual card submission or transactions in the conversation
- ❌ Judge payment method "insufficient" without explicit criteria
- ❌ Handle support tickets (out of scope)
- ❌ Query billing history or usage (use instead)
- ❌ Query subscription status (use instead)
- ❌ Retry login in a loop on auth failure