> For the complete documentation index, see [llms.txt](https://developers.oxylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.oxylabs.io/help-center/products-and-features/how-to-set-up-limitations.md).
# How to set up limitations
Learn how to set usage or spending limits for your product instances in Oxylabs Dashboard.
Limits cap how much an instance can use. This keeps one project from using up your whole balance.
When creating an instance, open Limits & Spending and enable limits. Enter your preferred limit, then set the limit type and period. Limits reset automatically based on the period you choose, for example, a daily limit resets at 00:00 UTC.
Choose what happens when a limit is exceeded. The instance can be disabled, an email can be sent, or both. To notify other people, add their addresses as email recipients.
You can come back and edit limits anytime afterward. Open your instance and choose **Set limits**. This opens a window where you can enable limits, enter your preferred limit, and set the limit type and period. The same settings are also available under **Configurator → Limits & Spending**.
🔎 For proxies, you'll set limits in GB. For Web API, you'll set limits in number of requests.
---
# 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://developers.oxylabs.io/help-center/products-and-features/how-to-set-up-limitations.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.