@myapihq/cli 2.10.0 → 2.11.0

package/dist/org-not-found.test.js

@@ -0,0 +1,42 @@
+// A resource sitting in another org answers exactly like a typo'd id. "Not
+// found" sends the reader to check the id — which is correct, and which is why
+// the org never gets questioned. Naming the org that was searched is what
+// turns the commonest org-drift symptom into its own diagnosis.
+//
+// The risk on the other side is appending it to everything, which is the
+// always-on banner in a different costume. These pin both edges.
+import { describe, it, expect } from 'vitest';
+import { withOrgContext } from './errors.js';
+const ORG = { org_id: 'org-aaaaaaaa-1111', org_name: 'Acme' };
+describe('withOrgContext', () => {
+    it('names the org searched on a 404', () => {
+        const out = withOrgContext('Funnel not found.', { status: 404, code: 'FUNNEL_NOT_FOUND' }, ORG);
+        expect(out).toContain('Funnel not found.');
+        expect(out).toContain('Acme');
+        expect(out).toContain('myapi org list');
+    });
+    it('fires on a not-found CODE even when the status is not 404', () => {
+        const out = withOrgContext('Resource not found.', { status: 400, code: 'not_found' }, ORG);
+        expect(out).toContain('Acme');
+    });
+    it('stays out of the way on unrelated errors', () => {
+        const msg = 'Too many requests. Please wait a moment and try again.';
+        expect(withOrgContext(msg, { status: 429, code: 'RATE_LIMITED' }, ORG)).toBe(msg);
+    });
+    it('says nothing when the org itself is what was not found', () => {
+        // "Looked in org X" where X is the id that does not exist restates the
+        // failure as though it were a clue.
+        const msg = 'Organization not found.';
+        expect(withOrgContext(msg, { status: 404, code: 'ORG_NOT_FOUND' }, ORG)).toBe(msg);
+    });
+    it('says nothing when no org was resolved', () => {
+        // Account-level commands (whoami, billing) never resolve an org; there is
+        // no org to blame and claiming one would be a fabrication.
+        const msg = 'Resource not found.';
+        expect(withOrgContext(msg, { status: 404, code: 'NOT_FOUND' }, undefined)).toBe(msg);
+    });
+    it('does not repeat an org the message already names', () => {
+        const msg = `Funnel not found in org ${ORG.org_id}.`;
+        expect(withOrgContext(msg, { status: 404, code: 'FUNNEL_NOT_FOUND' }, ORG)).toBe(msg);
+    });
+});

package/dist/org-notice.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/org-notice.test.js

@@ -0,0 +1,37 @@
+// The org-change notice has two silent failure modes and no build breaks for
+// either: always-speak turns it into noise that gets filtered out within a day
+// (and costs tokens on every call in an agent loop), always-silent lets the
+// wrong-org write it exists to catch go through unannounced. Pin both edges.
+import { describe, it, expect } from 'vitest';
+import { orgChangeNotice } from './helpers.js';
+const NAMES = { 'org-a': 'Acme', 'org-b': 'Demo Corp' };
+describe('orgChangeNotice', () => {
+    it('says nothing in steady state — the same org twice', () => {
+        expect(orgChangeNotice('org-a', 'org-a', NAMES)).toBeUndefined();
+    });
+    it('says nothing on the first ever resolution', () => {
+        // No prior means nothing has moved; announcing here would fire on every
+        // fresh config and train the reader to ignore the line.
+        expect(orgChangeNotice(undefined, 'org-a', NAMES)).toBeUndefined();
+    });
+    it('speaks when the org moves, naming both sides', () => {
+        const msg = orgChangeNotice('org-a', 'org-b', NAMES);
+        expect(msg).toBeDefined();
+        expect(msg).toContain('Acme');
+        expect(msg).toContain('Demo Corp');
+    });
+    it('still speaks when no name is cached, falling back to the id', () => {
+        // The cache is populated opportunistically by `org list` / `status`, so an
+        // agent that never ran either still has to be told the target moved.
+        const msg = orgChangeNotice('org-a', 'org-b', {});
+        expect(msg).toBeDefined();
+        expect(msg).toContain('org-a');
+        expect(msg).toContain('org-b');
+    });
+    it('shortens long ids so the line stays scannable', () => {
+        const long = 'org-7f1aa7f1-f6eb-4a6d-87b7-1bbe6584f5d6';
+        const msg = orgChangeNotice(long, 'org-b', {});
+        expect(msg).not.toContain(long);
+        expect(msg).toContain('org-7f1a');
+    });
+});

