> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/account/credits-and-rate-limits/how-credits-work.md). # How credits work Jet Admin’s [current pricing page](https://www.jetadmin.io/pricing) describes AI credits as the allowance used when the AI Builder generates an app from a prompt or makes substantial edits. People using an app you have already built do not consume AI building credits simply by using it. Plans differ in their monthly credit allowance. Free includes a limited allowance; Enterprise offers custom AI credits and lists rollover and on-demand top-ups. Check the pricing page and your account’s billing view for the allowance that applies to your plan. ## AI credit limits A monthly credit allowance limits how much AI building work your plan includes. The pricing page does not state a fixed credit cost for each prompt. For a reliable current balance or cost, use the usage information shown in your Jet Admin account or ask support before a large build. ## Rate limits A rate limit controls how quickly requests can be made; it is distinct from the monthly credit allowance. Jet Admin has not published a numerical AI Builder rate-limit schedule on its pricing page. If you are building an integration that depends on request throughput, ask Jet Admin support for the current limit for your plan and endpoint. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.jetadmin.io/account/credits-and-rate-limits/how-credits-work.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 `build a script that syncs our docs to a CMS` 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.