My API key is rejected, or the provider says there is no money left

Three different messages mean three different fixes: the provider refused the key, no key is saved for that provider, or the provider’s own account has run out of funds.

Last checked against the app on · View as Markdown

Steps

  1. Read the code on the message. NV-ROUTE-002 is "The API key was rejected", NV-ROUTE-010 is "No API key is saved for this provider" and NV-ROUTE-003 means the provider’s own account has no funds left, which is not your balance with us.
  2. For NV-ROUTE-002, open Settings, then Intelligence, then API keys, press Replace on that provider and paste the key again. Create a fresh key in the provider’s dashboard if you are not sure the old one is still active.
  3. For NV-ROUTE-010, no key is stored for the provider you chose. Add one in Settings, Intelligence, API keys, or choose a different provider in the model button.
  4. For NV-ROUTE-003, add funds with the provider and try again, or pick a model on an account that has some. NeuralVault’s own managed balance is a separate thing and is topped up in Settings, Intelligence, Managed usage.
  5. Send a short message in Chat to confirm.

How to tell it worked

A short message is answered by the provider you chose.

If it does not work

The key worked yesterday and is rejected today.
The provider may have revoked or expired it, or limited it to a project that excludes the model you chose. Make a new key and Replace the stored one.
The key is stored but every message fails.
Stored and valid are different things. A note "Saved, but not checked" means the provider could not be reached when you saved it. Check the provider’s dashboard for the key’s status and its funds.
You would rather not manage a provider account at all.
NeuralVault routing pays for the model from your NeuralVault balance instead. See the guide on routing.