> For the complete documentation index, see [llms.txt](https://docs.axobug.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.axobug.com/limits.md).
# Limits & errors
Public alpha limits, error handling and a few habits that make integrations feel good.
## Public alpha limits
| Limit | Current allowance |
| ------------------- | ----------------------------------------------------------- |
| Authentication | No API key required |
| Run requests | 30 per minute per IP; shared by visitors behind the same IP |
| Request body | Up to 4,096 bytes |
| Simulation duration | 50, 100, 150 or 200 ms |
| Intensity | 0–2 |
| Persistence | Independent runs; no saved neural state between requests |
Keep simulation frequency separate from your render loop. One result can animate many screen frames. Show the click or input immediately, then use the returned response to drive the action.
## Handle an unsuccessful request
| Status | Meaning | What to do |
| ------ | -------------------------------- | --------------------------------------------- |
| 400 | Invalid JSON, parameters or view | Fix the request before retrying |
| 413 | Body is too large | Keep the JSON under 4 KB |
| 429 | Public alpha rate limit | Wait; Retry-After is 60 seconds |
| 503 | Experiment could not complete | Retry after a delay, or let the visitor retry |
```json
{
"error": "The brain could not complete this experiment. Please retry."
}
```
A network timeout is different from an HTTP error: you may have no response body to read. Set a finite timeout, preserve the pending action and show a retry state. Avoid immediate retry loops and do not treat a failed response as a zero neural signal.
## Have something bigger in mind?
Tell us what you are building, expected requests per minute and concurrent users. Capacity enquiries are reviewed individually; submitting an enquiry does not reserve capacity or change your alpha limits.
Discuss your project
Share your idea and the response frequency it needs.
---
# 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://docs.axobug.com/limits.md?ask=&goal=
```
`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.