Try Hatched live

Hatch a buddy, tap a habit,
copy three lines.

Everything on this page — the rule engine, the widgets, the embed token — is what ships to partners. You get a live session to poke, and the exact HTML you’d paste into your own product.

The sandbox

A scoped session for this visitor. The buttons below fire real events through the production rule engine — the widgets further down react to your taps over an embed token.

loading session…

Hatched — /try

back to the magazine &nearr;

how production token minting works

This demo mints tokens through /demo/hatch (cookie-scoped, no api key) so you can click through without setup. In production your backend calls POST /api/v1/embed-tokens with its api key:

# server-side — your backend mints a short-lived embed token
# per end-user, then hands it to your frontend.
curl -X POST "https://api.staging.hatched.live/api/v1/embed-tokens" \
  -H "x-api-key: $HATCHED_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "buddy_id": "<your user's buddy id>",
    "user_id":  "<your internal user id>",
    "scopes":   ["read", "marketplace:purchase", "items:equip"]
  }'

# → { "token": "eyJhbGci…", "expires_at": "…" }

what’s real vs. demo shortcut

widgets + endpoints — real prod bundles, real customer-scoped /widget/* endpoints. Same JS, same JWT, same guard.
token mint — demo shortcut via /demo/hatch. Prod path shown above.
hatch + evolve — committed Fern sprites for instant feel. Prod runs through the fal.ai pipeline (~6–8s per image).
event ingestion — /demo/event (cookie-auth wrapper) instead of /events (api-key auth). Same reason: no secret in the browser.

Hatch a buddy, tap a habit,copy three lines.

The sandbox

Hatch a buddy, tap a habit,
copy three lines.