Configuring secure client-side RAG search parameters

Security is paramount when configuring client-facing AI widgets. Under no circumstances should database credentials or API keys (such as OpenAI keys) be exposed directly to the browser runtime. ### Recommended Security Pattern Always proxy calls through a backend API endpoint. Instead of initializing the client with server keys: 1. Implement a route handler in your Next.js app (e.g., `/api/retrivora/[[...retrivora]]`). 2. Pass client requests to the secure backend SDK instance which holds environment keys in server-only scope. 3. Secure your backend endpoint using JSON Web Tokens (JWT) or session cookies to restrict unauthorized script execution. Retrivora incorporates cryptographic license verification and server-side request routing, ensuring your vector indexes remain securely sealed behind backend network walls.