> For the complete documentation index, see [llms.txt](https://help.proxidize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.proxidize.com/readme.md).

# Proxidize Help Center

Docs for Proxidize Mobile Proxies and Residential Proxies, including setup, rotation, targeting, API usage, billing, troubleshooting, and legacy support.

Get to the right guide fast.

Use this help center for setup, billing, troubleshooting, and API docs.

<p align="center"><button type="button" class="button primary" data-action="ask" data-icon="brain-circuit">Ask the Ai</button><a href="https://status.proxidize.com/" class="button secondary" data-icon="signal">Proxidize Status Page</a></p>

### Start with your goal

<table data-view="cards"><thead><tr><th>Title</th><th>Description</th><th data-card-target data-type="content-ref">Link</th></tr></thead><tbody><tr><td>Quick start</td><td>Pick a plan, get credentials, and test your first proxy.</td><td><a href="/getting-started/quick-start-with-proxidize-proxies.md">Quick Start with Proxidize Proxies</a></td></tr><tr><td>Choose a product</td><td>Compare mobile and residential proxies before you buy.</td><td><a href="/getting-started/choose-between-mobile-and-residential-proxies.md">Choose Between Mobile and Residential Proxies</a></td></tr><tr><td>Set up your proxies</td><td>Connect Proxidize proxies in browsers, tools, and scripts.</td><td><a href="/getting-started/setting-up-your-proxidize-proxies.md">Setting Up Your Proxidize Proxies</a></td></tr><tr><td>Manage billing</td><td>Handle subscriptions, invoices, payments, and account settings.</td><td><a href="/account-and-billing/overview.md">Overview</a></td></tr><tr><td>Use the API</td><td>Browse API endpoints for proxy management and settings.</td><td><a href="/proxidize-rest-api/proxidize-api.md">Proxidize API</a></td></tr></tbody></table>

### Explore by product

<table data-view="cards"><thead><tr><th>Title</th><th>Description</th><th data-card-target data-type="content-ref">Link</th></tr></thead><tbody><tr><td>Mobile Proxies</td><td>Managed U.S. mobile IPs with Per Proxy and Per GB plans.</td><td><a href="/proxidize-proxies/mobile-proxies.md">Mobile Proxies</a></td></tr><tr><td>Residential Proxies</td><td>Residential IPs across 195+ countries with sticky or rotating sessions.</td><td><a href="/proxidize-proxies/residential-pergb.md">Residential - perGB</a></td></tr><tr><td>Proxy Builder (Legacy)</td><td>Explore the help center for the Proxy Builder Platform.</td><td><a href="/legacy-products/proxy-builder.md">Proxy Builder</a></td></tr></tbody></table>

{% hint style="info" %}
New customers should start with Mobile Proxies or Residential Proxies.

Legacy docs stay available for existing Proxy Builder users.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.proxidize.com/readme.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.