@visa/cli 4.1.0-rc.62 → 4.1.0-rc.63

package/dist/skills/pair-visa-agent/SKILL.md

@@ -6,7 +6,7 @@ allowed-tools: Bash(visa:*) Bash(visa-cli:*) Bash(node:*) Bash(npm:*) Bash(npx:*
 metadata:
   author: visa
   homepage: https://visacli.sh/agents
-  version: '0.6.5'
+  version: '0.6.6'
   # OpenClaw-namespaced extension (agentskills.io keeps `metadata` free-form, so
   # non-standard runtime config lives here — `user-invocable` is not a standard
   # top-level field). OpenClaw auto-installs `install[]` when `requires.bins` are
@@ -167,10 +167,13 @@ possible (re-pairing an existing identity silently dead-ends). Do this instead:
 2. **Report status honestly — "connected" is five separate things**, not one. Never
    imply the agent can spend just because it's connected:
    - **Identity** — connected (`.visa` name bound to _this user's_ account). ✓ once `already_connected`.
-   - **Spending** — a _separate human approval_. If `keyBound`/spend isn't set, say:
-     "To let me pay, approve spending in your **account settings → agent card → Spend**."
-     You **cannot** self-grant it; never tell the user to run `visa agent add-rail`
-     (it refuses identity-only agents).
+   - **Spending** — a _separate human approval_, and there are two rails. For the
+     Turnkey **wallet** (x402 stablecoin), the owner approves a wallet grant in
+     **account settings → agent wallet → Spend** (see "What you can do once paired"
+     below). For **card** checkout, the owner approves in **account settings → agent
+     card → Spend**. You **cannot** self-grant either; never tell the user to run
+     `visa agent add-rail` (it refuses identity-only agents), and never self-mint a
+     wallet with `wallet_init` on mainnet — it throws until the owner's delegation lands.
    - **Mesh (`.visa` messaging)** — with `SUBWAY_MESH=visa`, a returning device now
      registers on `pair`; if `meshRegistered` is false, `visa register <name>` joins it.
    - **Trusted (TAP)** — follows spend/provisioning; don't promise it before then.
@@ -178,8 +181,36 @@ possible (re-pairing an existing identity silently dead-ends). Do this instead:
    signed in with (their email); the wallet + spend limits are theirs. Speak in terms
    of "your agent / your account / the limits you approved," never a shared identity.
 
-The paid wallet keeps working regardless of the account's spend flag — see "What you
-can do once paired." Missing **spend** blocks _checkout mandates_, not local x402 pay.
+Missing **spend** blocks _checkout mandates_, not a delegated x402 wallet — but that
+wallet must first be acquired by owner approval (below); it is never self-minted.
+
+## What you can do once paired — acquiring a wallet to spend
+
+Pairing binds **identity only**. To let this agent pay via the Turnkey x402
+(stablecoin) wallet, the wallet must be **delegated by the human owner** — the runtime
+never self-mints it. On mainnet (production) `wallet_init` throws
+`WalletCredentialRequiredError` until that delegation lands, so do NOT call it as a
+setup step. Follow this sequence:
+
+- [ ] **Pair** the identity (the flow above). Identity only — no wallet yet.
+- [ ] **Resolve the next step** with `setup_agent` (`{"rail":"wallet"}`), or drive the
+      raw `visa agent grant-wallet <agentId>` ceremony. `setup_agent` reports
+      `needs_wallet` and points at the owner-approval grant — it does not tell you to
+      self-mint.
+- [ ] **Owner approves the wallet.** The human runs / confirms the wallet grant and
+      approves it in the account UI (**account settings → agent wallet → Spend**),
+      confirming caps and passkey. That approval registers the delegated signer + caps
+      and writes the delegated Turnkey credential (`turnkey.json`) to this runtime.
+      You cannot approve on their behalf.
+- [ ] **Confirm the real wallet** with `wallet_status` (or `visa wallet show`). Only a
+      provisioned/delegated credential — not the served tool list — means the wallet is
+      usable; `agent_capabilities.wallet.available` reflects this.
+- [ ] **Spend** with `wallet_pay` (x402), enforced by the owner-approved local policy
+      caps. Never raise a human-approved limit yourself.
+
+Card checkout is a separate upgrade on top of this Turnkey-only base — approve a card
+in **account settings → agent card → Spend**, then `start_card_mandate` / `pay_merchant`
+draw against it. Neither rail is enabled by pairing.
 
 ## Core flow
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@visa/cli",
-  "version": "4.1.0-rc.62",
+  "version": "4.1.0-rc.63",
   "description": "Visa CLI runtime for stable agent identity and separately authorized payment capabilities",
   "bin": {
     "visa-cli": "./bin/visa-cli.js",

package/server.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
   "name": "io.github.visa-crypto-labs/visa-cli",
-  "version": "4.1.0-rc.62",
+  "version": "4.1.0-rc.63",
   "title": "Visa CLI",
   "description": "Pair a human-approved agent identity, configure payment capabilities separately, and discover and pay x402 services from your AI coding assistant.",
   "websiteUrl": "https://github.com/Visa-Crypto-Labs/Visa-mono/tree/main/packages/cli#readme",
@@ -9,7 +9,7 @@
     {
       "registryType": "npm",
       "identifier": "@visa/cli",
-      "version": "4.1.0-rc.62",
+      "version": "4.1.0-rc.63",
       "transport": {
         "type": "stdio"
       },