> For the complete documentation index, see [llms.txt](https://stonkfun.gitbook.io/stonkfun-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stonkfun.gitbook.io/stonkfun-docs/developer-api/rate-limits.md). # Rate limits Every response carries `X-RateLimit-Remaining` and `X-RateLimit-Reset`. A `429` adds `Retry-After`, and you should honour it. ## The whole table | Endpoints | Per minute | Covers | | ---------------------------------------- | ---------: | ----------------------------------- | | Everything except the two prepares | 300 | Reads, both submits, status polling | | `POST /launches/prepare` | 25 | Launch quotes | | `POST /tokens/{mint}/fees/claim/prepare` | 20 | Claim quotes | Limits are per IP address, per minute, and that table is the whole story. There are no paid tiers above it. Read responses are CDN-cached, and a cache hit never reaches the origin, so it costs you nothing against these numbers. ## Why the prepares are lower The two prepare endpoints are the only ones that do real work for a caller who has committed nothing. Each one spends several on-chain reads and builds a transaction before anybody has paid or signed anything, so they get their own, tighter budget. Everything else is either a cached read or already bound to a real payment. An invalid payment is refused before any work happens, and a valid one has been paid for. The two prepares have separate counters rather than sharing one, because they are unrelated activities. Claiming fees across a portfolio should not be throttled by someone else's launch burst from the same address. ## Sizing The numbers are set well above what an honest integration does, because a false positive here breaks somebody's product, and on the launch path it breaks it for somebody who has already paid. The read budget in particular is sized so that an integrator running many launches at once can poll every one of them at the recommended 5-second cadence and still have room for ordinary reads. ## Need more headroom? Building something that needs more than the table above? Get in touch: [@launchonsf](https://x.com/launchonsf). --- # 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://stonkfun.gitbook.io/stonkfun-docs/developer-api/rate-limits.md?ask=&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.