Get started
Contract-first REST for builders and agents. Same control plane as Fat Heron products — documented here for the developer surface.
One path for domainers and builders: mint an account API key, wire your agent, then run a first recipe. Prefer fh_test_ while rehearsing (sandbox dry-run); promote with fh_live_. Prefer clicks over keys? Start with human guides.
1. Choose your path
Same control plane and keys. Different first wins:
- Domainers — claim an alias or attach DNS on a portfolio domain. Mint keys in the portal at app.fatheron.com/developers.
- Builders — create a project and sandbox-plan a manifest. Mint keys at app.fatheron.dev/keys.
2. Mint an API key
Open Keys (builders) or Developers (portal). Label the key, pick fh_test_ for sandbox or fh_live_ for real mutations, set scopes (or a developer preset), create, and copy the secret once.
Typical agent scopes: builders:write, aliases:write, domains:write, notifications:write, billing:read. Full catalog: GET /v1/api-keys/scopes.
Recipe: Mint an API key.
3. Connect your agent
Install Fat Heron MCP (largest reach first). Paste-ready JSON and click-paths:
Prefer shell? fh CLI + @fatheron/sdk.
4. First win
With a test key, confirm sandbox first:
GET /v1/sandbox/status X-API-Key: fh_test_…
5. Troubleshooting
insufficient_scope
Mint again with the scopes the recipe lists (or legacy
write).invalid_api_key
Check prefix (
fh_live_/fh_test_), revoke+rotate if leaked.sandbox_mutation_forbidden
Test keys only mutate
sb-projects — or promote with a live key.dry_run: true
Expected on
fh_test_for aliases/DNS/billing/webhooks — not a failure.