# Error Responses

#### 400 Bad Request - Invalid Address

```json
{
  "success": false,
  "error": "Invalid address format"
}
```

#### 401 Unauthorized - Missing/Invalid API Key

```json
{
  "success": false,
  "error": "API key required in header"
}
```

#### 402 Forbidden - Insufficient credits

```json
{
  "success": false,
  "error": "Insufficient credits"
}
```

#### 403 Forbidden - Insufficient Paid Endpoint Permission

```json
{
  "success": false,
  "error": "Paid endpoints require credit billing to be enabled"
}
```

#### 403 Forbidden - Insufficient API Key Permissions 

```json
{
  "success": false,
  "error": "API key not authorized for this endpoint"
}
```

#### 404 Not Found - Request path invalid

```json
{
  "success": false,
  "error": "Not found"
}
```

#### 404 Not Found - Unsupported Network

```json
{
  "success": false,
  "error": "Network not supported"
}
```

#### 429 Rate Limit Exceeded

```json
{
  "success": false,
  "error": "Rate limit exceeded"
}
```

#### 500 Internal Server Error - API Unavailable

```json
{
  "success": false,
  "error": "External service unavailable"
}
```


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.drops.bot/api-reference/error-responses.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.