@visa/cli 2.4.0-rc.10 → 2.4.0-rc.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/README.md +44 -24
  2. package/dist/cli.js +5 -5
  3. package/dist/mcp-server/index.js +4 -4
  4. package/package.json +1 -1
  5. package/server.json +2 -2
package/README.md CHANGED
@@ -46,36 +46,56 @@ visa-cli config hud enable
46
46
  ## CLI commands
47
47
 
48
48
  ```bash
49
- visa-cli login # GitHub OAuth — opens browser, stores session token
50
- visa-cli add-card # Enroll a Visa card via VGS secure form
51
- visa-cli status # Show auth state, enrolled cards, daily spend remaining
52
- visa-cli tokens create my-demo-app
53
- # Create an API token for an app or agent
54
- visa-cli history # Recent transactions with amounts and status
55
- visa-cli config hud enable
56
- # Enable the Claude Code statusLine HUD
57
- visa-cli config hud doctor
58
- # Diagnose HUD setup
59
- visa-cli config hud disable
60
- # Remove the Claude Code statusLine HUD
61
- visa-cli config hud enable claude
62
- # Explicitly register the Claude Code statusLine renderer
63
- visa-cli config hud enable shell
64
- # Opt-in shell prompt HUD for zsh/bash
65
- visa-cli config statusline
66
- # Renderer for statusLine integrations
49
+ visa-cli setup # First run: register MCP server, GitHub OAuth, enroll a card
50
+ visa-cli status # Show auth state, enrolled cards, wallet balance, daily spend remaining
51
+
52
+ # Cards
53
+ visa-cli cards add # Enroll a Visa card via the VGS secure form
54
+ visa-cli cards list # List enrolled cards
55
+ visa-cli cards default <id> # Set the default payment card
56
+ visa-cli cards remove <id> # Remove an enrolled card
57
+
58
+ # Balance & credits
59
+ visa-cli balance show # Prepaid balance + recent ledger entries
60
+ visa-cli balance topup --amount 5 # Top up balance from your default card (Touch ID)
61
+
62
+ # API tokens for apps and agents
63
+ visa-cli tokens create my-demo-app # Create an API token (prints the vk_... key once)
64
+ visa-cli tokens list # List API tokens
65
+ visa-cli tokens revoke <id> # Revoke an API token
66
+
67
+ # Run merchant tools
68
+ visa-cli generate image|video|music|speech|3d # Generate media with merchant tools
69
+ visa-cli run-llm # Chat-completion via an OpenRouter-backed LLM
70
+ visa-cli merchants list # Discover paid merchant tools
71
+
72
+ # Spend HUD & config
73
+ visa-cli config hud enable # Enable the Claude Code statusLine HUD (claude is the default surface)
74
+ visa-cli config hud enable shell # Opt-in shell prompt HUD for zsh/bash
75
+ visa-cli config hud disable # Remove the HUD
76
+ visa-cli config hud doctor # Diagnose HUD setup
77
+ visa-cli config statusline # Renderer for statusLine integrations
78
+ visa-cli config biometric off # Toggle Touch ID enforcement for remote payments
79
+
80
+ # Maintenance
81
+ visa-cli update # Update Visa CLI to the latest stable version
82
+ visa-cli uninstall # Remove the MCP server from an AI client
83
+ visa-cli feedback # Submit feedback about Visa CLI
84
+
67
85
  # MCP (stdio): run the bundled entrypoint (IDE configs use the same path — see getServerEntry in src/clients.ts)
68
86
  # node "$(npm root -g)/@visa/cli/dist/mcp-server/index.js"
69
87
  ```
70
88
 
89
+ Transaction history with amounts, merchants, and status is available through the `transaction_history` MCP tool (ask your assistant), or as a recent ledger via `visa-cli balance show`. There is no standalone `history` subcommand.
90
+
71
91
  ---
72
92
 
73
93
  ## Authentication
74
94
 
75
- Login is GitHub OAuth. Your session token is stored at `~/.visa-mcp/session-token`.
95
+ Login is GitHub OAuth and runs as part of `visa-cli setup`. Your session token is stored at `~/.visa-mcp/session-token`.
76
96
 
77
97
  ```bash
78
- visa-cli login # opens github.com/login/oauth/authorize in your browser
98
+ visa-cli setup # registers the MCP server, then opens github.com/login/oauth/authorize in your browser
79
99
  visa-cli status # verify you're logged in
80
100
  ```
81
101
 
@@ -83,10 +103,10 @@ visa-cli status # verify you're logged in
83
103
 
84
104
  ## Card enrollment
85
105
 
86
- Cards are tokenized via VGS — your raw card number never touches Visa servers. `add_card` opens a hosted VGS Collect form in your browser. You receive $1 in free credits on your first card enrollment.
106
+ Cards are tokenized via VGS — your raw card number never touches Visa servers. `visa-cli cards add` (or the `add_card` MCP tool) opens a hosted VGS Collect form in your browser. You receive $1 in free credits on your first card enrollment.
87
107
 
88
108
  ```bash
89
- visa-cli add-card
109
+ visa-cli cards add
90
110
  ```
91
111
 
92
112
  Multiple cards can be enrolled. The first becomes the default; you can switch defaults with `set_default_card` from within your assistant. To remove a card: `remove_card` (requires authentication).
@@ -107,7 +127,7 @@ Share your referral link (visible in `get_status`) and you both get **$2 in free
107
127
 
108
128
  Every paid tool call requires authentication. On macOS, this is Touch ID (or device password); on Windows and Linux, payments are server-verified with restricted spending limits. Your assistant will show you the amount and merchant before prompting. If you cancel, the payment is aborted — nothing is charged.
109
129
 
110
- Remote CLI/MCP servers can run ordinary paid tools under those server-enforced limits, but card-funded credit top-ups require local biometric attestation. Credits and the biometric preference are account-level: top up from any interactive Touch ID-capable CLI signed into the same account, optionally run `visa-cli biometric off` there for remote ordinary payments, then use that balance from the remote server. Credit top-ups still require local attestation even when biometric is off. For unattended server workloads, scoped API keys with daily caps are also supported.
130
+ Remote CLI/MCP servers can run ordinary paid tools under those server-enforced limits, but card-funded credit top-ups require local biometric attestation. Credits and the biometric preference are account-level: top up from any interactive Touch ID-capable CLI signed into the same account, optionally run `visa-cli config biometric off` there for remote ordinary payments, then use that balance from the remote server. Credit top-ups still require local attestation even when biometric is off. For unattended server workloads, scoped API keys with daily caps are also supported.
111
131
 
112
132
  You can set hard limits via the `update_spending_controls` tool, or check your current limits any time:
113
133
 
@@ -228,7 +248,7 @@ Paid calls then spend from that explicit approval window until the cap is used,
228
248
  **Touch ID prompt doesn't appear (macOS)**
229
249
  Make sure the MCP process (`node …/dist/mcp-server/index.js`) runs in a foreground TTY with access to the macOS security framework. Running inside some sandboxed environments may prevent Touch ID. On Windows and Linux, biometric prompts are not used for ordinary payments. Buying credits with an enrolled card currently requires local biometric attestation from the CLI; remote servers can spend account balance topped up from any interactive Touch ID-capable CLI signed into the same account.
230
250
 
231
- **"Not logged in" after `visa-cli login`**
251
+ **"Not logged in" after `visa-cli setup`**
232
252
  Restart the MCP server after logging in — your MCP client needs to reconnect to pick up the new session.
233
253
 
234
254
  **Card not showing in `get_cards`**