@zanfia/cli 0.10.0 → 0.21.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.
Files changed (3) hide show
  1. package/README.md +16 -0
  2. package/dist/index.js +1961 -244
  3. package/package.json +38 -38
package/README.md CHANGED
@@ -36,6 +36,22 @@ zanfia emails test purchase-confirmation --lang en # queued to YOUR own addres
36
36
  Raw HTTP: `GET|PATCH /email-templates`, `POST /email-templates/{key}/test-sends`. Full reference for every
37
37
  command group: `.claude/skills/zanfia-cli/SKILL.md`.
38
38
 
39
+ ## Community member keys (read-only option)
40
+
41
+ A member key acts as a creator's customer in their communities (Community API + the member MCP
42
+ tools), never in a workspace. Three ways to get one:
43
+
44
+ ```bash
45
+ zanfia login --address https://<creator-platform-url> [--read-only] # browser consent on that platform
46
+ zanfia join <handle> [--read-only] # public community, emailed code
47
+ zanfia auth set-key --api-url <api-community-url> <key> # key from the platform's settings
48
+ ```
49
+
50
+ `--read-only` (or „Tylko odczyt” when generating a key under **Settings → AI agents** on the
51
+ platform) grants `communities:read` only: the key reads and summarizes, and
52
+ every write (post, comment, chat, ticket) gets a 403 / a refused MCP tool. `zanfia auth status` and
53
+ `zanfia whoami` show the scope, e.g. `scope : communities:read (read-only)`.
54
+
39
55
  ## Auth resolution order
40
56
 
41
57
  1. `--api-key` flag