Decide where API key management lives in the IA and how the UX should work.

Current state: /dashboard/keys exists with full CRUD functionality.

Options to consider

• Keep at /dashboard/keys (current)
• Dedicated /keys route (more prominent)
• Part of onboarding flow first, then dashboard
• Settings subpage

Decision needed

Where keys page lives in navigation, whether it's the first thing new users see after signup.

---

Decided Approach

Onboarding-first flow with keys as mandatory step

1. Create /h/onboard route that checks if user has any API keys
2. If no keys, show streamlined key generation flow (subset of current keys page)
3. After generating first key, redirect to dashboard
4. Returning users with keys bypass onboarding
5. Keys management remains at /h/dashboard/keys for ongoing management

Decision: @Keys page: onboarding-first flow with mandatory key generation