> 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/dashboard/overview.md). # Overview Oxylabs Dashboard is where you activate products, monitor spending, and manage your account. All in one place to set up and manage as you like. [Oxylabs Dashboard](https://dashboard.oxylabs.io) is built around a few core ideas: * **A credit-based billing model:** One shared balance covers all your products, instead of a separate subscription per product. See [Credit-Based Billing](/dashboard/credit-based-billing.md). * **Self-service product activation:** Enable new products directly from the dashboard, instantly. See [Product Instances](/dashboard/product-instances.md). * **Real-time spending and usage visibility:** Follow your budget, plan usage, and statistics anytime. * **Granular instance limits:** Cap spending, results, or traffic per product instance, not just account-wide. **Want to know all the basics in just 2 minutes? Check the video below:** {% embed url="" %} ## Overview page When you log in, the **Overview** page is your home section. It shows: * Your current plan and real-time spending progress in the top bar. * A table of all your active product instances. The top bar shows your current plan and spending budget. For a full breakdown of how this balance works, see [Credit-Based Billing](/dashboard/credit-based-billing.md). ## Product instances table {% hint style="info" %} A product instance is a specific configuration of a service (e.g., Residential Proxies, Web API) with its own name, authentication credentials, and optional spending limit. {% endhint %} The Overview page lists all your active instances along with their `Usage`, `Spending`, `Limit`, and `Price`. Use the search bar and filters to find instances by `Product`, `Status`, or `Limit`. For step-by-step instructions on creating and configuring instances, see [Product Instances](/dashboard/product-instances.md). ## Where to go next | I want to... | Go to | | --------------------------------------- | ------------------------------------------------------------------------------- | | Create or manage a product instance | [Product Instances](/dashboard/product-instances.md) | | Understand how billing and credits work | [Credit-Based Billing](/dashboard/credit-based-billing.md) | | Change my plan or add credits | [Upgrading, Downgrading & Top-Ups](/dashboard/upgrading-downgrading-top-ups.md) | | Update payment details or cancel a plan | [Payments & Invoices](/dashboard/payments-and-invoices.md) | | Manage my team or account settings | [Team & Account Settings](/dashboard/team-and-account-settings.md) | | Manage my proxy list | [Managing IP Products](/dashboard/managing-ip-products.md) | | Access usage data programmatically | [Dashboard API](/dashboard/dashboard-api.md) | --- # 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/dashboard/overview.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.