mirror of
https://github.com/supermemoryai/supermemory.git
synced 2026-09-29 01:41:22 +00:00
cba67a55ed
The route previously fell back to "x-api-key": process.env.EXA_API_KEY ?? "", so a missing env var produced an outbound call to Exa with an empty key. Exa returned an auth failure, which was then surfaced to the client as a generic 500 "Failed to fetch content from Exa API" — making missing configuration indistinguishable from upstream errors and slowing self-hosted setup. Read EXA_API_KEY once at the top of the handler, log a specific message when it's absent, and return a 500 with a clear "service is not configured" error. The downstream fetch now uses the validated, non-empty key directly. |
||
|---|---|---|
| .. | ||
| (app) | ||
| (auth)/login | ||
| api | ||
| auth/connect | ||
| ref | ||
| upgrade-mcp | ||
| global-error.tsx | ||
| icon.png | ||
| layout.tsx | ||
| manifest.ts | ||
| not-found.tsx | ||
| opengraph-image.png | ||
