> For the complete documentation index, see [llms.txt](https://docs.bravostudio.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bravostudio.app/good-to-know/billing.md). # Billing Go to your profile page and you will find the Billing settings section

**Billing Settings**

In the **billing settings** you will find: * **Plan** -> Your current Bravo Plan. Also, the option to upgrade and downgrade your plan * **Next Invoice** -> Information about when and which amount will your next invoice be (only paying users) * **Add-on** -> Users that have upgraded their apps and are using an add-on (ADVANCED or BUSINESS) will be available to manage the allowance on which app will be using the Add-on. * **Payment details** -> Your credit card payment details * **EU VAT / Tax ID** -> option to add or update the Tax ID for your invoices * **Invoices** -> List of invoices to download --- # 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://docs.bravostudio.app/good-to-know/billing.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.