@usenaive-sdk/vetta-cli 0.1.0
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 +66 -0
- package/dist/index.js +25651 -0
- package/package.json +36 -0
package/README.md
ADDED
|
@@ -0,0 +1,66 @@
|
|
|
1
|
+
# @usenaive-sdk/vetta-cli
|
|
2
|
+
|
|
3
|
+
The `vetta` command line — drive the whole Vetta API from a terminal or a script: agents, sessions,
|
|
4
|
+
computers, skills, files, identities, vaults, comms, deployments, webhooks and credits.
|
|
5
|
+
|
|
6
|
+
It is built on [`@usenaive-sdk/vetta`](https://www.npmjs.com/package/@usenaive-sdk/vetta), the same typed
|
|
7
|
+
client the dashboard uses, so the CLI and the API never drift apart.
|
|
8
|
+
|
|
9
|
+
## Install
|
|
10
|
+
|
|
11
|
+
```bash
|
|
12
|
+
npm i -g @usenaive-sdk/vetta-cli
|
|
13
|
+
```
|
|
14
|
+
|
|
15
|
+
## First run
|
|
16
|
+
|
|
17
|
+
```bash
|
|
18
|
+
vetta login --api-key sk_… # or: vetta login --email … --password …
|
|
19
|
+
vetta whoami
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
Credentials are stored on a named profile, so several organizations can be driven from one machine
|
|
23
|
+
with `--profile`.
|
|
24
|
+
|
|
25
|
+
## Shape
|
|
26
|
+
|
|
27
|
+
```
|
|
28
|
+
vetta <group> <command> [flags]
|
|
29
|
+
```
|
|
30
|
+
|
|
31
|
+
Groups: `agent` `audit` `auth` `computer` `connections` `credits` `deploy` `domain` `email` `file`
|
|
32
|
+
`identity` `keys` `login` `logout` `models` `org` `phone` `run` `session` `skill` `vault` `webhook`
|
|
33
|
+
`whoami`.
|
|
34
|
+
|
|
35
|
+
`vetta <group> --help` lists a group's commands.
|
|
36
|
+
|
|
37
|
+
Global flags: `--json` (the default) · `--human` · `--profile <name>` · `--api-key <key>` ·
|
|
38
|
+
`--org <org_id>` · `--api-base-url <url>`
|
|
39
|
+
|
|
40
|
+
## Example
|
|
41
|
+
|
|
42
|
+
```bash
|
|
43
|
+
# Create an agent, run one task, and read what it cost.
|
|
44
|
+
vetta agent create \
|
|
45
|
+
--name summariser \
|
|
46
|
+
--model openai/gpt-oss-120b \
|
|
47
|
+
--system "Answer in one sentence." \
|
|
48
|
+
--budget-usd 2.00 --max-task-usd 0.10 --budget-period day
|
|
49
|
+
|
|
50
|
+
vetta session run --agent agt_… --message "What is 17 times 3?"
|
|
51
|
+
vetta session get ses_… --human
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
|
|
55
|
+
## Output
|
|
56
|
+
|
|
57
|
+
`--json` is the default because the CLI is meant to be piped. Every command writes a single JSON
|
|
58
|
+
document to stdout and nothing else; diagnostics go to stderr. `--human` switches to a readable
|
|
59
|
+
table when you are driving it yourself.
|
|
60
|
+
|
|
61
|
+
Exit codes follow the API's error taxonomy, so a script can branch on the failure rather than
|
|
62
|
+
parsing a message.
|
|
63
|
+
|
|
64
|
+
## License
|
|
65
|
+
|
|
66
|
+
MIT
|