> For the complete documentation index, see [llms.txt](https://docs.fastrouter.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastrouter.ai/api-reference/error-codes.md).

# Error Codes

### Error Code Overview

FastRouter uses standard HTTP status codes to indicate errors during API requests. Below is a list of common errors you might encounter, along with tips to resolve them.

| Code | Meaning                           | Description                                                                                                |
| ---- | --------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| 400  | **Bad Request**                   | The request is malformed. This could be due to missing parameters, invalid formats, or CORS issues.        |
| 401  | **Invalid Credentials**           | Your API key is invalid, disabled, or your OAuth session has expired. Check your credentials.              |
| 402  | **Insufficient Credits**          | Your account or API key has run out of credits. Add more credits and retry the request.                    |
| 403  | **Moderation Blocked**            | The input was flagged by the model’s content moderation system. Modify the prompt and try again.           |
| 429  | **Rate Limited**                  | You have exceeded your request limits (TPM/RPM). Slow down or increase your limits.                        |
| 500  | **Internal Error**                | Something went wrong on our side. Retry the request, and contact support if the issue persists.            |
| 502  | **Model Down / Invalid Response** | The selected model is currently unavailable or returned an invalid response. Retry or use fallback models. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fastrouter.ai/api-reference/error-codes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
