How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/qwencloud/qwencloud-ai --skill qwencloud-paymentBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
QwenCloud Payment
Manage QwenCloud account payment method status, card binding, and spending limits.
Prerequisites
- QwenCloud CLI >= 1.3.0 must be installed. Verify with:
qwencloud versionIf not installed, run:
npm install -g @qwencloud/qwencloud-cliNode.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→authenticated: true→ skip to commandsqwencloud auth login --init-only --format json→ extractverification_url→ open in browserqwencloud auth login --complete --format json→ poll untilsuccessevent
If authenticated: true on step 1, proceed directly to payment commands.
For full details on the two-phase login flow (init-only → complete), refer to the qwencloud-usage skill or qwencloud-ops-auth skill documentation.
Payment Status Commands
Payment Method Status
qwencloud billing payment-method list --format jsonResponse fields:
items[]— list of payment methodsitems[].status— only items with statusVALIDare considered active
Present the count of valid payment methods and their types.
Spending Limit
Query or display the current spending limit configuration.
qwencloud billing limit --format jsonReturns the configured spending limit and current consumption against it. When status is INACTIVE, 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
confirmation_requiredstatus if not confirmed - Execute only after confirmation
States
| State | Meaning |
|---|---|
confirmation_required | Action pending user confirmation — do NOT execute |
confirmed | 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
confirmation_required, take no action
Execute
qwencloud billing payment-method bind --format jsonOpens 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 `--format json`, 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 |
|---|---|
success | Command executed and full data returned |
partial | Command executed (exit 0) but some expected fields are missing or null — e.g., payment-method list returns items but a field is null, or billing limit returns INACTIVE with some fields absent. Present available data and note that the user should verify details in the web console |
empty | Command executed but no data (e.g., no payment methods bound) |
confirmation_required | Bind-card action awaiting user confirmation |
error | Command failed — include error details |
NEVER
- ❌ Execute
bindwithout 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
qwencloud-usageinstead) - ❌ Query subscription status (use
qwencloud-usageinstead) - ❌ Retry login in a loop on auth failure