package/dist/output.d.ts

@@ -5,6 +5,11 @@ export declare function success(message: string): void;
 export declare function error(message: string): never;
 export declare function info(message: string): void;
 export declare function banner(message: string): void;
+type ResolvedContext = {
+    org_id: string;
+    org_name?: string;
+};
+export declare function setResolvedContextSource(fn: () => ResolvedContext | undefined): void;
 export declare function printJson(data: unknown): void;
 export declare function spinnerFrame(i: number): string;
 export declare function spinnerWrite(s: string): void;
@@ -16,3 +21,4 @@ export interface PrintTableOptions {
     empty?: string;
 }
 export declare function printTable<T extends object>(rows: T[], opts?: PrintTableOptions): void;
+export {};

package/dist/output.js

@@ -12,8 +12,15 @@ export function info(message) {
 export function banner(message) {
     process.stderr.write(message + '\n');
 }
+let resolvedContext;
+export function setResolvedContextSource(fn) {
+    resolvedContext = fn;
+}
 export function printJson(data) {
-    console.log(JSON.stringify(data, null, 2));
+    const ctx = resolvedContext?.();
+    const stampable = ctx && data !== null && typeof data === 'object' && !Array.isArray(data);
+    const payload = stampable ? { ...data, _resolved: ctx } : data;
+    console.log(JSON.stringify(payload, null, 2));
 }
 // Spinner / line-clear primitives. Used by polling helpers (utils.pollJob)
 // and any handler that wants its own progress UI.

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

@@ -1,10 +1,10 @@
 ---
 name: my-api-hq
-version: 1.0.0
+version: 1.1.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, doctor, health check, is my org healthy]
-checksum: sha256-fab324491446026e1600ac531bfbb164c10d46a617e528e6886be74b7dbdb4b1
+checksum: sha256-6f54c719facde1ddcdee04ffcf9527ed42550cbfc67679ced5aea55fc7adba7d
 ---
 
 # MyApiHQ
@@ -15,14 +15,6 @@ The root service. It manages accounts, API keys, organizations, and billing. No
 <!-- llm:start -->
 MyApiHQ is the platform's foundation. Every other service (domain, funnel, auth, payments, fn, workflow, database, storage, email, webhook, crm, llm, image, pixel, 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
-                  │
-          ┌───────┴────────┐
-     mydomainapi       myfunnelapi
-     (domains)         (websites)
-```
-
 ### Anonymous vs registered accounts
 
 Two tiers, chosen at setup time:
@@ -42,6 +34,7 @@ An anonymous account can upgrade at any time via `myapi account link <email>`
 | Command | What it does |
 |---|---|
 | `myapi account setup` | Interactive setup: creates account, generates api_key, sets defaults |
+| `myapi status` | Single-screen orientation: account + every resource in the default org. Start here when you don't know what already exists |
 | `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 |
@@ -72,6 +65,7 @@ myapi account setup
 myapi org create "Acme" --yes
 
 # Day-to-day
+myapi status                   # what exists already, in one screen
 myapi account whoami           # confirm what's active
 myapi billing balance       # before doing anything that costs credits
 myapi billing topup 20      # add $20
@@ -98,28 +92,54 @@ Each org gets a free preview subdomain (`*.makeautonomous.com`) usable before re
 - API keys have format `hq_live_...` and are sent as `Authorization: Bearer <key>`.
 - `org sync-brand` is async (scrapes the site, polls the job).
 
-## Minting a least-privilege API key
+## Scoping a key — and why `--org` is the one that saves you
 
 A key's authority is inline and always a subset of the key that mints it, so
 you can hand work a key that cannot exceed its job:
 
 ```bash
+myapi keys create --name agent --org <id> --grant '*'       # locked to ONE org
 myapi keys create --name ci --grant funnel:write,storage:read
 myapi keys create --name readonly --grant '*:read'          # read anything, write nothing
 myapi keys create --name billing-fn --org <id> --grant email --spend-cap 25
 ```
 
