Owning surface
Provider VaultStart where the product already explains or controls the problem.
Support
Provider key invalid
A provider-key problem usually means credentials, account scope, or model access do not match what the runtime expects.
Guide summary
Use this page to understand the surface before you act inside it.
Recover when provider credentials or model access are not accepted by the runtime.
Guide type
SupportThis guide reflects the current product workflow and surface ownership.
Sections
5Summary first, then steps, mistakes, and recovery notes.
Related guides
3Written against the current product structure and core execution workflow.
Escalation rule
Use support with contextAttach the relevant run, mission, task, or artifact whenever possible.
Related action
Contact Support only after inspectionSupport is strongest when the dominant symptom is already known.
Guide section
Symptoms
These signals usually indicate this specific class of problem.
What it is
Recover when provider credentials or model access are not accepted by the runtime.
When to use it
Use this guide when these symptoms match what you see in the product.
Where to find it
Start from the owning surface: Provider Vault.
What happens next
You narrow the problem before you retry or escalate.
Common mistake
Escalating too early without checking whether the owning surface already explains the blocker.
Related action
Open the owning surface first, then return here if the diagnosis is still unclear.
- Provider shows invalid or inactive state
- Runs fail before meaningful specialist execution
- A supported provider is connected but no live execution can start
Guide section
Likely causes
- The API key is wrong or revoked
- The key belongs to the wrong environment or account
- The selected model is not supported for that provider account
- The provider account itself has a billing or access problem
Guide section
How to fix it
- Open Provider Vault and replace the credential carefully
- Verify the provider account and model access outside the product if needed
- Choose a supported default model
- Use Mock Mode temporarily if you only need workflow validation
Guide section
Where to inspect next
Use the product surface that owns the problem first.
Where to find it
Provider Vault
What happens next
The owning surface should tell you whether the next move is fix, retry, continue, or support.
Related action
Move into Provider Vault now if you have not already done so.
Guide section
When to contact support
Contact Support if the credential is known-good and the product still cannot use it safely.
Tip
Report with the right object
A linked run or artifact is much easier to investigate than a generic support request with no runtime context.