# First Activation Event (FAE)

**Purpose:** Conversion playbook §3.2, §3.5 — activation in <5 min. SSOT: this doc + GitHub #337, #330.

## Definition

**FAE = First API key created in the app and first successful request to the LLMHosts proxy (e.g. `GET /v1/models` or `POST /v1/chat/completions`) using that key.**

- **Measured:** Key creation is in DB; first request can be inferred from proxy logs or `apiKey.lastUsed`. Optional: track `first_key_created` and `first_proxy_request` in product analytics.
- **Target:** User reaches FAE in **<5 minutes** from start (signup or first visit).

## Minimal path (<5 min)

1. **Register** at llmhosts.com/auth/register (or login if existing).
2. **Verify email** (if required); skip if already verified.
3. **Login** → redirect to dashboard.
4. **Create API key** — Dashboard → API Keys → Create → copy key.
5. **First request** — `curl -H "Authorization: Bearer <key>" https://<tunnel-or-local>/v1/models` or equivalent.

Steps 1–4 are app-only; step 5 requires local proxy or tunnel (or cloud BYOK). For **app-only activation** we treat "API key created and copied" as a soft FAE; full FAE = key + one successful proxy call.

## Minimized setup

- No mandatory profile fields beyond email/password for signup.
- API Keys one click from dashboard; copy immediately.
- Docs and hero CTA: "Get your first API call in 90 seconds" → register → keys → curl.

## Instrumentation (optional)

- Backend: `apiKey.lastUsed` already exists; first non-null = first use.
- Frontend: on "Create key" success, optional event `first_key_created` (if no key existed before).
- No PII in events; correlation by anonymous or hashed user id per policy.
