supermemory/apps/web/app/api/onboarding
vimzh 494dd25cf8 fix(onboarding): hoist EXA_API_KEY check and return generic 503
Copilot review flagged two things:

1. console.error inside the handler fires on every request when the key
   is missing, which spams logs and can mask other errors. Moved the
   read to module scope so the warning fires once at module load.
2. 'Content extraction service is not configured' tells the client a
   bit too much about deployment state. Reply with a generic 'Content
   extraction is unavailable' instead, while keeping the detailed
   reason in the server log.

Also bumped the status from 500 to 503 since 'service unavailable due
to missing config' is what we are actually telling the client now.
2026-05-24 12:43:12 +05:30
..
account-status fix: Implement the onboarding account lookup (#913) 2026-05-11 02:29:15 -07:00
extract-content fix(onboarding): hoist EXA_API_KEY check and return generic 503 2026-05-24 12:43:12 +05:30
research feat: onboarding config, reset onboarding, xai agentic migration (#701) 2026-01-25 01:04:15 +00:00