> 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/help-center/dashboard/navigating-the-dashboard.md). # Navigating the dashboard Oxylabs Dashboard is where you activate products, monitor spending, and manage your account. As soon as you sign up, you get **$5 in welcome credit**. Use it to test any available product before committing to a paid plan. Before you start exploring, watch the onboarding video for a quick tour of the dashboard and the key steps you'll need to get started. {% embed url="" %} ### **1. Explore products** Your home screen, or **All Products** page, shows an overview of your existing instances, and lets you browse all available products below. Select a product to learn more about it, or create an instance to start using it. ### **2. Create a product instance** You'll need to create a product instance whenever you want to use a product. A product instance is your specific setup for that product. It has its own name, authentication credentials, and a spending limit. Click **Add product instance** and select the product you need. Depending on the product, you'll need to: * Select the product type. * Name your instance. * **For IP-based products**, choose the number of IPs and, if needed, a location. You can search or scroll through the country list. * Set your authentication settings, for example, whitelisting your own IP addresses if needed. Once your instance is created, your username and password are generated and ready to use in your code. For step-by-step instructions on creating and configuring instances, see [Product Instances](https://sites.gitbook.com/preview/site_rPdpB/~/revisions/N8oqgYuDnXc4hB5kxNhV/dashboard/product-instances). ### **3. Monitor your usage** Use the left-hand menu to keep track of how you're using your products. Go to **Usage** to see your daily usage. You can switch between Traffic and Requests, use the filters to narrow down the data, and check your remaining credits in the usage graph. ### **4. Manage billing and spending** Go to **Billing & Spending** to check your current plan and view past invoices. Your credits work the same way regardless of where they come from, whether you use your **welcome credit**, purchase a plan, or add a **top-up**. ### **5. Explore plans and get help** Go to **Pricing** to explore the available plans. Looking for a **custom option**? Reach out to your **Account Manager** using the contact details in the bottom-left corner of the dashboard, or contact our **24/7 Support Team** for help. --- # 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/help-center/dashboard/navigating-the-dashboard.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.