+- `--org <id>` — **lock it to one org.** Omit for account-wide.
 - `--grant <list>` — `slot:read` / `slot:write`; a bare slot means write, `*`
   means all. **Omitting `--grant` mints an unrestricted key.**
-- `--org <id>` — lock it to one org. Omit for account-wide.
 - `--spend-cap <usd>` — hard ceiling; `0` means the key cannot spend at all.
 - `keys revoke-all --kind function|manual|account` narrows the kill switch.
 
+**Agents working for one org: use an org-locked key.** The org is otherwise
+ambient — a saved default that survives across turns, where a stale one looks
+exactly like a correct one. That is how a demo lands on a live site. Locking
+turns a wrong-org write into a `403`. Keep your *own* key account-wide though:
+an org-locked one cannot create orgs or manage billing.
+
+Two more signals, no flags needed: resolving to a different org than last time
+prints `→ org changed: <from> → <to>` on stderr, once — silence means it has
+not moved. Under `--json`, object responses carry `_resolved: {org_id,
+org_name}`; assert on that rather than assuming.
+
 ## Org profile fields
 
 `myapi org create <name>` also takes `--tagline`, `--description`,
 `--business-sector` and `--logo-url`. They populate the org's public profile
-and the funnel created alongside it, so setting them at create avoids editing
-two places later.
+and the funnel created alongside it.
+
+## HTTP (from deployed code)
+
+<!-- http:start -->
+<!-- generated by `npm run canonical-sync` — do not edit -->
+```
+base   https://api.myapihq.com
+path   GET /hq/orgs/{org_id}
+auth   Authorization: Bearer <key>   (fn: env.__MYAPI_KEY · container: env.MYAPI_KEY)
+reply  { "success": true, "data": …, "error": null, "meta": {…} }
+```
+
+- **Per-slot host** — do not assume one host serves every slot.
+- **Org id goes in the PATH** — there is no `X-Org-Id` header.
+<!-- http:end -->
 
 Run `myapi --help` or `myapi <command> --help` for full flag reference.

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

@@ -4,7 +4,7 @@ version: 1.0.0
 description: >
   Saved audiences = named Goldfox-filter snapshots over the people or company database. Build a target list once, name it, reuse it across campaigns, refresh to re-evaluate against current data. The persistence layer on top of my-people-api + my-company-api.
 triggers: [audience, segment, target list, saved filter, goldfox, lead list, abm list, refresh, members, prospect database]
-checksum: sha256-a2c7142e880932ac2aa53cdb29b8632ce2c4d5ef33c3f8b6df705f7e987ab6af
+checksum: sha256-3fc9f2966804381cb9e2b5f52d44a0c12c857f243b151a93a813c6345574f07f
 ---
 
 # MyAudienceAPI
@@ -136,4 +136,19 @@ myapi audience create "EU growth-stage SaaS accounts" \
 - Audiences are per-org. Two orgs can have audiences with the same name; ids are globally unique.
 - Look before you delete: confirm the target with `myapi audience get <id>`, pass `--org` explicitly; delete verbs require `--yes` in non-interactive runs.
 
+## HTTP (from deployed code)
+
+<!-- http:start -->
+<!-- generated by `npm run canonical-sync` — do not edit -->
+```
+base   https://api.myapihq.com
+path   POST /audience/orgs/{org_id}/audiences
+auth   Authorization: Bearer <key>   (fn: env.__MYAPI_KEY · container: env.MYAPI_KEY)
+reply  { "success": true, "data": …, "error": null, "meta": {…} }
+```
+
+- **Per-slot host** — do not assume one host serves every slot.
+- **Org id goes in the PATH** — there is no `X-Org-Id` header.
+<!-- http:end -->
+
 Run `myapi audience --help` for full flag reference.

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

@@ -4,7 +4,7 @@ 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-5eeacc463d7323f85a330639b7073f735ccc80bddfb8217c9c15c56989b8a99a
+checksum: sha256-07690e940717e8f65c195f9fbecdc1def9372edfd52dea19f6570227008d28ad
 ---
 
 # MyAuthAPI
@@ -121,4 +121,19 @@ with no email — for throwaway or machine-owned orgs. It cannot receive
 password resets or magic links, so attach a real identity before anything
 depends on it. `myapi status` shows `Type: anonymous`.
 
