Documentation

Account & API Keys

Your Conical account includes settings, preferences, and authentication tools for integrations.

Account Settings

From the Settings page, you can:

  • Update profile information — Manage your display name and contact details
  • Change password — Update your account security credentials
  • View account status — See your account activation status and join date
  • Manage preferences — Control how you receive notifications and updates

API Keys

API keys enable external tools and services to authenticate with Conical on your behalf. They’re particularly useful for:

  • Research tools — Connect evaluation harnesses or assessment tools
  • External integrations — Use Conical conversations and assessments with other platforms
  • Automated workflows — Enable scripts or tools to interact with your data

Creating an API Key

  1. Go to Settings → API Keys
  2. Click “Generate New Key”
  3. Give the key a label (e.g., “Evaluation Harness”, “Research Tool”)
  4. Optionally set an expiration date
  5. Copy the key immediately—you won’t be able to see it again

Using Your API Key

Once created, use the key with the Authorization header:

Authorization: Bearer ak_YOUR_KEY_HERE

Include this header when making requests to Conical API endpoints.

Managing Keys

For each API key, you can see:

  • Label — The name you gave it
  • Created — When it was generated
  • Expires — Expiration date (if set)
  • Last Used — When it was last used for authentication
  • Actions — Revoke access or view key details

Security Best Practices

  • Use expiration dates — Set keys to expire after 30–90 days
  • Label keys clearly — Include what tool or purpose the key is for
  • Revoke unused keys — Remove keys for tools you no longer use
  • Don’t share keys — Treat API keys like passwords
  • Rotate keys regularly — Generate new keys periodically and retire old ones

Revoking a Key

Click “Revoke” next to any key to immediately disable it. The key becomes invalid for all future requests. This doesn’t delete historical data—it just prevents new authentications.