Skip to main content
Open API keys in the platform and create an account-linked key. Copy it when it is shown and store it as a server-side environment variable.
Send it in the HTTP authorization header:
Use the key for project inference and access status. The owning account must still belong to the project team. A master key or standalone legacy key without a user identity cannot access project inference.

​
Browser sessions

The platform manages signed-in sessions for project setup, data editing, model registration, and demo controls. API keys cannot perform these session-only operations. Admin and developer roles can make changes; members can read and use connected inference.

​
Key handling

Never put a key in browser JavaScript, a public repository, a model registry field, or a shared chat URL. Revoke unused keys from API keys. Your application never needs the serving provider’s credentials.