# Errors, Rate Limits & Credits

Requests are metered two ways - how fast you call, and how many Cyber credits you spend. Both are visible in your responses.

## Request rate

Requests are rate-limited per token, about **1 request per second**. Sending faster returns `429` with `rate limit exceeded`.

## Credits

The Cyber API has its own monthly credit quota, separate from other Webz.io products:

- Every search, segmentation, cached-page, and image request costs **1 credit**.
- `requestsLeft` in every response shows your remaining balance (also in the `X-WebHose-Requests-Left` header).
- When the quota is exhausted, requests return `429` with `Too many requests: used X out of Y allowed in a month`.

## Error responses

| Status | When |
| --- | --- |
| `400` | Invalid query (`Failed to execute query: invalid query`), or an unknown `sort`, `order`, or segmentation `field` value |
| `401` | Missing or unknown token, or your account lacks Cyber API permission (`/cyberSeg` returns `429` in this case) |
| `429` | Rate limit exceeded or monthly quota used up |
| `500` | Internal error, including unbalanced quotes or parentheses in `q` |

> [!TIP]
> Need access, more credits, or additional networks? Contact **sales@webz.io**.