> For the complete documentation index, see [llms.txt](https://help.meltingspot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.meltingspot.io/english/how-to/accessing-your-billing-space.md). # Accessing your billing space Bzzz bzzz bzzzz... On your way to your Chargebee account! ### From your account, you can: * Check your subscription status * Download your invoices * Edit your subscription (under MeltingSpot's control) * Add options to your subscription ### Accessing your portal * You can access it from the URL [meltingspot.chargebeeportal.com](https://meltingspot.chargebeeportal.com/) * Log in with the email you used when you first subscribed to MeltingSpot and confirm access with the code sent by e-mail

### Adding add-ons to your subscription You can add options from your account, such as support slots with one of our community building experts. 1. Select your subscription 2. Click on `Edit subscription` 3. Click on `Add Addons` 4. Select 'Community Expert Support' 5. Choose the number of hours of support you want 6. Click on `Update subscription`. Well done :tada:

--- # 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://help.meltingspot.io/english/how-to/accessing-your-billing-space.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.