Skip to main content
When Henry reports that the API key is invalid, the cause is almost always on the provider side (a revoked or rotated key, a usage limit, a permission scope). Work through the symptoms below.
Cause. The most common cause is a key that has been rotated or revoked in the provider’s dashboard. Second most common: a key with insufficient permissions.Fix.
  1. Open your AI provider’s dashboard (OpenAI or Gemini).
  2. Find the key currently in use (the name should match what you configured in Brand Atlas).
  3. If the key is missing, it was revoked. Generate a new one.
  4. If the key exists but is restricted, check that Chat completions (OpenAI) or Generate content (Gemini) is in the allowed scopes.
  5. Paste the working key into Settings → AI → Henry in Brand Atlas. The test runs automatically.
Cause. The usage limit on your provider account has been reached, or the account has no credit balance.Fix.
  1. In your provider’s dashboard, check the current usage and limit.
  2. Increase the limit, or add credit to the account.
  3. Henry resumes working within minutes of the limit being raised.
Cause. The provider is rate-limiting requests, usually due to a usage spike or a low default per-minute limit.Fix.
  1. Wait the suggested time and try again.
  2. If the rate limit is hit frequently, request a higher rate limit from the provider (both OpenAI and Gemini accept this request from established accounts).
  3. Consider whether the model in use is appropriate; higher-tier models often have lower default rate limits.
Cause. The model configured in Brand Atlas is not accessible on the provider account, or the model has been deprecated.Fix.
  1. Open Settings → AI → Henry → Model.
  2. Select a model that your provider account has access to.
  3. The default model is configured to one that all accounts can access.
Cause. A key was rotated or revoked recently, possibly by someone else on your team with provider-account access.Fix.
  1. In your provider’s dashboard, check the key’s audit log. The provider shows when the key was created, last used, and modified.
  2. If the key was revoked unexpectedly, check with your team. Treat unexpected key changes as a potential security incident; if no team member knows of the change, write to security@brandatlas.pro.
  3. Issue a new key and paste it into Brand Atlas.
Cause. The provider is having an outage.Fix.
  1. Check the provider’s status page (OpenAI: status.openai.com; Gemini: status.cloud.google.com).
  2. Wait for the provider’s recovery.
  3. For low-tolerance operations, see Switching providers for tested failover.

​
When the key cannot be recovered

If you have lost access to the key and the provider has no record of it (an account closure, a deletion), the key cannot be recovered. The fix is to create a new key:
  1. Sign in to your provider’s dashboard.
  2. Create a new API key with the same permissions and limits.
  3. Paste into Settings → AI → Henry → Replace key. The old key entry in Brand Atlas is removed in the same operation.

​
When to escalate

Write to support@brandatlas.pro when:
  • The fixes above do not resolve the issue.
  • Brand Atlas’s test of the key fails for reasons not covered above.
  • The provider’s dashboard shows the key as valid but Henry continues to report it as invalid.

Setting up Henry

Initial setup.

How your key is stored

The storage model.

Rotating and revoking

Hygiene practices.