Menu
Auth, organizations, and billing hub. Start here to get an api_key and org_id — every other service depends on both.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| 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","doctor","health check","is my org healthy"] |
| checksum | sha256-pending |
The root service. It manages accounts, API keys, organizations, and billing. No other service works without credentials from here.
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)
Two tiers, chosen at setup time:
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.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 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).
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?).
| Command | What it does |
|---|---|
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 (funnels included). Verify the target with myapi org get <id> first; asks for confirmation — --yes required in non-interactive runs |
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 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]` |
| `myapi billing spend-cap [ | clear] [--period month |
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 |
# Cold start: provision account + default org
myapi account setup
myapi org create "Acme" --yes
# Day-to-day
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 account switch 2
If any service returns 402 INSUFFICIENT_FUNDS, top up (myapi billing topup) — or enable myapi billing auto-recharge so it refills itself. With auto-recharge enabled, billable CLI commands (llm, image, email send, domain register/renew, git commit) handle a refill-in-flight automatically: they wait the server-hinted interval and retry instead of failing, so don't add your own retry loop. 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.
--org defaults once with myapi config set-org <id> to skip the flag on every command.hq_live_... and are sent as Authorization: Bearer <key>.org sync-brand is async (scrapes the site, polls the job).Run myapi --help or myapi <command> --help for full flag reference.
Deploy JavaScript functions to the MyAPI edge runtime (Cloudflare Workers). Register a function, upload a single-file JS bundle, get a live HTTP invocation URL or run it on a cron schedule. Each function gets a scoped capability key for cross-slot calls.
Take payments via Stripe — one-off or recurring. Connect your own Stripe account, then create hosted Stripe Checkout URLs. No raw card data ever touches your code.
Tracking pixel + identity resolution for MyAPI funnels and email. Capture visits and events, resolve known users to anonymous sessions, stream interaction events for analytics. Pairs with mycrmapi for auto-ingest of pixel_visit events on known contacts.
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.
Register new domains and manage edge settings. Required before a funnel can go live on a custom URL.
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.