For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Trust CenterStatusSupportGet a demoPlatform
DocumentationEvals API ReferenceIntegrations & OTELPlatform SettingsSelf-HostingChangelog
DocumentationEvals API ReferenceIntegrations & OTELPlatform SettingsSelf-HostingChangelog
    • Platform Settings
    • Data Residency
    • RBAC
  • Project Settings
    • API Keys
    • Team Members
    • Roles & Permissions
    • Transformers
    • Integrations
    • Alerts
    • AI Connections
    • Model Costs
    • Data Usage
    • Evaluation Models
    • Evaluation Rules
    • Annotation Options
    • Classifiers
    • Data Sources
    • Data Retention
    • Audit Logs
  • Organization Settings
    • Projects
    • Users
    • Roles & Permissions
    • Model Credentials
    • SSO
    • Data Retention
    • Audit Logs
    • Feature Access
LogoLogo
Trust CenterStatusSupportGet a demoPlatform
On this page
  • Setting Up Credentials
  • Inheriting Credentials in Projects
Organization Settings

Model Credentials

Manage API credentials for AI models that are shared across all projects in your organization.
Was this page helpful?
Previous

Single-Sign-On (SSO)

Configure SSO for secure and streamlined authentication across your organization.
Next
Built with

Instead of entering API keys separately for each project, you can configure model credentials once at the organization level and let projects inherit them. This keeps your secrets in one place and makes rotating keys much less painful.

Setting Up Credentials

Head to Organization Settings → Model Secrets, find the provider you want, and click the three-dot menu to enter your API key.

You can configure credentials for:

  • Model Providers — OpenAI, Anthropic, Gemini, X-AI, DeepSeek, Mistral, Perplexity

  • Cloud Providers — Amazon Bedrock, Vertex AI

  • LLM Gateways — Portkey, LiteLLM

Inheriting Credentials in Projects

Just because you’ve set up credentials here doesn’t mean projects will automatically use them. Each project needs to explicitly opt-in by toggling Inherit from Organization in their Evaluation Model settings.

This is intentional—it gives you flexibility. Some projects might need different models or credentials, while others can just inherit the org defaults.