@visa/cli 4.1.0-rc.214 → 4.1.0-rc.216
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.
- package/README.md +17 -8
- package/dist/cli.js +367 -365
- package/dist/mcp-server/index.js +189 -189
- package/native/bin/win32-x64/visa-keychain-win.exe +0 -0
- package/package.json +1 -1
- package/server.json +2 -2
package/README.md
CHANGED
|
@@ -9,9 +9,11 @@ public key to the TAP directory by default; owners can durably remove it with
|
|
|
9
9
|
|
|
10
10
|
The product flow has three explicit parts:
|
|
11
11
|
|
|
12
|
-
1. **Identity** — `
|
|
13
|
-
review
|
|
14
|
-
stays on the
|
|
12
|
+
1. **Identity** — `setup_start` (or `visa setup start`) opens ONE browser
|
|
13
|
+
review that covers the exact runtime, its public-key fingerprint, and every
|
|
14
|
+
requested rail in a single owner approval. The private key stays on the
|
|
15
|
+
runtime device. (`enroll_agent` / `visa agent enroll` remains the
|
|
16
|
+
identity-only legacy door.)
|
|
15
17
|
2. **Capabilities** — payment methods, spend grants, email and directory
|
|
16
18
|
bindings are configured separately, each with its own human-visible terms.
|
|
17
19
|
3. **Use** — when a separately provisioned capability exists, the wallet and
|
|
@@ -82,13 +84,20 @@ Visa sidebands no longer pollute business JSON. Clients receive keys such as `io
|
|
|
82
84
|
|
|
83
85
|
## Pair an agent identity
|
|
84
86
|
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
|
|
88
|
-
`
|
|
87
|
+
For a NEW agent, call **`setup_start`** with the name the human chooses: one
|
|
88
|
+
resumable setup covers identity plus every requested rail in a single owner
|
|
89
|
+
approval on one review page, and `setup_status` / `setup_resume` carry it
|
|
90
|
+
across restarts. From a terminal, `visa setup start "<name>"` begins the same
|
|
91
|
+
operation.
|
|
92
|
+
|
|
93
|
+
The identity-only legacy door remains for existing integrations: `enroll_agent`
|
|
94
|
+
with `{"action":"start"}` creates the runtime's Ed25519 key locally, verifies
|
|
95
|
+
the terminal/browser channel, and opens the identity-only review; after the
|
|
96
|
+
human approves, `{"action":"claim"}` activates and durably stores the identity.
|
|
89
97
|
|
|
90
98
|
```bash
|
|
91
|
-
visa
|
|
99
|
+
visa setup start "Name" # one review page, one approval, every rail
|
|
100
|
+
visa agent enroll # legacy identity-only review page
|
|
92
101
|
visa agent enroll-claim # resumes delivery/activation after approval
|
|
93
102
|
visa agent list
|
|
94
103
|
visa agent show <agent-id>
|