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
  • Generate an API Key
  • Manage API Keys
  • Best Practices
Project Settings

API Keys

Generate and manage API keys to authenticate your applications with Confident AI.
Was this page helpful?
Previous

Team Members

Managing team access in your projects.
Next
Built with

API keys are used to authenticate your applications when interacting with the Confident AI API. Each project can have multiple API keys, allowing you to manage access for different environments or services.

API keys do not count as a seat or user in your organization. You can create as many API keys as needed without affecting your billing.

Provision API Keys

Generate an API Key

To create a new API key:

  1. Navigate to Project Settings → API Keys
  2. Click the Generate New API Key button
  3. Enter a descriptive name for the key (e.g., “Production”, “Development”, “CI/CD Pipeline”)
  4. Copy and securely store the key secret

Manage API Keys

To manage an existing API key, click the three-dot menu (⋮) on the right side of the row:

  • Deactivate — Temporarily disables the key. The key can be reactivated later if needed.
  • Delete — Permanently removes the key from your project.

Deleting an API key is permanent and cannot be undone. Any applications using that key will immediately lose access to the API.

Best Practices

  • Use descriptive names — Name keys after their purpose (e.g., “GitHub Actions”, “Production Server”)
  • Rotate keys regularly — Generate new keys periodically and phase out old ones
  • Use separate keys per environment — Create distinct keys for development, staging, and production
  • Monitor usage — Check the “Last Used” column to identify unused keys that can be deactivated or deleted