-**End-to-end example:** `examples/authenticated-app/` walks the full seam — hosted login → token verification → per-user KV record → deployed container — including the parts that cost real users hours (verify the id_token for identity; the access token is a bearer credential for `<issuer>/userinfo`).
+**End-to-end example:** `examples/authenticated-app/` in github.com/myapihq/myapi walks the full seam — hosted login → token verification → per-user KV record → deployed container — including the parts that cost real users hours (verify the id_token for identity; the access token is a bearer credential for `<issuer>/userinfo`).
+
+## HTTP (from deployed code)
+
+<!-- http:start -->
+<!-- generated by `npm run canonical-sync` — do not edit -->
+```
+base   https://api.myapihq.com
+path   POST /auth/orgs/{org_id}/tenant
+auth   Authorization: Bearer <key>   (fn: env.__MYAPI_KEY · container: env.MYAPI_KEY)
+reply  { "success": true, "data": …, "error": null, "meta": {…} }
+```
+
+- **Per-slot host** — do not assume one host serves every slot.
+- **Org id goes in the PATH** — there is no `X-Org-Id` header.
+<!-- http:end -->

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

@@ -4,7 +4,7 @@ version: 1.0.0
 description: >
   Company database backed by the Goldfox crawl. Filter companies by Goldfox confidence tier, country/TLD consistency, behavioral page signals (has_careers_page, has_investors_page, has_shop_page, has_c_level, has_decision_maker), legal-entity status, headcount, and source-URL count. Account-based targeting and B2B firmographics.
 triggers: [companies, accounts, firmographics, abm, search, filter, goldfox, careers signal, investors, c-level, shop, b2b targeting]
-checksum: sha256-4754de8a66bf13e7e2f2a23acc407ccec147e142abf8adc670ae7962ca860a74
+checksum: sha256-5204c6218af2d4c52b1b81aa0d917b69c863be1d3c0384d2d2f7d9dda1587534
 ---
 
 # MyCompanyAPI
@@ -107,4 +107,19 @@ myapi audience members $AID --limit 50 --json > accounts.json
 - `keyword` is a substring match on the company's **domain** — use `--keyword stripe` to find domains containing "stripe".
 - For a persistent account list, use `my-audience-api` with `--from company`.
 
+## HTTP (from deployed code)
+
+<!-- http:start -->
+<!-- generated by `npm run canonical-sync` — do not edit -->
+```
+base   https://api.myapihq.com
+path   POST /company/orgs/{org_id}/search
+auth   Authorization: Bearer <key>   (fn: env.__MYAPI_KEY · container: env.MYAPI_KEY)
+reply  { "success": true, "data": …, "error": null, "meta": {…} }
+```
+
+- **Per-slot host** — do not assume one host serves every slot.
+- **Org id goes in the PATH** — there is no `X-Org-Id` header.
+<!-- http:end -->
+
 Run `myapi company --help` for full flag reference.

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

@@ -4,7 +4,7 @@ version: 1.0.0
 description: >
   Run containers on demand — long-running services, background workers, and scheduled jobs. The heavier-duty sibling of edge functions, for native deps and long execution.
 triggers: [container, cloud run, dynamic app, custom domain app, service, worker, scheduled job, deploy container, docker image]
-checksum: sha256-0e68a4596027c9ccccf0cc86423deffbe71307d265aa973d3cd6261db2695152
+checksum: sha256-a5aabfe95b85f1e6ceb2b9254441183d540e81f888cefbdcf302385b95db2fd0
 ---
 
 # MyContainerAPI
@@ -92,14 +92,14 @@ myapi container deploy <id> --source ./my-app
 # 2b. Or ship an image you already built and pushed.
 myapi container deploy <id> registry.example.com/my-app:v1
 
-# Either way this takes 100% of traffic immediately — there is no staging
-# step, so verify on a non-production container FIRST.
+# A plain deploy takes 100% of traffic the moment it lands. Gate it with
+# --smoke, or hold it back with --no-promote and test the revision yourself.
 
-# 3. Check what you actually shipped. Assert on content: a build whose
-#    frontend never bundled still binds its port and returns 200.
+# 3. Verify content, not status: a build whose frontend never bundled
+#    still binds its port and returns 200.
 curl -s https://<your-domain>/ | grep -q 'assets/' || echo "BROKEN BUILD"
 
