# Chat gave an error: what each NV-ROUTE code means

In the Beta build, a failed chat reply shows an NV-ROUTE code that says whether the key was refused, the account is out of funds, you are being slowed down, the model is gone, or the model is not set up.

*https://perpetualtechnologies.co.uk/support/chat-error-codes-explained — last checked 2026-10-14*

## Steps

1. Read the message and the code under your last message. Press "Copy error details" if you need to send it to us.
2. NV-ROUTE-002, "The API key was rejected": open Settings, then Intelligence, then API keys. Check the key for that provider and paste it again, or use a different provider.
3. NV-ROUTE-003, the provider says the account has no funds left: it refused because the account on its side has nothing left, or not enough for a reply this long. Add funds with the provider, or pick a model on an account that has some. NeuralVault’s own balance is topped up in Settings.
4. NV-ROUTE-004, "Too many requests right now": the provider is limiting how many requests it will take. Wait a minute and send again, or pick a different model.
5. NV-ROUTE-005, "That model was not found": the provider has no model with that name. It may have been removed or renamed. Pick a different model.
6. NV-ROUTE-006, "The conversation is too long for this model": start a new conversation, or pick a model with a bigger context window.
7. NV-ROUTE-007, 008, 009 and 010 mean something is not set up: no provider, no model for the provider, no address for a provider that runs at an address you type, or no API key saved. Open Settings, choose or fill in what is missing, then try again. For a key, go to Settings, then Intelligence, then API keys.
8. NV-ROUTE-017, "Ollama cannot be reached": start Ollama (or install it from ollama.com/download), then send the message again. To use a cloud model instead, paste a key and pick that provider.
9. NV-ROUTE-018, "That address is not encrypted": a provider address that starts with http:// and is not on this computer would send your key across the network in the clear, so nothing was sent. Change it to https://. An address on this computer may stay http://.
10. NV-ROUTE-011, "The conversation could not be read": check the vault folder can be reached and is not open in another program, then send the message again.
11. NV-ROUTE-999, "The model could not answer": try sending it again. If it keeps happening, pick a different model or send us the error details.

## How to tell it worked

A short message in Chat is answered.

## If it does not work

**The model you want is missing from the picker.**

See the guide on a model missing from the picker.

**You cannot tell whether it is a key problem or a setup problem.**

Choose a different model and send another message. See the guide on chat not answering.

**The code is not on this list.**

Send it to us with its details. See the guide on NV codes.

## Related guides

- [My API key is rejected, or the provider says there is no money left](https://perpetualtechnologies.co.uk/support/key-rejected-or-no-funds)
- [Chat will not answer: what to check](https://perpetualtechnologies.co.uk/support/model-not-answering)
- [A model is missing from the picker, and what its labels mean](https://perpetualtechnologies.co.uk/support/model-missing-from-the-picker)

## Still stuck

Bug reports belong in the app, in Settings, About. Those carry no contact details, so they
get fixed rather than answered. To get a reply, email us instead: that route targets two
business days. https://perpetualtechnologies.co.uk/contact