huntitHelp center

Reading your key states — and fixing a rejected key

Every provider key shows its state on its row, on the setup screen and in Settings → Credentials. Red means the provider refused the key. Amber means the key works and the provider account behind it needs fixing.

Grey, green and red: the key

StateWhat it meansWhat to do
Not setNo key is connected for this provider yet.Add one with that provider's guide: BrightData, Apify or Gemini.
Verified (green)The key works and the account is ready.Nothing. Last verified is the last time a save or re-test passed, or the row cleared on its own.
Invalid (red)The provider refused the saved key, at a re-test or while it was in use. Usually it was revoked or regenerated.Press Re-test. If it stays red, replace it with a fresh key copied from the provider.

Amber: the account

The key is already saved, so there's nothing to paste again. Fix the account and the state clears at its next check, or re-test the key to clear it now.

StateProviderWhat it meansWhat to do
Free plan — upgradeApifyThe account is on Apify's Free plan.Upgrade to a paid plan (Starter), then re-test.
Usage limit reachedApifyThe account hit its monthly usage limit, so everything that runs on Apify is paused.Raise the limit in Apify under Billing, Limits, or wait for the next billing period.
Account not activeBrightDataThe account can't scrape yet: billing isn't activated, or BrightData suspended the account.Add a payment method and activate billing in BrightData, then re-test. For a suspension, contact your BrightData account manager.
Out of fundsBrightDataThe account is out of funds, so scraping can't run.Add funds in BrightData.
Needs fundingBrightData, during setup onlyYour balance and credit together are under $10, so scraping can't be turned on yet.Make your first deposit (BrightData matches it up to $500), then check again.
No creditsGeminiThe account has no usable credits: billing was never finished, the key is free-tier, or prepaid credit ran out.In AI Studio, add billing to the key's project and buy credit with auto-reload on, then re-test.

After setup, low BrightData funds show as a note under its row, not as a state. BrightData funding rules explains why.

When a state changes on its own

States change without a save. The Apify row is re-checked about every 15 minutes, and the BrightData row whenever new posts are collected. The Gemini row is checked whenever a post is analyzed, and once a day while it shows a problem.

When a provider refuses the key or the account stops, the row turns red or amber with the fix written under it. Most of these also ring a provider alert. Once the provider works again, the row turns green at its next check.

While the Gemini row is red or amber, the manual analyses and the analyses Claude runs for you don't start. A re-test that passes lets them run again.

When a pasted key is refused

A refused key is never saved, and the message under the field says why.

MessageProviderCauseFix
That key didn't pass its testAnyA typo, a partly copied key, or a key that was revoked or regenerated. Setting a BrightData key to Admin regenerates it.Copy the current key from the provider and paste it again.
on the Free plan, so the key wasn't savedApifyThe key works, but the account is on the Free plan.Upgrade to a paid plan (Starter), then paste the key again.
has limited permissionsBrightDataYou pasted the default key, which has User permissions.In BrightData, Settings → Users and API keys → ⋯ → Edit key configuration. Set Permissions to Admin and Expiration to Never expires, then paste the new key it shows once.

A key that saves but turns the row amber was not refused: its state is in the amber table above.

If BrightData declines your first deposit, its anti-fraud check flagged the payment. Match the billing details to the card exactly, then retry once or use PayPal. Don't keep retrying. See BrightData account troubles.

If it still fails

Use Request support, on the setup screen or from the sidebar, and say which key failed and the message you saw.