-# 3. Serve it on a custom domain. The parent domain must already be
+# 4. Serve it on a custom domain. The parent domain must already be
 #    registered: myapi domain register synthesisdaily.com
 myapi container domain <id> app.synthesisdaily.com
 # → app.synthesisdaily.com now serves the container over HTTPS
@@ -150,6 +150,21 @@ service costs nothing while idle.
   `invalid_json_response`. Build the tarball yourself and pass
   `--source ctx.tar.gz`, or keep the directory clean.
 
+## HTTP (from deployed code)
+
+<!-- http:start -->
+<!-- generated by `npm run canonical-sync` — do not edit -->
+```
+base   https://api.myapihq.com
+path   POST /container/orgs/{org_id}/containers
+auth   Authorization: Bearer <key>   (fn: env.__MYAPI_KEY · container: env.MYAPI_KEY)
+reply  { "success": true, "data": …, "error": null, "meta": {…} }
+```
+
+- **Per-slot host** — do not assume one host serves every slot.
+- **Org id goes in the PATH** — there is no `X-Org-Id` header.
+<!-- http:end -->
+
 Run `myapi container --help` for the full flag reference.
 
-**End-to-end example:** `examples/authenticated-app/` walks the full seam — hosted login → token verification → per-user KV record → deployed container — including the parts that cost real users hours (env vars are create-only; a service is multi-instance; health-check `/livez` not `/healthz`).
+**End-to-end example:** `examples/authenticated-app/` in github.com/myapihq/myapi walks the full seam — hosted login → token verification → per-user KV record → deployed container. Every constraint it hits is in **Runtime constraints** above.

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

@@ -4,7 +4,7 @@ version: 1.0.0
 description: >
   The canonical store of engaged contacts + companies for an org. Auto-ingests from inbound webhooks via a configurable dot-path. Fixed lifecycle_stage enum (cold | warm | qualified | customer | churned). Append-only event timeline with reserved kinds. Soft delete + restore. Promote-from-Goldfox closes the discovery → engagement loop.
 triggers: [crm, contact, company, lead, engagement, pipeline, lifecycle, qualified, customer, webhook ingest, promote]
-checksum: sha256-dfadb20670d9d978503549d330c2c9717fbe6d13ac35b53d9e1a8874d2136fde
+checksum: sha256-3f840c8d7205d6a3eacc7c2be3ba2580a52a1964c085af241fd9ad67d48e19b6
 ---
 
 # MyCRMAPI
@@ -167,4 +167,19 @@ myapi crm contacts events <id> --kind webhook_received
 - **Only `webhook_received` fires today.** Email and pixel auto-ingest are coming; the CLI surface will not change.
 - **Free in v1.** Metered later if usage warrants.
 
+## HTTP (from deployed code)
+
+<!-- http:start -->
+<!-- generated by `npm run canonical-sync` — do not edit -->
+```
+base   https://api.myapihq.com
+path   POST /crm/orgs/{org_id}/contacts
+auth   Authorization: Bearer <key>   (fn: env.__MYAPI_KEY · container: env.MYAPI_KEY)
+reply  { "success": true, "data": …, "error": null, "meta": {…} }
+```
+
+- **Per-slot host** — do not assume one host serves every slot.
+- **Org id goes in the PATH** — there is no `X-Org-Id` header.
+<!-- http:end -->
+
 Run `myapi crm --help` or `myapi crm <namespace> --help` for inline reference.

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

@@ -4,7 +4,7 @@ version: 1.0.0
 description: >
   Per-org KV store with named namespaces, JSON values up to 256 KB, prefix-scan listing, and compare-and-swap via etag. The substrate for any stateful agent-built app on MyAPI — user tables, session stores, idempotency keys, per-user lookup maps.
 triggers: [database, kv, key value, namespace, store, state, etag, cas, session, idempotency]
-checksum: sha256-924071245c33bf3e43f085fbd756af003e19c990f4522f658de33f42504452d7
+checksum: sha256-9b6f14fa5b0115ce042c71f861cb71ec8993aa68447d740b63f5b3689c23b629
 ---
 
 # MyDatabaseAPI
@@ -105,26 +105,22 @@ myapi database get "by-email:$EMAIL" --ns users --json | jq -r .value
 - **Free in v1.** Metered later if usage shows a need. Cost discipline still applies — store data, not blobs.
 
 
