@sendforai/claude-plugin 0.1.0 → 0.1.2

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.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "sendforai",
3
- "version": "0.1.0",
3
+ "version": "0.1.2",
4
4
  "description": "Transactional and broadcast email at cost. Adds the SendForAI skill and the hosted MCP server.",
5
5
  "author": {
6
6
  "name": "SendForAI",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sendforai/claude-plugin",
3
- "version": "0.1.0",
3
+ "version": "0.1.2",
4
4
  "description": "Claude Code plugin for SendForAI: the set-up-and-send email skill plus the SendForAI MCP server.",
5
5
  "keywords": [
6
6
  "claude-code",
@@ -20,5 +20,10 @@
20
20
  ".mcp.json",
21
21
  "skills",
22
22
  "README.md"
23
- ]
23
+ ],
24
+ "repository": {
25
+ "type": "git",
26
+ "url": "git+https://github.com/sendforai/sendforai.git",
27
+ "directory": "packages/claude-plugin"
28
+ }
24
29
  }
@@ -23,10 +23,11 @@ Use the CLI (`npx sendforai`, prints JSON, never prompts), the Node SDK (`@sendf
23
23
  - Otherwise run `npx sendforai domains status example.com` (after `init` or `domains add`) and give the user the exact records to add at their DNS host. Do not guess records.
24
24
  - From a sandbox identity, the real domain is added by delegation; `dns setup --domain` and `domains add` both handle it and keep the same account.
25
25
  4. **Check cost before sending for real.** `--dry-run` (API: `"dry_run": true`) returns cost, capacity and lint warnings without sending. Always pass `--max-cost` (API: `max_cost_usd`) on real sends so a mistake cannot overspend.
26
- 5. **Hand money to the human.** Sending to anyone outside the account's own domains needs prepaid credit. On `402 balance_required`, run `npx sendforai topup --amount 10` and give the user the `checkout_url`. Do not try to pay it yourself. Raising the monthly budget works the same way (`approval_url`).
26
+ 5. **Hand money to the human.** Sending to anyone outside the account's own domains needs prepaid credit (from $10). Before the first real send, check `npx sendforai account`: if `next_action` is `add_credit`, run `npx sendforai topup` and give the user the `checkout_url`. A dry run also says so: when `funding.ok` is false, give the user `funding.checkout_url` (credit) or `funding.approval_url` (budget). If a send still returns `402`, the error's `details.checkout_url` or `details.approval_url` is the link to hand over; nothing was sent, so retry with the same `idempotency_key` after they pay. Never try to pay or approve yourself.
27
27
  6. **Send.** Use `idempotency_key` on anything that might be retried. Read `cost` and `capacity` from the response instead of assuming.
28
28
  7. **Broadcasts need a person.** `npx sendforai broadcasts create ...` returns an `approval_url`; give it to the user and wait. Only pass `require_approval: false` when the user has explicitly said they approve sends themselves.
29
29
  8. **Watch results** with `npx sendforai events` (keep the cursor). No webhook endpoint is needed.
30
+ 9. **When the person wants to see or manage the account** (balance, spending, recent sends, card, budget, auto top-up, notice email), run `npx sendforai operator` (MCP `operator_link`) and give them the `url`. It is a signed link to their operator page, valid 7 days; there is no login. Do not open it yourself.
30
31
 
31
32
  ## Integrating into an app (Node)
32
33