# Live Wiring and Environment Truth > [!summary] > This page explains which live systems Eval Labs should call and how to verify it. --- ## Current environment rule For active Lucia development: ```text Eval Labs → api-dev.hellolucia.ai ``` For promoted validation: ```text Eval Labs → api-staging.hellolucia.ai ``` Do not confuse these. --- ## Active dev endpoint ```text https://api-dev.hellolucia.ai/admin/operator-focus ``` This is the correct endpoint when testing current dev Engine changes. --- ## Netlify environment variable Eval Labs uses a Vite environment variable: ```text VITE_LUCIA_EVAL_ENDPOINT ``` For active dev testing, it should be: ```text https://api-dev.hellolucia.ai/admin/operator-focus ``` Because Vite bakes environment variables into the frontend bundle, changing the Netlify variable requires a redeploy. --- ## Render CORS allowlist The dev Engine must allow Eval Labs as an origin. Render dev Engine environment variable: ```text ADMIN_ALLOWED_ORIGINS ``` It must include: ```text https://evaluationlabs.ai https://www.evaluationlabs.ai https://dev.hellolucia.ai https://lucia-admin-dev.onrender.com ``` --- ## How to verify the live path In browser DevTools → Network, run a custom prompt and click `operator-focus`. Expected: ```text Request URL: https://api-dev.hellolucia.ai/admin/operator-focus Status: 200 OK ``` If it points to staging, Eval Labs is testing stale validation code. If it has a CORS error, the Engine allowlist is wrong. --- ## Clean Devtools connections and queries >![[devtools-operator-focus-network.png]] _DevTools Network proof that deployed Eval Labs is calling the active dev Engine and receiving a 200 response._ --- >![[devtools-response-headers.png]] _DevTools Network request header._ --- >![[devtools-request-headers.png]] _DevTools Network response header._