> For the complete documentation index, see [llms.txt](https://help.rankability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rankability.com/api/api-credits-rate-limits-and-errors.md).

# API credits, rate limits, and errors

Design integrations around plan-specific request limits, operation-specific credit rules, and structured error responses.

## Request limits

| Public plan | Requests per minute |
| ----------- | ------------------- |
| Solo        | 30                  |
| Core        | 30                  |
| Team        | 60                  |
| Agency      | 120                 |

Use response headers and retry with backoff after `429`. Page-based crawler operations also have daily quota headers.

## Credits

Write and run endpoints can reserve or consume credits. Read endpoints normally do not start metered work. Check the operation’s response and the [credit costs reference](/account-and-settings/credit-costs-reference.md).

## Failure semantics

Do not assume every failed status releases every reservation. Many operations charge only on success, but Autopilot is charged once a usable draft exists; a later optimization, fact, or image failure can still return a charged partial result.

## Common status codes

* `400` — Invalid request fields.
* `401` — Missing, invalid, expired, or revoked key.
* `403` — Missing scope or plan access.
* `402` — Insufficient credits.
* `404` — Resource not found in the authenticated organization.
* `409` — Conflicting state.
* `429` — Request, concurrency, or quota limit reached.

## Safe retries

Retry reads and documented polling calls with backoff. Before retrying a create or run request, check whether the first request already created a job so you do not create duplicate work.


---

# 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 dynamically by asking a question.

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

```
GET https://help.rankability.com/api/api-credits-rate-limits-and-errors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.