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

# Errors and rate limits

## Error format

Errors from the trading endpoints use `{error, message, ...details}`. Launch endpoints return `error.code` and `error.fields` as described below.

## Launch endpoints

| HTTP | `error.code`            | When                                                                                                                                         |
| ---- | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| 400  | `INVALID_JSON`          | The body is not a JSON object                                                                                                                |
| 400  | `INVALID_PARAMS`        | A field breaks a factory or API limit. `error.fields` names them                                                                             |
| 400  | `KEY_MATERIAL_REJECTED` | A private key or seed field was present                                                                                                      |
| 413  | `PAYLOAD_TOO_LARGE`     | The body is over 16 KiB                                                                                                                      |
| 422  | `SIMULATION_REVERTED`   | `eth_call` reverted. `unsignedTx` is still included. `error.revert` names the error when recognized, such as `InvalidParams` or `HookNotSet` |
| 429  | `RATE_LIMITED`          | Too many requests. `Retry-After` is 600                                                                                                      |
| 503  | `RPC_UNAVAILABLE`       | The Robinhood Chain RPC did not answer. `unsignedTx` is still included so you can simulate elsewhere                                         |

## Trading and commitment endpoints

| HTTP | Codes                                                                                                   |
| ---- | ------------------------------------------------------------------------------------------------------- |
| 400  | `invalid_params`, `invalid_json`, `key_material_rejected`                                               |
| 403  | `not_creator`                                                                                           |
| 404  | `not_found`, `unknown_action`                                                                           |
| 409  | `not_on_curve`, `not_in_commit_window`, `nothing_committed`, `nothing_to_claim`, `insufficient_balance` |
| 422  | `simulation_reverted`. Unsigned transactions are still returned for inspection                          |
| 429  | `rate_limited`                                                                                          |
| 503  | `unavailable`, `rpc_unavailable`                                                                        |

## Rate limits

| Group                     | Limit                                                                                          |
| ------------------------- | ---------------------------------------------------------------------------------------------- |
| `validate` and `simulate` | 20 requests per 10 minutes per client IP. `validate`, `simulate`, and `marks` share one bucket |
| `quote` and `tx/*`        | 60 requests per minute per IP                                                                  |
| `launch/build`            | 30 simulations per API key per hour, plus per-wallet and per-key launch limits                 |

The launch window is kept in memory per server process. A limit across several instances needs a shared store.

The limit exists so a broken agent cannot hammer `eth_call` against the public RPC. It is not an authentication scheme.

## Handling failures

* On `429`, wait for `Retry-After` seconds.
* On `422` or `503`, the returned `unsignedTx` is for inspection or for simulation elsewhere. Do not sign it unless you have verified it.
* On `409 not_on_curve`, the launch has graduated. Trade on the Uniswap V4 pool instead.


---

# 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://polydash.gitbook.io/polydash-docs/agents-and-api/errors-and-rate-limits.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.
