> For the complete documentation index, see [llms.txt](https://docs.zooproxy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zooproxy.com/overview.md). # Overview Stable and clean network resources help your business operate efficiently. **Zooproxy** is a service platform focused on providing high-quality residential network resources. It is committed to providing stable and clean IP solutions to help users obtain target market information more smoothly and improve business operational efficiency. The platform currently offers three core solutions, which users can flexibly choose according to their actual needs: Dynamic Residential Traffic – Based on native home broadband networks, IP resources can be automatically rotated on demand. Suitable for large-scale public data collection, market information monitoring, and other scenarios. Long-Term Static IP – Provides long-term, fixed, clean residential IPs, ensuring consistency of network identity. Suitable for enterprises requiring a stable and persistent network environment, such as multi-account security management and cross-border e-commerce operations. Unlimited Traffic Package – No traffic cap, supports on-demand port expansion, meets various needs such as multi-tasking, public data collection, and daily operations. No need to worry about excess charges, flexibly adapting to changes in business scale. --- # 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.zooproxy.com/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.