-## Calling this from deployed code (HTTP)
-
-The CLI is not what runs in production — a deployed function or container calls
-the HTTP API directly. That surface was previously only discoverable by
-grepping the CLI bundle, which cost one team an hour per slot.
+## HTTP (from deployed code)
 
+<!-- http:start -->
+<!-- generated by `npm run canonical-sync` — do not edit -->
 ```
-base    https://api.myapihq.com
-path    /database/orgs/{org_id}/namespaces/{ns}/keys/{key}
-auth    Authorization: Bearer <api key>
-        (inside a function: env.__MYAPI_KEY · inside a container: env.MYAPI_KEY)
-body    writes take {"value": <json>} — the value is WRAPPED
-reply   { "success": true, "data": …, "error": null, "meta": {…} }
-        Unwrap `data`. On failure `success` is false and `error` is
-        { code, message }.
+base   https://api.myapihq.com
+path   PUT /database/orgs/{org_id}/namespaces/{ns}/keys/{key}
+body   writes are WRAPPED: {"value": <json>} — not the bare value
+auth   Authorization: Bearer <key>   (fn: env.__MYAPI_KEY · container: env.MYAPI_KEY)
+reply  { "success": true, "data": …, "error": null, "meta": {…} }
 ```
 
-**The org id goes in the PATH, not a header.** There is no `X-Org-Id`.
-**Base URLs differ per slot** — do not assume one host for everything.
+- **Per-slot host** — do not assume one host serves every slot.
+- **Org id goes in the PATH** — there is no `X-Org-Id` header.
+<!-- http:end -->
 
 Run `myapi database --help` for inline reference.
 
-**End-to-end example:** `examples/authenticated-app/` walks the full seam — hosted login → token verification → per-user KV record → deployed container — including the parts that cost real users hours (KV writes must be wrapped as `{"value": …}`).
+**End-to-end example:** `examples/authenticated-app/` in github.com/myapihq/myapi walks the full seam — hosted login → token verification → per-user KV record → deployed container — including the parts that cost real users hours (KV writes must be wrapped as `{"value": …}`).

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

@@ -4,7 +4,7 @@ version: 1.0.0
 description: >
   Register new domains and manage edge settings. Required before a funnel can go live on a custom URL.
 triggers: [domain, register domain, dns, custom domain, edge, cdn, security level, browser check, renew, namecheap]
-checksum: sha256-6a686b453528c69dcc791db409c04a514422951abf333c8feed7c614311815cb
+checksum: sha256-ffe00d434534f444320a3e84323e87168c0c5797445fa0f39eeb55ad8278f721
 ---
 
 # MyDomainAPI
@@ -133,4 +133,19 @@ myapi domain records create <domain> --type CNAME --name app --content x.com --p
   reassign path, so pass `--org` explicitly and check `domain list --filter all`
   first.
 
+## HTTP (from deployed code)
+
+<!-- http:start -->
+<!-- generated by `npm run canonical-sync` — do not edit -->
+```
+base   https://api.mydomainapi.com
+path   GET /domain/orgs/{org_id}/list
+auth   Authorization: Bearer <key>   (fn: env.__MYAPI_KEY · container: env.MYAPI_KEY)
+reply  { "success": true, "data": …, "error": null, "meta": {…} }
+```
+
+- **Per-slot host** — do not assume one host serves every slot.
+- **Org id goes in the PATH** — there is no `X-Org-Id` header.
+<!-- http:end -->
+
 Run `myapi domain --help` or `myapi domain <subcommand> --help` for full flag reference.

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

@@ -4,7 +4,7 @@ version: 1.0.0
 description: >
   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-aa22381613affcff041a8d51d2acb2ba657fecefc97f4feba45958bcc11b2e06
+checksum: sha256-98aedd0274a450fdd68a2d0cfe3a8af33520c58b2ce6e7cfaee7840fd5526aa6
 ---
 
 # MyEmailAPI
@@ -64,6 +64,7 @@ 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.
+- **`402`** — `INSUFFICIENT_FUNDS`: top up or enable `myapi billing auto-recharge`. `SPEND_CAP_EXCEEDED`: raise your own ceiling with `myapi billing spend-cap`.
 - Templates are org-scoped. Set a default org once: `myapi config set-org <id>`.
 
 
@@ -81,24 +82,19 @@ Two things that read as contradictory and are not:
   to run Google Workspace or another provider on the apex, check the existing
   records first with `myapi domain records <domain>`.
 
