> For the complete documentation index, see [llms.txt](https://docs.scraperapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scraperapi.com/resources/release-notes/april-2026/billing-page-redesign-released.md).
# Billing page redesign Released
We've redesigned the billing page from the ground up to make it easier to understand your plan, manage usage, and upgrade when you're ready.
## What's changed
The page is now organized into three tabs — *Subscription*, *Billing Details*, and *Manage plan* — so related information is grouped together instead of stacked on one long page.
The *Subscription* tab gives you a real-time view of your current plan, renewal date, and usage across API credits and concurrency. A visual meter shows how much of your limit you've used, and if you're approaching 70%, you'll see a warning before you hit the ceiling.
You can now choose what to do when you reach your plan limit from the billing page. You can choose between interrupted scraping (default), auto-upgrade, or pay-as-you-go — depending on your plan type. Controlling Plan limitation behaviors requires a payment method on file and walks you through adding one if needed.
***
**Nothing changes about your plan or billing** — this is a design update only. All existing subscriptions, payment methods, and invoices carry over exactly as they were.
*Questions? Contact our* [*support team*](mailto:support@scraperapi.com)*.*
Explore the new Billing page
---
# 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.scraperapi.com/resources/release-notes/april-2026/billing-page-redesign-released.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.