Application traffic
Production request mix across registered AI experiences.
Application control plane
Applications
4 active
Integration contract
Canonical identifiers Orvexa expects from any buyer backend.
Tenanttenant_id
Applicationapplication_id
External identityexternal_user_id
Sessionsession_id
Requestrequest_id
Tracetrace_id
Orvexa does not own the buyer's customer database. The buyer can pass stable external references through API/events and map them to any schema on their side.