Skip to main content
skill CX Codex

qwencloud-payment — Claude Code skill: payments and setup

Check QwenCloud payment methods and spending limits, or open the card-binding page after confirmation. Useful for payment status and account payment settings.

Apache-2.0 391 installs ★ 44 updated 2026-09-21

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add QwenCloud/qwencloud-ai --skill qwencloud-payment -a claude-code
Open on GitHub

What qwencloud-payment does

The skill uses QwenCloud CLI to retrieve payment methods and the current spending limit. It treats a method as active only when its status is VALID, and reports the configured limit alongside current usage. CLI responses are parsed as JSON and presented as a readable summary.

You need QwenCloud CLI 1.3.0 or later, Node.js 18 or later, and an authenticated account. If authentication is needed, the skill follows a two-stage login flow. Billing commands require authentication.

Card binding requires explicit user approval. Once approved, the CLI opens the official card-binding page in a browser; it does not submit card details or make transactions in the conversation. Billing history, usage, and subscription-status questions belong to the qwencloud-usage skill.

What it helps with

  • check which payment methods are active
  • view the spending limit and current usage
  • open the card-binding page after user approval
  • retrieve payment status through QwenCloud CLI

Example prompts for the agent

  • Check which QwenCloud payment methods are active.
  • Show my spending limit and current usage.
  • Ask me for approval, then open the card-binding page.

How to install qwencloud-payment

1Skills CLI (Vercel)

npx skills add QwenCloud/qwencloud-ai --skill qwencloud-payment -a claude-code

2Manually: put the files in place

~/.claude/skills/qwencloud-payment/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/qwencloud-payment/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about qwencloud-payment

How do I install qwencloud-payment in Claude Code?

Run npx skills add QwenCloud/qwencloud-ai --skill qwencloud-payment -a claude-code. The skill file is at ~/.claude/skills/qwencloud-payment/SKILL.md.

What does qwencloud-payment do?

It checks payment-method status and spending-limit usage for QwenCloud. Card binding opens a browser page only after explicit approval.

What does qwencloud-payment need to run?

It requires QwenCloud CLI 1.3.0 or later, Node.js 18 or later, and account authentication.

Source text

SKILL.md · Apache-2.0
---
name: qwencloud-payment
description: "Manage payment methods, bind card, spending limit. TRIGGER when: user asks about payment methods, bind card, spending limit, payment status. DO NOT TRIGGER when: billing history, usage queries, subscription status (use qwencloud-usage), support tickets."
compatibility: "Requires QwenCloud CLI >= 1.3.0 and authentication. Cursor: auto-loaded. Claude Code: read SKILL.md before first use."
---

# QwenCloud Payment

Manage QwenCloud account payment method status, card binding, and spending limits.

## Prerequisites

- **QwenCloud CLI >= 1.3.0** must be installed. Verify with:

```bash
qwencloud version
```

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

1. `qwencloud auth status --format json` → `authenticated: true` → skip to commands
2. `qwencloud auth login --init-only --format json` → extract `verification_url` → open in browser
3. `qwencloud auth login --complete --format json` → poll until `success` event

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

```bash
qwencloud billing payment-method list --format json
```

**Response fields:**
- `items[]` — list of payment methods
- `items[].status` — only items with status `VALID` 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 `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:

1. **Show impact** — explain what the action will do (open a web page for card binding)
2. **Wait for explicit user confirmation** — return `confirmation_required` status if not confirmed
3. **Execute only after confirmation**

#### States

| State | Meaning |
|-------|---------|
| `confirmation_required` | Action pending user confirmation — do NOT execute |
| `confirmed` | User explicitly agreed — proceed with command |

#### Steps

1. User requests bind card
2. Agent presents: "This will open the official card-binding page in your browser. Proceed?"
3. If user confirms → execute the command
4. If user declines or does not respond → return `confirmation_required`, 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 `--format json`**, parse the structured response, then present a human-readable summary.

### How to present output

1. **Parse the JSON** and extract relevant data for the user's question
2. **Present a human-readable summary** — do not dump raw JSON
3. **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 `bind` 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 `qwencloud-usage` instead)
- ❌ Query subscription status (use `qwencloud-usage` instead)
- ❌ Retry login in a loop on auth failure

© QwenCloud · Apache-2.0 · QwenCloud/qwencloud-ai

Similar skills

All skills for Finance and business →

From the same set10

The whole set →
qwencloud-video-generation qwencloud-video-generation — a skill that generates and edits video with Wan models: text-to-video, image animation, frame transitions. Useful when the agent has to hand back a finished clip. CX Codex +1 1,800installs qwencloud-ops-auth qwencloud-ops-auth configures authentication for QwenCloud APIs, checks credentials, and resolves 401 errors. Useful when setting up DASHSCOPE_API_KEY or fixing access issues. CX Codex +1 1,800installs qwencloud-model-selector The qwencloud-model-selector skill recommends which Qwen model and parameters fit your task. Handy when you are unsure what is cheaper or what your key can actually reach. CX Codex +1 1,800installs qwencloud-text qwencloud-text is a Claude Code skill that sends text requests to QwenCloud models. It activates for text or code generation, chat, and function calls. CX Codex +1 1,800installs qwencloud-update-check qwencloud-update-check is a Claude Code skill that checks the qwencloud-ai pack for GitHub releases and warns when a newer version is available. CX Codex +1 1,800installs qwencloud-image-generation qwencloud-image-generation — a skill that generates and edits images with Wan and Claude Image models from inside your agent: text-to-image, style transfer, reference photos. CX Codex +1 1,800installs qwencloud-audio-tts qwencloud-audio-tts turns text into speech with Qwen TTS models: voiceovers, narration, audio output for apps. Runs in Claude, Codex, Cursor, Copilot, Gemini CLI and OpenCode. CX Codex +1 1,800installs qwencloud-usage qwencloud-usage — a skill for your QwenCloud account: login and logout, credit usage, billing, quotas, call logs and subscriptions. Useful when a request failed or you need to know what's left. CX Codex +1 1,700installs

Project sponsors

Companies that keep this analytics open