exa-multi-env-setup

# Exa Multi-Environment Setup ## Overview Exa charges per search request at `api.exa.ai`. Multi-environment setup focuses on API key isolation per environment, request limits and caching to control costs in staging, and appropriate `numResults`/content settings per tier. ## Prerequisites - Exa API key(s) from dashboard.exa.ai - `exa-js` installed (`npm install exa-js`) - Optional: Redis for search result caching in staging/production ## Environment Strategy | Environment | Key Isolation | numResults | Content | Cache TTL | |-------------|---------------|------------|---------|-----------| | Development | Shared dev key | 3 | highlights only | None | | Staging | Staging key | 5 | text (1000 chars) | 5 min | | Production | Prod key | 10 | text (2000 chars) | 1 hour | ## Instructions ### Step 1: Environment-Aware Configuration ```typescript // config/exa.ts import Exa from "exa-js"; type Env = "development" | "staging" | "production"; interface ExaEnvConfig { apiKey: string; defaultNumResults: number; maxCharacters: number; searchType: "auto" | "neural" | "keyword"; cacheEnabled: boolean; cacheTtlSeconds: number; } const configs: Record<Env, Omit<ExaEnvConfig, "apiKey"> & { keyVar: string }> = { development: { keyVar: "EXA_API_KEY", defaultNumResults: 3, maxCharacters: 500, searchType: "auto", cacheEnabled: false, cacheTtlSeconds: 0, }, staging: { keyVar: "EXA_API_KEY_STAGING", defaultNumResults: 5, maxCharacters: 10...