Sign in to continue
Sign in to continue setup
Sign in first so Relayon can show your project boundary and next activation step.
Relayon / API runtime
Start by routing OpenAI-compatible API traffic through Relayon. Once traffic is connected, review runtime readiness, managed access, usage evidence, and project controls from the same surface.
Sign in to continue setup
Sign in first so Relayon can show your project boundary and next activation step.
Use one project-scoped API key, send one OpenAI-compatible request, then confirm whether runtime evidence is visible before expanding managed access.
POST https://api.relayon.ai/v1/chat/completions
curl https://api.relayon.ai/v1/chat/completions \
-H "Authorization: Bearer $RELAYON_API_KEY" \
-H "Content-Type: application/json" \
-d '{"messages":[{"role":"user","content":"Say hello from Relayon"}]}'The first response confirms transport and runtime gating. Evidence may still show as pending if the request completed before the bounded evidence view is refreshed.
No Relayon-routed request seen yet.
Sign in, create a project, and use the runtime test to produce the first Relayon-routed request.
The project needs one usable runtime key before Codex or another agent can connect safely.
This is a quick preview only. Open the project runtime page for full key, runtime, and evidence details.
Account ready
You are signed in. Keep this account tied to project access and recovery.
Create your first project
Projects are the runtime boundary for keys, agents, orders, and controls.
Request managed access
Managed access opens after billing and account review.
Open project runtime
Review readiness, keys, and controls before agents run.