> For the complete documentation index, see [llms.txt](https://docs.trybasket.live/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trybasket.live/developers-and-api/auth-and-rate-limits.md). # Auth & rate limits This page documents Basket API authentication and limits. ### Status Authentication and rate-limit policy are `TBD`. ### Why this page matters Integrators need to know whether the API is meant for public browsing, production workloads, or both. That depends on auth and rate-limit policy. ### Minimum final disclosure | Topic | Why it matters | | ----------------- | ------------------------------------------------------- | | Auth requirement | Determines onboarding path | | Rate limit window | Determines cache and retry design | | Limit scope | Determines whether limits apply per IP, key, or account | | Error codes | Determines failure handling | ### Until finalized Assume production integrations should be conservative and rate-aware until Basket publishes a formal policy. ### What to publish later * Whether public reads require auth * API key format * Per-IP or per-key limits * Burst and daily quotas * Error codes and retry guidance --- # 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.trybasket.live/developers-and-api/auth-and-rate-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.