-## Calling this from deployed code (HTTP)
-
-The CLI is not what runs in production — a deployed function or container calls
-the HTTP API directly. That surface was previously only discoverable by
-grepping the CLI bundle, which cost one team an hour per slot.
+## HTTP (from deployed code)
 
+<!-- http:start -->
+<!-- generated by `npm run canonical-sync` — do not edit -->
 ```
-base    https://api.myemailapi.com   ← not the gateway
-path    /email/mailboxes   ·   /email/orgs/{org_id}/messages/send
-auth    Authorization: Bearer <api key>
-        (inside a function: env.__MYAPI_KEY · inside a container: env.MYAPI_KEY)
-body    application/json
-reply   { "success": true, "data": …, "error": null, "meta": {…} }
-        Unwrap `data`. On failure `success` is false and `error` is
-        { code, message }.
+base   https://api.myemailapi.com
+path   POST /email/send
+auth   Authorization: Bearer <key>   (fn: env.__MYAPI_KEY · container: env.MYAPI_KEY)
+reply  { "success": true, "data": …, "error": null, "meta": {…} }
 ```
 
-**The org id goes in the PATH, not a header.** There is no `X-Org-Id`.
-**Base URLs differ per slot** — do not assume one host for everything.
+- **Per-slot host** — do not assume one host serves every slot.
+- **Account-scoped, not org-scoped** — no `{org_id}` segment; the key identifies the account.
+<!-- http:end -->
 
 Run `myapi email --help` or `myapi email <namespace> --help` for full flag reference.

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

@@ -4,7 +4,7 @@ version: 1.0.0
 description: >
   Synchronous single-address email verification — syntax + DNS + Microsoft GetCredentialType probe. Returns a verdict in <1s for ~50% of inputs; the rest get verdict='unknown' with smtp_recommended=true. The pre-send quality gate for any outbound campaign.
 triggers: [email verify, email validation, deliverability, smtp, syntax check, dns mx, microsoft, mx lookup, bounce prevention]
-checksum: sha256-a8f4d3fa04436c997d02d1d33f262190166e59e3e890b1c40a877bbd49ad3f00
+checksum: sha256-c8ae836c355066eee8a12753f818d3a90c35b99983d74913c8fc76edcc99668f
 ---
 
 # MyEmailVerifyAPI
@@ -90,4 +90,19 @@ done < emails.txt | grep -v ' undeliverable$' > verified.txt
 - 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.
 
+## HTTP (from deployed code)
+
+<!-- http:start -->
+<!-- generated by `npm run canonical-sync` — do not edit -->
+```
+base   https://api.myemailapi.com
+path   POST /email/orgs/{org_id}/verify
+auth   Authorization: Bearer <key>   (fn: env.__MYAPI_KEY · container: env.MYAPI_KEY)
+reply  { "success": true, "data": …, "error": null, "meta": {…} }
+```
+
+- **Per-slot host** — do not assume one host serves every slot.
+- **Org id goes in the PATH** — there is no `X-Org-Id` header.
+<!-- http:end -->
+
 Run `myapi email verify --help` for inline reference.

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

@@ -0,0 +1,33 @@
+---
+# my-feedback-api
+
+The loop back from the people using what you built. A page collects feedback with a public widget key that authenticates nobody; you read, filter, and close it.
+
+## What it does
+
+- Public widget keys — embed in page source, restrict by origin, revoke without losing collected feedback
+- Three kinds (`bug` | `issue` | `suggestion`), chosen by the reporter rather than inferred
+- Filterable listing by kind and status, newest first, paged with `--limit` / `--offset`
+- `resolve` closes an item; unknown ids answer identically so ids can't be probed across orgs
+
+## Quickstart
+
+```bash
+myapi feedback widget create marketing --origins example.com,www.example.com
+myapi feedback list --status open
+myapi feedback resolve <id>
+```
+
+## Authentication
+
+```bash
+export MYAPI_KEY=hq_live_...
+```
+
+Requires `api_key` + `org_id` from **myapihq**. The widget key is separate and deliberately public — it goes in your page source.
+
+## Documentation
+
+Full command reference and why `kind` is a claim rather than a guess: see `SKILL.md`.
+
+Run `myapi feedback --help` for inline reference.