@myapihq/cli 1.3.13 → 2.1.0

package/dist/registrant.js

@@ -4,7 +4,7 @@
 // Sources, in priority order:
 //   1. --registrant-json '<inline JSON>'
 //   2. Per-field flags (--registrant-name, --registrant-email, …)
-//   3. Stored on the active account (set via `myapi auth registrant set`)
+//   3. Stored on the active account (set via `myapi account registrant set`)
 //   4. Interactive TTY prompt — offers to save to config
 //   5. Hard error in non-interactive contexts
 //
@@ -127,7 +127,7 @@ export async function resolveRegistrantForRegister(flags, config) {
             const save = await confirm('  Save as your default for future domain registrations? (Y/n) ', true);
             if (save) {
                 saveConfig({ ...config, registrant: r });
-                console.error('  ✓ Saved. Manage with: myapi auth registrant <get|clear>');
+                console.error('  ✓ Saved. Manage with: myapi account registrant <get|clear>');
             }
         }
         return r;
@@ -135,18 +135,18 @@ export async function resolveRegistrantForRegister(flags, config) {
     // 5: hard error.
     error(`Missing registrant field(s): ${missing.join(', ')}\n\n` +
         `Provide them via one of:\n` +
-        `  myapi auth registrant set                  (one-time interactive setup)\n` +
+        `  myapi account registrant set                  (one-time interactive setup)\n` +
         `  --registrant-json '{"name":"...","email":"...","phone":"...","street":"...","city":"...","postal_code":"...","country_code":"DE"}'\n` +
         `  Per-field flags: --registrant-name, --registrant-email, --registrant-phone,\n` +
         `                   --registrant-street, --registrant-city, --registrant-postal-code,\n` +
         `                   --registrant-country, --registrant-state (US/CA only)`);
 }
