> For the complete documentation index, see [llms.txt](https://guides.getalby.com/user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.getalby.com/user-guide/browser-extension/features/create-and-change-budgets.md).
# Create and change budgets
Create and edit an allowance on a platform
When you want to pay in apps from the [Alby app directory](https://getalby.com/discover), Alby asks to confirm the payment
To avoid these requests you can create an allowance by checking the box in the prompt window. You will then have the chance to choose the budget for this website. When you click on confirm you pay the displayed amount and activate the allowance.
Now we can pay again with one click without an additional confirmation as long as we are within the set budget.
To check your active allowances you can open the extension window and see how much of it you have already spent..
..or you can go to '**Connected Sites**' in the Settings extension window.
Here, you see all websites that we granted access to your wallets. You will also see all active allowances and what budget is left per website.
By clicking on one of the websites you will see the site-specific transaction history
By clicking on the gearwheel you can now set a new budget. The new budget overwrites the old one and starts at 0 sat used.
---
# 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://guides.getalby.com/user-guide/browser-extension/features/create-and-change-budgets.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.
