@duvoai/cli 1.88.0 → 1.90.1

package/guides/duvo.md

@@ -119,16 +119,24 @@ with `duvo pulse send-message <id> --message "…"` (creator only).
 ## Escape hatch — `duvo api`
 
 Any public endpoint is reachable before it has a dedicated command, modelled
-on `gh api`:
+on `gh api`'s short flags. `duvo api` sends the path through verbatim —
+unlike the high-level commands, it does not resolve `--team`/`DUVO_TEAM_ID`/
+the profile default for you, so spell out whatever the endpoint's own path
+is. Route shapes vary per resource — some collections are team-scoped, some
+are flat (`/v2/artifacts`), and some by-ID routes stay team-scoped — so take
+the exact path from `GET /v2/documentation/json` (the raw OpenAPI document —
+`/v2/documentation` itself is the Swagger UI HTML) rather than inferring it:
 
 ```bash
-duvo api GET /v1/agents -F limit=20 -F offset=0
-duvo api POST /v1/agents -f name="Ops bot"
-cat body.json | duvo api POST /v1/agents --input -
+duvo api GET "/v2/teams/$TEAM_ID/agents" -F limit=20 -F offset=0
+duvo api POST "/v2/teams/$TEAM_ID/agents" -f name="Ops bot"
+cat body.json | duvo api POST "/v2/teams/$TEAM_ID/agents" --input -
 ```
 
 `-f key=value` always sends a string; `-F key=value` parses booleans, numbers,
-JSON null, or `@file`. Run `duvo api --help` for the full flag set.
+JSON null, or `@file`. Prefer the short spellings: the long aliases are the
+reverse of `gh api`'s (`--field` is the string form here, `--raw-field` the
+typed one). Run `duvo api --help` for the full flag set.
 
 ## Discoverability
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@duvoai/cli",
-  "version": "1.88.0",
+  "version": "1.90.1",
   "description": "Command-line interface for the Duvo public API",
   "bin": {
     "duvo": "./dist/bin/duvo.js"