-// ── Used by `myapi auth registrant set` ────────────────────────────────────
+// ── Used by `myapi account registrant set` ────────────────────────────────────
 // Public so the auth subcommand can drive the same prompt sequence without
 // going through the register flow.
 export async function promptAndSave(config, prefill = {}) {
     if (isNonInteractive()) {
-        error('myapi auth registrant set requires a TTY. Use --json \'{...}\' instead.');
+        error('myapi account registrant set requires a TTY. Use --json \'{...}\' instead.');
     }
     console.error('› Setting your WHOIS registrant info (used at every domain register call):');
     const r = await promptRegistrant(prefill);

package/dist/sdk-queue.test.js

@@ -78,9 +78,10 @@ describe('queue jobs', () => {
     });
 });
 describe('queue.EXPOSES', () => {
-    it('covers all 6 queue endpoints', () => {
-        expect(queue.EXPOSES).toHaveLength(6);
+    it('covers all 7 queue endpoints', () => {
+        expect(queue.EXPOSES).toHaveLength(7);
         expect(queue.EXPOSES).toContain('POST /queue/orgs/{org_id}/queues/{name}/jobs');
         expect(queue.EXPOSES).toContain('GET /queue/orgs/{org_id}/jobs/{id}');
+        expect(queue.EXPOSES).toContain('DELETE /queue/orgs/{org_id}/queues/{name}');
     });
 });

package/dist/skills/my-api-hq/README.md

@@ -8,6 +8,7 @@ Core identity and billing hub for the MyAPI ecosystem. **Start here** — every
 - API key creation and management
 - Organization management (`org_id` used by all other services)
 - Balance top-up and billing history
+- Org-wide health check (`myapi doctor`)
 
 ## Quickstart
 

package/dist/skills/my-api-hq/SKILL.md

@@ -3,7 +3,7 @@ name: my-api-hq
 version: 1.0.0
 description: >
   Auth, organizations, and billing hub. Start here to get an api_key and org_id — every other service depends on both.
-triggers: [api key, account, organization, org, billing, balance, topup, credits, setup, defaults, brand, sync brand]
+triggers: [api key, account, organization, org, billing, balance, topup, credits, setup, defaults, brand, sync brand, doctor, health check, is my org healthy]
 checksum: sha256-pending
 ---
 
@@ -13,7 +13,7 @@ The root service. It manages accounts, API keys, organizations, and billing. No
 
 ## Capabilities
 <!-- llm:start -->
-MyApiHQ is the platform's foundation. Every other service (domain, funnel, email, image, storage, pixel, webhook, workflow, url) requires both an `api_key` and (for org-scoped resources) an `org_id` minted here. Setup is one command — `myapi auth setup` — which provisions an account, generates an api_key, creates a default org, and stores everything in `~/.myapi/config.json`. Subsequent commands pick up those defaults automatically.
+MyApiHQ is the platform's foundation. Every other service (domain, funnel, email, image, storage, pixel, webhook, workflow, url) requires both an `api_key` and (for org-scoped resources) an `org_id` minted here. Setup is one command — `myapi account setup` — which provisions an account, generates an api_key, creates a default org, and stores everything in `~/.myapi/config.json`. Subsequent commands pick up those defaults automatically.
 
 ```
 myapihq  ──►  org_id + api_key
@@ -27,54 +27,67 @@ myapihq  ──►  org_id + api_key
 
 Two tiers, chosen at setup time:
 
-- **Anonymous** (`myapi auth setup --anonymous`): zero-friction account creation. **Starts with $0 credit.** Good for catalog browsing, reading help, inspecting schemas — nothing that costs upstream money. The agent-onboarding path: provisions an account in one call, no email needed.
-- **Registered** (verified email via `myapi auth link <email>`): unlocks $5 free credit and the paid surface (LLM, image, email, domain register, etc.). Required for `myapi billing setup` and anything that hits Stripe.
+- **Anonymous** (`myapi account setup --anonymous`): zero-friction account creation. **Starts with $0 credit.** Good for catalog browsing, reading help, inspecting schemas — nothing that costs upstream money. The agent-onboarding path: provisions an account in one call, no email needed.
+- **Registered** (verified email via `myapi account link <email>`): unlocks $5 free credit and the paid surface (LLM, image, email, domain register, etc.). Required for `myapi billing setup` and anything that hits Stripe.
 
-An anonymous account can upgrade at any time via `myapi auth link <email>` — the credit grants on successful verification. Anonymous accounts that need paid actions hit a friendly `INSUFFICIENT_BALANCE` or `REGISTRATION_REQUIRED` error pointing at `myapi auth link`.
+An anonymous account can upgrade at any time via `myapi account link <email>` — the credit grants on successful verification. Anonymous accounts that need paid actions hit a friendly `REGISTRATION_REQUIRED` error pointing at `myapi account link`; a registered account with an empty wallet hits `402 INSUFFICIENT_FUNDS` (top up, or enable auto-recharge — below).
+
+### Health check
+
+`myapi doctor` runs an org-wide consistency check across every slot (funnels, webhooks, domains, containers, workflows, emails, payments) and layers on customer-perspective DNS/HTTP probes from your machine. It returns per-section findings (`✓` pass / `⚠` warning / `✗` critical) with remediation hints; add `--json` for machine output. The exit code is non-zero **only** on customer-actionable criticals — platform-side issues the MyAPI team is already handling are surfaced with an `ℹ` marker but don't fail the run. Run it to self-check before building (is the org set up?) and after (did everything wire up?).
 <!-- llm:end -->
 
 ## Commands
 <!-- generated:start -->
 | Command | What it does |
 |---|---|
-| `myapi auth setup` | Interactive setup: creates account, generates api_key, sets defaults |
-| `myapi auth whoami` | Show current account, default org/funnel, balance, free-tier usage |
-| `myapi auth link [email]` | Upgrade anonymous account to registered (or add a second session) |
-| `myapi auth switch [index]` | Switch active account |
+| `myapi account setup` | Interactive setup: creates account, generates api_key, sets defaults |
+| `myapi account whoami` | Show current account, default org/funnel, balance, free-tier usage |
+| `myapi account link [email]` | Upgrade anonymous account to registered (or add a second session) |
+| `myapi account switch [index]` | Switch active account |
 | `myapi org list` | List all orgs (`*` marks the default) |
 | `myapi org create --name "..."` | Create a new org (`--yes` auto-sets as default) |
 | `myapi org get [id]` | Inspect one org (defaults to current default) |
 | `myapi org update [id]` | Update fields (name, tagline, description, business-sector, logo-url) |
 | `myapi org delete <id>` | Delete an org and cascade |
 | `myapi org sync-brand <domain>` | Scrape a live site and auto-fill brand info |
-| `myapi keys list / create / revoke <id>` | Manage API keys (alias `myapi auth api-keys`) |
+| `myapi keys list / create / revoke <id>` | Manage API keys (alias `myapi account api-keys`) |
 | `myapi billing balance` | Check balance |
 | `myapi billing topup <amount>` | Top up by dollar amount |
 | `myapi billing history` | Recent transactions |
+| `myapi billing usage [--period month|30d]` | Spend rolled up by service (this month, or trailing 30d) |
+| `myapi billing spend-cap [<amount> | clear] [--period month|day]` | Set/show/clear the account-level spend ceiling (IAM Layer 2) |
+| `myapi billing auto-recharge [show \| set \| disable]` | Keep the wallet funded automatically — off-session refill when balance drops below a threshold, bounded by a monthly cap |
+| `myapi account mailing-address ["<address>"]` | Get or set the account's CAN-SPAM mailing address (required for email send) |
 | `myapi config set-org <id>` / `set-funnel <id>` / `set-domain <name>` | Set CLI defaults |
 | `myapi install-skills` | Install agent skill files into ~/.claude/, ~/.gemini/, ~/.cursor/ |
+| `myapi doctor [--verbose] [--json]` | Org-wide health check: per-slot config/integrity findings + DNS/HTTP probes |
 <!-- generated:end -->
 
 ## Examples
 <!-- llm:start -->
 ```bash
 # Cold start: provision account + default org
-myapi auth setup
+myapi account setup
 myapi org create "Acme" --yes
 
 # Day-to-day
-myapi auth whoami           # confirm what's active
+myapi account whoami           # confirm what's active
 myapi billing balance       # before doing anything that costs credits
 myapi billing topup 20      # add $20
 
+# For unattended/autonomous runs: keep the wallet funded so a 402 never
+# stalls the agent. Refill to ≥$5, $20 at a time, up to $100/month.
+myapi billing auto-recharge set --threshold 5 --amount 20 --monthly-cap 100
+
 # Sync brand info from an existing website
 myapi org sync-brand acme.com
 
 # Switch between multiple accounts
-myapi auth switch 2
+myapi account switch 2
 ```
 
-If any service returns `402`, run `myapi billing balance` and top up before retrying.
+If any service returns `402 INSUFFICIENT_FUNDS`, top up (`myapi billing topup`) — or enable `myapi billing auto-recharge` so it refills itself. A `402 SPEND_CAP_EXCEEDED` is different: you hit a spend ceiling you set, so raise it with `myapi billing spend-cap` rather than topping up.
 
 Each org gets a free preview subdomain (`*.makeautonomous.com`) usable before registering a custom domain.
 <!-- llm:end -->

package/dist/skills/my-auth-api/README.md

@@ -0,0 +1,33 @@
+---
+# my-auth-api
+
+Add authentication to apps you build on MyAPI — a managed OIDC identity provider
+for your app's **end users** (à la Kinde/Auth0). Not your MyAPI account; that's
+`myapi account`.
+
+## What it does
+
+- One OIDC **auth tenant** per org (issuer + JWKS + hosted login page)
+- Register **OIDC clients** (your apps): `spa` (public) or `web` (confidential)
+- Managed **Google sign-in** — no customer GCP account
+- RS256 tokens, verified locally against the tenant JWKS
+- Standard OIDC endpoints (`/authorize`, `/token`, `/userinfo`, `/jwks`,
+  `/.well-known/openid-configuration`) consumed by your app + the JS SDK
+
+## Quickstart
+
+```bash
+# Provision the tenant, then register an app
+myapi auth tenant create
+myapi auth client create --name "My App" --type spa \
+  --redirect https://app.example.com/callback
+
+myapi auth tenant         # issuer + hosted login URL
+myapi auth client list
+```
+
+Point any OIDC client library at the tenant `issuer`; verify access tokens
+against `<issuer>/jwks`.
+
+> Sign-in methods: managed Google, email/password (with verification + reset),
+> and magic links — pick per tenant with `auth tenant create --connections`.

package/dist/skills/my-auth-api/SKILL.md

@@ -0,0 +1,112 @@
+---
+name: my-auth-api
+version: 1.0.0
+description: >
+  Add authentication to apps you build on MyAPI — a managed OIDC identity provider for your app's END USERS (à la Kinde/Auth0). One auth tenant per org; register OIDC clients; sign users in with managed Google or the hosted login page; verify RS256 tokens against the tenant JWKS.
+triggers: [auth, authentication, login, sign-in, oidc, oauth, jwt, jwks, sso, google sign-in, user accounts, identity provider, kinde, auth0, clerk]
+checksum: sha256-pending
+---
+
+# MyAuthAPI
+
+Authentication for the **end users of apps you build on MyAPI** — not your MyAPI
+account (that's `myapi account`). It's a managed multi-tenant **OIDC identity
+provider**: each org gets one auth tenant, you register OIDC clients (your apps)
+against it, and your users sign in via managed Google or the hosted login page.
+Tokens are RS256, verified locally against the tenant's JWKS — no per-request
+call back to MyAPI.
+
+## Capabilities
+<!-- llm:start -->
+Auth is the identity layer for apps an agent deploys (containers, funnels). It
+closes the gap between "shipped an app" and "the app has real users with
+accounts" — natively, on the same org/domain/bill, no third-party auth to wire.
+
+**Mental model:** one **tenant** per org (your identity provider) → many
+**clients** (your apps) registered against it → end users sign in and get
+RS256 tokens your app verifies against the tenant **JWKS**.
+
+The standard OIDC machine endpoints live under the tenant issuer and are
+consumed by your app + the JS SDK, **not** the CLI:
+`/.well-known/openid-configuration`, `/jwks`, `/authorize`, `/token`,
+`/userinfo`. The CLI manages the two things you set up by hand: the tenant and
+its clients.
+
+- **Tenant** — `auth tenant create` provisions (idempotent) your org's OIDC
+  issuer + hosted login URL. `auth tenant` shows them.
+- **Client** — `auth client create` registers an app. `type spa` is a public
+  client (no secret; for browser/SPA/mobile). `type web` is confidential and
+  returns a `client_secret` **once** — store it immediately. `--redirect` lists
+  allowed callback URIs (absolute https, or http://localhost for dev).
+- **Usage** — `auth usage` shows monthly active users (auth is billed per MAU).
+- **Custom domain** — `auth domain set --domain auth.acme.com` serves auth on
+  your own domain; it prints the DNS record, TLS provisions automatically, and
+  the domain becomes your issuer once active.
+
+**Sign-in methods** are chosen per tenant via
+`auth tenant create --connections google,password,magic` (default `google`):
+**managed Google** (no customer GCP account), **email/password** (with
+verification + password reset), and **magic links** (passwordless email). All
+are served by the hosted login page. Verifying tokens, the authorize/token
+dance, userinfo, and the password/magic/reset flows are handled by the hosted
+page + standard OIDC — point any OIDC client library at the tenant issuer; the
+CLI is only the management surface.
+<!-- llm:end -->
+
+## Commands
+<!-- generated:start -->
+| Command | What it does |
+|---|---|
+| `myapi auth tenant` | Show your org's OIDC auth tenant (issuer + hosted login URL + sign-in methods) |
+| `myapi auth tenant create` | Create/enable the tenant (`--connections google,password,magic`; `--theme <json>`) |
+| `myapi auth client list` | List the OIDC clients (apps) registered to your tenant |
+| `myapi auth client create` | Register an OIDC client (`--name`, `--type spa\|web`, `--redirect`) |
+| `myapi auth usage` | Monthly active users (MAU) for the current period |
+| `myapi auth domain` | Show/set/delete a custom auth domain (`set --domain auth.acme.com`) |
+<!-- generated:end -->
+
+## Examples
+<!-- llm:start -->
+```bash
+# 1. Provision your org's auth tenant (one time)
+myapi auth tenant create
+# → issuer + login_url for the hosted login page
+
+# 2. Register your app as an OIDC client
+#    SPA / browser app (public, no secret):
+myapi auth client create --name "My SPA" --type spa \
+  --redirect https://app.example.com/callback
+
+#    Server-side / confidential app (secret returned ONCE):
+myapi auth client create --name "My API" --type web \
+  --redirect https://app.example.com/auth/callback
+
+# 3. Inspect
+myapi auth tenant
+myapi auth client list
+
+# 4. In your app: point any OIDC client library at the tenant `issuer`.
+#    Verify access tokens locally against <issuer>/jwks (RS256) — no call back.
+```
+<!-- llm:end -->
+
+## Tenant vs client
+
+- **Tenant** = your identity provider (one per org). It owns the issuer, signing
+  keys (JWKS), and the hosted login page. Create it once.
+- **Client** = one app authenticating against the tenant. Register one per app
+  (or per environment). `spa` = public, `web` = confidential (has a secret).
+
+## Operator auth is different
+
+`myapi auth` is for **your app's users**. To manage **your own MyAPI account**
+(login, API keys, billing config), use `myapi account` (`whoami`, `link`,
+`api-keys`, `config`, …).
+
+## Notes
+
+- The `client_secret` for `web` clients is shown **once** at creation and cannot
+  be retrieved later — store it immediately. SPA clients have no secret.
+- Redirect URIs are matched exactly: absolute `https://…` (or
+  `http://localhost…` for local dev).
+- `402 INSUFFICIENT_FUNDS` = empty wallet → `myapi billing topup <amount>` (or keep it funded automatically: `myapi billing auto-recharge set`). `402 SPEND_CAP_EXCEEDED` = you hit your account spend ceiling → raise it with `myapi billing spend-cap`.

package/dist/skills/my-auth-api/claude/.claude-plugin/plugin.json

@@ -0,0 +1,6 @@
+{
+  "name": "my-auth-api",
+  "description": "Managed OIDC identity provider for the end users of apps built on MyAPI. Per-org auth tenant + OIDC clients, RS256/JWKS, hosted login, managed Google sign-in. A Kinde alternative.",
+  "version": "1.0.0",
+  "published": true
+}

package/dist/skills/my-crm-api/SKILL.md

@@ -45,7 +45,7 @@ Set automatically based on how the contact entered the CRM. Useful filter when y
 ```
 created | promoted | stage_changed
 email_sent | email_opened | email_clicked | email_replied
-pixel_visit | webhook_received
+pixel_visit | webhook_received | payment
 ```
 
 Agents cannot write events directly — the closed enum is intentional. If you need custom state, use **mydatabaseapi** (KV) keyed on the contact id; the curated timeline stays authoritative for engagement.

package/dist/skills/my-domain-api/SKILL.md

@@ -29,10 +29,10 @@ The CLI stores this locally so you only enter it once:
 
 ```bash
 # One-time interactive setup (human)
-myapi auth registrant set
+myapi account registrant set
 
 # Or non-interactive (agent)
-myapi auth registrant set --registrant-json '{
+myapi account registrant set --registrant-json '{
   "name":"Simon Janin", "email":"simon@example.com", "phone":"+33612345678",
   "street":"1 rue de la Paix", "city":"Paris",
   "postal_code":"75001", "country_code":"FR"
@@ -47,7 +47,7 @@ Resolution at register time (highest wins): `--registrant-json` → per-field fl
 | Command | What it does |
 |---|---|
 | `myapi domain check <domain>` | Check availability and yearly price |
-| `myapi domain register <domain> [--years N] <registrant flags>` | Register a new domain (deducts credits). Requires ICANN WHOIS contact info — store once with `myapi auth registrant set`, or pass per-call via `--registrant-json` / `--registrant-*` flags |
+| `myapi domain register <domain> [--years N] <registrant flags>` | Register a new domain (deducts credits). Requires ICANN WHOIS contact info — store once with `myapi account registrant set`, or pass per-call via `--registrant-json` / `--registrant-*` flags |
 | `myapi domain renew <domain>` | Renew a registered domain for another period |
 | `myapi domain list [--filter all\|unassigned\|org]` | List domains in your account |
 | `myapi domain assign <domain>` | Assign domain to your default (or `--org`) org |
@@ -69,7 +69,7 @@ Resolution at register time (highest wins): `--registrant-json` → per-field fl
 <!-- llm:start -->
 ```bash
 # One-time: store your WHOIS contact info (used by every register call)
-myapi auth registrant set
+myapi account registrant set
 
 # Register and bring online
 myapi domain check example.com
@@ -114,6 +114,6 @@ Set `essentially_off` + `browser-check=off` to allow AI crawlers and training bo
 
 - `register`, `renew`, `assign`, and `unassign` always require an explicit domain argument — they don't fall back to a stored default, to prevent accidental destructive actions.
 - All commands default to `--org` from your saved config (set with `myapi config set-org <id>`).
-- `402` errors mean insufficient credits — run `myapi billing topup <amount>`.
+- `402 INSUFFICIENT_FUNDS` = empty wallet → `myapi billing topup <amount>` (or keep it funded automatically: `myapi billing auto-recharge set`). `402 SPEND_CAP_EXCEEDED` = you hit your account spend ceiling → raise it with `myapi billing spend-cap`.
 
 Run `myapi domain --help` or `myapi domain <subcommand> --help` for full flag reference.

package/dist/skills/my-email-api/README.md

@@ -1,7 +1,7 @@
 ---
 # my-email-api
 
-Send transactional email and run drip campaigns from mailboxes on your own registered domains. Includes AI template generation, warmup, and inbox/outbox reading.
+Send transactional email from mailboxes on your own registered domains. Includes AI template generation, warmup, and inbox/outbox reading.
 
 ## What it does
 
@@ -9,7 +9,6 @@ Send transactional email and run drip campaigns from mailboxes on your own regis
 - Send transactional emails (one-shot or templated)
 - Read inbox, outbox, sent history, and per-message status
 - Generate HTML email templates with AI from a prompt
-- Run paced drip campaigns against uploaded contact lists
 - Manage IP/domain warmup for sender reputation
 
 ## Quickstart
@@ -36,7 +35,7 @@ export MYAPI_KEY=mak_...
 Requires:
 - An `api_key` from **myapihq**
 - A registered domain via **mydomainapi**, assigned to your org
-- Default `org_id` (for templates/campaigns) — set with `myapi auth config set-org <id>`
+- Default `org_id` (for templates) — set with `myapi account config set-org <id>`
 
 ## Documentation
 

package/dist/skills/my-email-api/SKILL.md

@@ -2,20 +2,20 @@
 name: my-email-api
 version: 1.0.0
 description: >
-  Send transactional and bulk email from your own domain. Create mailboxes, send/receive messages, generate AI templates, run drip campaigns, and manage warmup.
-triggers: [email, mailbox, send email, transactional email, drip campaign, template, warmup, inbox, outbox, ses, sender reputation]
+  Send transactional and bulk email from your own domain. Create mailboxes, send/receive messages, generate AI templates, and manage warmup.
+triggers: [email, mailbox, send email, transactional email, template, warmup, inbox, outbox, ses, sender reputation]
 checksum: sha256-pending
 ---
 
 # MyEmailAPI
 
-Account-scoped email infrastructure tied to your registered domains. Mailboxes belong to domains; sending and receiving work without per-org plumbing. Templates and campaigns are org-scoped.
+Account-scoped email infrastructure tied to your registered domains. Mailboxes belong to domains; sending and receiving work without per-org plumbing. Templates are org-scoped.
 
 ## Capabilities
 <!-- llm:start -->
-Email is built around mailboxes. Each mailbox lives on a registered domain (e.g. `hello@yourdomain.com`) and must be activated for sending before transactional sends or campaigns work — newly-created mailboxes can receive but not send.
+Email is built around mailboxes. Each mailbox lives on a registered domain (e.g. `hello@yourdomain.com`) and must be activated for sending before transactional sends work — newly-created mailboxes can receive but not send.
 
-Templates are AI-generated HTML emails (org-scoped). Campaigns combine a template + a contact list + a per-day rate limit, sending to recipients over time. Warmup is a separate flow that gradually ramps a mailbox's send rate to build inbox reputation before high-volume campaigns.
+Templates are AI-generated HTML emails (org-scoped). Warmup is a separate flow that gradually ramps a mailbox's send rate to build inbox reputation before high-volume sending.
 
 A registered domain via **mydomainapi** is the prerequisite — mailboxes need a domain to live on.
 <!-- llm:end -->
@@ -28,7 +28,6 @@ A registered domain via **mydomainapi** is the prerequisite — mailboxes need a
 | `email message` | `send`, `status`, `sent`, `inbox`, `outbox`, `get` | Transactional send + read |
 | `email warmup` | `start`, `stats`, `pause`, `resume`, `stop` | IP/domain warmup for sending reputation |
 | `email template` | `generate`, `list`, `get`, `preview`, `edit`, `send-test`, `delete` | AI-generated HTML templates |
-| `email campaign` | `create`, `list`, `get`, `update`, `upload-contacts`, `upload-contacts-file`, `start`, `pause`, `resume`, `stats` | Drip campaigns |
 <!-- generated:end -->
 
 ## Examples
@@ -55,16 +54,7 @@ myapi email template preview <id>            # public preview URL — share with
 myapi email template send-test <id> --to me@yourdomain.com
 myapi email template edit <id> --prompt "Make the CTA larger and red"
 
-# 5. Drip campaign
-myapi email campaign create "Welcome series" \
-  --template-id <id> --from hello@yourdomain.com --per-day 50
-myapi email campaign upload-contacts <campaign_id> --emails "alice@x.com,bob@y.com"
-# (or for big lists)
-myapi email campaign upload-contacts-file <campaign_id> --file ./contacts.csv
-myapi email campaign start <campaign_id>
-myapi email campaign stats <campaign_id>
-
-# 6. Warm up before a big send
+# 5. Warm up before a big send
 myapi email warmup start --address hello@yourdomain.com
 myapi email warmup stats --address hello@yourdomain.com
 ```
@@ -74,7 +64,6 @@ myapi email warmup stats --address hello@yourdomain.com
 
 - A mailbox is uniquely identified by its address (`username@domain`).
 - Sending is opt-in per mailbox. Newly-created mailboxes can receive but not send until `activate-sending` runs.
-- Templates and campaigns are org-scoped. Set a default org once: `myapi config set-org <id>`.
-- An active or paused campaign blocks `domain unassign` with `DOMAIN_IN_USE`.
+- Templates are org-scoped. Set a default org once: `myapi config set-org <id>`.
 
 Run `myapi email --help` or `myapi email <namespace> --help` for full flag reference.

package/dist/skills/my-email-api/claude/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "my-email-api",
-  "description": "Send transactional and bulk email from your own domain. Mailboxes, AI templates, drip campaigns, and warmup.",
+  "description": "Send transactional and bulk email from your own domain. Mailboxes, AI templates, and warmup.",
   "version": "1.0.0",
   "published": true
 }

package/dist/skills/my-email-verify-api/SKILL.md

@@ -85,7 +85,7 @@ done < emails.txt | grep -v ' undeliverable$' > verified.txt
 
 - This is the **cheap layer only**. The full pipeline at outreach scale typically chains: this verify (free signal) → SMTP probe (medium cost) → catch-all detector (slow). Only the first is exposed today.
 - The `confidence` field is a hint, not a guarantee. A `deliverable` verdict at 0.95 confidence is still ≈5% bounce risk in practice.
-- For bulk verification, call this in parallel from your code with throttling — there is no batch endpoint today. A batch + async-job endpoint is on the backend roadmap.
+- For bulk verification use the async batch endpoint: `myapi email verify bulk < emails.txt` (one address per line) returns a `job_id`, then poll `myapi email verify job <job_id>` for status + per-address results.
 - Verification is per-org; you'll get rate-limited if you blast more than ~1 req/sec per key.
 
 Run `myapi email verify --help` for inline reference.

package/dist/skills/my-email-verify-api/claude/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "my-email-verify-api",
-  "description": "Sync single-address email verification — syntax + DNS + Microsoft probe. Pre-send quality gate for campaigns.",
+  "description": "Sync single-address email verification — syntax + DNS + Microsoft probe. Pre-send quality gate for outbound.",
   "version": "1.0.0",
   "published": true
 }

package/dist/skills/my-funnel-api/SKILL.md

@@ -115,6 +115,6 @@ myapi funnel form <funnel_id> --slug survey \
 - Set defaults with `myapi config set-org <id>` and `myapi config set-funnel <id>` to skip flags on every command — but a stale default is exactly how a push lands on the wrong org/funnel. For demos and one-offs, pass `--org`/`--funnel` explicitly instead of relying on whatever default was set last.
 - `push` (any slug) and `publish --env prod` overwrite live content and are refused without `--force` when something already exists at the target. `--force` means "yes, replace the live page/site" — confirm you're aimed at the right `(org, funnel, slug)` before using it, don't use it to silence the error.
 - Deleting a funnel purges all its edge pages immediately.
-- `402` errors mean insufficient credits — run `myapi billing topup <amount>`.
+- `402 INSUFFICIENT_FUNDS` → top up (`myapi billing topup`) or enable `myapi billing auto-recharge`.
 
 Run `myapi funnel --help` or `myapi funnel <subcommand> --help` for full flag reference.

package/dist/skills/my-git-api/README.md

@@ -0,0 +1,43 @@
+---
+# my-git-api
+
+Hosted git repositories over HTTP. Read history and commit atomically without a clone, or use real `git clone`/`push` over HTTPS with your API key as the password.
+
+## What it does
+
+- Repo CRUD: `create` / `list` / `get` / `delete`
+- Clone-free reads: `log` / `show` / `tree` / `blob` / `diff` / `refs`
+- Atomic writes: `commit` (JSON file edits) / `create-branch` / `delete-branch` / `tag`
+- Fast-forward `merge` and `repack`
+- **Real git over HTTPS** — `git clone`/`fetch`/`push` with HTTP Basic auth
+
+## Quickstart
+
+```bash
+# Create a repo and commit a file — no local clone
+myapi git create my-app --default-branch main
+myapi git commit my-app --branch main --message "init" \
+  --changes '[{"path":"README.md","content":"# My App"}]'
+
+# Or use real git over HTTPS (API key as the password, any username)
+git clone https://x:$MYAPI_KEY@git.mygitapi.com/<org-slug>/my-app.git
+# <org-slug> = your org's preview subdomain (myapi org get)
+git push origin main
+```
+
+## Authentication
+
+```bash
+export MYAPI_KEY=mak_...
+```
+
+Requires `api_key` and `org_id` from **myapihq**. For real-git clone/push, the
+same key is the HTTP Basic password (clone/fetch needs git read, push needs git
+write).
+
+## Documentation
+
+Full command reference, the `--changes` commit format, optimistic-concurrency
+(`--base`), and the smart-HTTP clone/push URL: see `SKILL.md`.
+
+Run `myapi git --help` for inline reference.