> ## Documentation Index
> Fetch the complete documentation index at: https://developers.meshapi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Support

> Get help with Mesh API — debugging tips, contact options, and useful resources.

## Self-service resources

Before reaching out, these resources often resolve issues quickly:

* **Request logs** — every request has a unique `req_...` ID visible in Dashboard → **Logs**. Filter by date, model, or key to find a specific call.
* **Error codes** — check the `error.code` field in the response body. Common codes are listed below.
* **Model status** — if a specific model is failing, check whether it's enabled in `GET /v1/models`.
* **Balance** — a `402 Payment Required` response means your balance is zero or a spend cap was hit. Check Dashboard → **Billing**.

## Common error codes

| Code                        | HTTP | Cause                                   | Fix                                            |
| --------------------------- | ---- | --------------------------------------- | ---------------------------------------------- |
| `unauthorized`              | 401  | Missing or invalid API key              | Check `Authorization: Bearer rsk_...` header   |
| `forbidden`                 | 403  | Key is active but lacks permission      | Verify key scopes                              |
| `spend_limit_exceeded`      | 402  | Balance zero or spend cap exceeded      | Top up or raise the cap                        |
| `rate_limit_exceeded`       | 429  | RPM or RPD limit hit                    | Wait and retry, or raise the key's rate limits |
| `model_not_found`           | 404  | Model ID doesn't exist or isn't enabled | Use `GET /v1/models` to check available models |
| `upstream_error`            | 500  | Provider returned an error              | Retry — often transient                        |
| `upstream_rate_limit_error` | 429  | Provider throttled the request          | Retry with backoff                             |

## The error catalog endpoint

`GET /v1/errors` returns the full error action-item catalog — the machine-readable
source behind the table above. Use it to surface a helpful message and next step
for any error your client receives:

```bash theme={null}
curl https://api.meshapi.ai/v1/errors \
  -H "Authorization: Bearer rsk_YOUR_KEY"
```

Resolve an error by looking up `codes` with the specific error identifier, falling
back to `categories` by the error's category, then to `default`.

<Info>
  The payload is small and slow-changing. Cache it, and re-fetch only when its
  `version` field changes.
</Info>

For a symptom-by-symptom walkthrough of Mesh API failures, see
[Troubleshooting → Mesh API](/debug/mesh-api).

## Contacting support

**Email:** [support@meshapi.ai](mailto:support@meshapi.ai)

When writing in, include:

1. Your **request ID** (`req_...` from the response headers or Dashboard logs)
2. The **model** and **endpoint** you were calling
3. A **description of the issue** and any error message you received
4. The **account email** associated with your API key

## Billing issues

For payment failures, missing credits, or invoice questions: [support@meshapi.ai](mailto:support@meshapi.ai) with subject line **Billing**.

## Feature requests

Have an idea? Open a discussion or request at [support@meshapi.ai](mailto:support@meshapi.ai) with subject line **Feature Request**.