Sign-in and API keys

How people sign in and how org API keys are managed.

Sign-in

Sign in at https://platform.intertrace.ai/sign-in with email and password; /login and /signup redirect there. Members join through email invites (see Org invites), and roles are changed in Settings.

Single sign-on

SSO (SAML/OIDC) and directory provisioning (SCIM) are not available yet. Today everyone signs in with email and password, and access is managed through invites and roles.

Org API keys

Org API keys authenticate the control plane: itr, permission hooks and policy as code. Create and revoke them in Settings → API keys (needs gateway manage permission). New keys start itr_; older bst_ keys keep working. The key is shown once; Intertrace stores only a hash and a prefix.

Send it as X-Intertrace-Key. Runtime itr_rt_* keys are for the gateway and are rejected on control-plane routes. itr connect mints a hook-scoped org key named "itr on <host>" during browser sign-in, so developers never copy keys. See Control plane.