Live Wiring and Environment Truth

This page explains which live systems Eval Labs should call and how to verify it.

Current environment rule

For active Lucia development:

Eval Labs → api-dev.hellolucia.ai

For promoted validation:

Eval Labs → api-staging.hellolucia.ai

Do not confuse these.

https://api-dev.hellolucia.ai/admin/operator-focus

This is the correct endpoint when testing current dev Engine changes.

Eval Labs uses a Vite environment variable:

VITE_LUCIA_EVAL_ENDPOINT

For active dev testing, it should be:

https://api-dev.hellolucia.ai/admin/operator-focus

Because Vite bakes environment variables into the frontend bundle, changing the Netlify variable requires a redeploy.

The dev Engine must allow Eval Labs as an origin. Render dev Engine environment variable:

ADMIN_ALLOWED_ORIGINS

It must include:

https://evaluationlabs.ai
https://www.evaluationlabs.ai
https://dev.hellolucia.ai
https://lucia-admin-dev.onrender.com

In browser DevTools → Network, run a custom prompt and click operator-focus. Expected:

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.

DevTools Network proof that deployed Eval Labs is calling the active dev Engine and receiving a 200 response.

DevTools Network request header.

DevTools Network response header.

⌘I