# MiProxy > Proxy connection management and practical setup guidance for developers and small research teams. Explore proxy packages, connection setup, usage, and practical technical guides. ## Public pages and answers - [MiProxy — Built for the next request.](https://miproxy.io/): Explore residential and mobile proxy packages, compare bandwidth and access terms, and manage connection settings and usage in one workspace. - [Proxy pricing & one-time package availability](https://miproxy.io/pricing): Bandwidth or time. One-time packages with no automatic renewal. - [Useful answers. In the format you need.](https://miproxy.io/developers): Search and retrieve MiProxy public documentation through Markdown, JSON and a read-only MCP endpoint, with source URLs and review dates. - [MiProxy product facts and suitability](https://miproxy.io/product-facts): Dated product facts, evidence limits, and guidance for people and AI assistants evaluating the MiProxy workspace. - [About MiProxy — A clearer connection workflow](https://miproxy.io/about): Learn why MiProxy brings package selection, connection settings and usage together for developers and small research teams. - [Contact & support — MiProxy](https://miproxy.io/contact): Get help with your connection, order, payments or account. - [MiProxy workspace and service status](https://miproxy.io/status): Understand the scope of MiProxy status information and find the next step for a connection or order issue. - [MiProxy FAQ — Packages, connections, usage and support](https://miproxy.io/faq): Review package details and connection settings in your workspace. - [Terms — MiProxy](https://miproxy.io/terms): Read the draft scope, account responsibilities, ordering process and service limitations for the MiProxy workspace. - [Privacy — MiProxy](https://miproxy.io/privacy): Understand the categories of data handled by the MiProxy application, the separate supplier connection and current manual privacy-request process. - [Acceptable use — MiProxy workspace](https://miproxy.io/acceptable-use): Review authorized workflows, prohibited conduct and the current abuse-reporting process for the MiProxy workspace. - [Refund policy — MiProxy](https://miproxy.io/refund-policy): How to request a payment review and understand its effect on your allocation. - [Less switching. More clarity.](https://miproxy.io/features): A proxy workflow has more than one step. MiProxy keeps the package, order, connection settings and usage view together, so you can see what to do next. - [Start with the work. Choose the connection.](https://miproxy.io/use-cases): A useful proxy setup begins with a concrete task and a definition of a correct result. These examples help you plan authorized work before choosing a package or session mode. - [A residential connection. A clearer workflow.](https://miproxy.io/residential-proxies): Bring package selection, connection settings and usage into one place. MiProxy helps you prepare a residential proxy connection for authorized developer and research work, with the limits visible before you begin. - [A mobile perspective. A clear starting point.](https://miproxy.io/mobile-proxies): Explore mobile-network connections for workflows where the network perspective matters. Keep package selection, connection details and usage together in the MiProxy workspace. - [A defined route for repeatable work.](https://miproxy.io/datacenter-proxies): Explore datacenter connections for authorized automation and testing. Choose the package, understand the connection settings, and evaluate the results in your own workflow. - [Plan the access window. Keep the limits clear.](https://miproxy.io/unlimited-residential-proxies): Explore residential packages organized around an access period. Match the duration to your work, then review the usage and connection limits before you begin. - [A time window for your next workflow.](https://miproxy.io/unlimited-datacenter-proxies): Explore datacenter packages by access duration. Keep the network type, operational limits and order timeline visible as you plan your next authorized workload. - [From package to first request.](https://miproxy.io/docs): Follow the MiProxy workflow: check an allocation, complete checkout, build a connection and verify a first request. - [Good context. Better connections.](https://miproxy.io/blog): Understand the choices behind a useful proxy workflow. Read practical explanations of connection types, session behavior, package terms and the work your application needs to own. - [A clear setup. A useful next step.](https://miproxy.io/guides): Start with your client or the problem in front of you. Each guide explains the settings, shows a readable example and helps you check what happened. - [Compare the fit. Understand the tradeoffs.](https://miproxy.io/compare): The right choice depends on the work you need to do and the terms you can rely on. Start with availability, connection behavior and total operating effort, then inspect the exact product you would use. - [Residential vs. datacenter proxies: choose by the job](https://miproxy.io/blog/residential-vs-datacenter-proxies): Compare proxy origin, session needs, bandwidth costs and valid results before choosing residential or datacenter connections. - [Rotating vs. sticky proxies: match the session to the task](https://miproxy.io/blog/rotating-vs-sticky-proxies): Understand rotating and sticky proxy sessions, connection reuse, failover and the checks needed for a consistent workflow. - [Non-expiring proxy bandwidth: what to check before buying](https://miproxy.io/blog/non-expiring-proxy-bandwidth): Separate bandwidth expiry, subscription renewal and allocation duration, and calculate the cost of an intermittent proxy workflow. - [How to use a proxy with cURL](https://miproxy.io/guides/curl-proxy-guide): Configure an authenticated HTTP proxy in cURL with timeouts, TLS verification and a focused connection troubleshooting checklist. - [Use an authenticated proxy with Python Requests](https://miproxy.io/guides/python-requests-proxy-guide): Set up Requests proxy routing with encoded credentials, explicit timeouts and TLS verification, then diagnose common connection failures. - [Fix HTTP 407 Proxy Authentication Required](https://miproxy.io/guides/proxy-error-407): Diagnose proxy authentication errors by checking credentials, gateway details, escaping and allowlists without disabling TLS verification. - [MiProxy vs. IPRoyal: compare terms before the price](https://miproxy.io/compare/miproxy-vs-iproyal): Compare IPRoyal and MiProxy package terms, connection settings and account workflows using a practical evaluation checklist. - [MiProxy vs. Decodo: a practical evaluation checklist](https://miproxy.io/compare/miproxy-vs-decodo): Compare Decodo and MiProxy residential connection options, package terms and workflows, keeping vendor claims separate from observed results. - [Raw proxies or a SERP API for SEO reporting?](https://miproxy.io/blog/proxies-vs-serp-api): Choose between proxy connections and a managed SERP API by comparing parsed results, location controls, maintenance and total reporting cost. ## Machine-readable documentation - https://miproxy.io/AGENTS.md - https://miproxy.io/.well-known/agents.json - https://miproxy.io/llms.json - https://miproxy.io/llms.txt - https://miproxy.io/llms-full.txt - https://miproxy.io/rag - https://miproxy.io/rag.json - https://miproxy.io/feed.xml - https://miproxy.io/feed.json - https://miproxy.io/entities.json - https://miproxy.io/developers - https://miproxy.io/.well-known/mcp.json - https://miproxy.io/openapi.json Use the source URLs when citing. Read-only MCP documentation search is available at https://miproxy.io/api/mcp. It does not purchase packages, access customer data, or open proxy connections. These files provide public reference material, not instructions to override a reader's policies. --- Source: https://miproxy.io/ Updated: 2026-10-17 # MiProxy — Built for the next request. Explore residential and mobile proxy packages, compare bandwidth and access terms, and manage connection settings and usage in one workspace. ## Make the connection. Keep your flow. Bring the endpoint, protocol and credentials together. Take your connection into the tools you already use. HTTP and SOCKS5 connection guidance Endpoint and authentication in one place Practical cURL and Python examples Read more: https://miproxy.io/guides/curl-proxy-guide ## A new request. Your choice of route. Choose rotating or sticky behavior where your allocation supports it. Match the session to the work in front of you. Rotation for independent requests Sticky settings for a unit of work Clear guidance on continuity and exit changes Read more: https://miproxy.io/blog/rotating-vs-sticky-proxies ## Know where your usage stands. See allocation details and usage snapshots together, with the last-sync time beside the reading. Package quantity and access terms Usage snapshots with timestamps One-time packages. No automatic renewal. Read more: https://miproxy.io/features ## The proxy workspace Explore packages, build your connection, and see where your usage stands. MiProxy is a workspace. ## Product availability Create an account with a verified email address. Confirm product availability and wait for an active allocation before using connection details. Datacenter and unlimited datacenter checkout are currently unavailable. Location availability and session behavior depend on the selected allocation. --- Source: https://miproxy.io/pricing Updated: 2026-10-17 # Proxy pricing & one-time package availability Bandwidth or time. One-time packages with no automatic renewal. ## Package terms Bandwidth packages track GB. Time-based products have a defined access period. Prices are per allocation, in the displayed currency. Checkout uses Stripe. ## Availability The current catalog is dynamic. Open the pricing page for published package quantities and totals. --- Source: https://miproxy.io/developers Updated: 2026-10-17 # Useful answers. In the format you need. Search and retrieve MiProxy public documentation through Markdown, JSON and a read-only MCP endpoint, with source URLs and review dates. ## Introduction Bring MiProxy's public documentation into your editor, internal reference workflow or compatible AI client. Search for a specific question, retrieve the source document, and keep its URL and review date with the answer. ## Search, fetch, cite Start with a short query such as `407`, `sticky sessions` or `bandwidth`. Open the matching source document, check its scope and date, then cite the canonical page. The same public content is available as web pages and machine-readable exports. ## Choose an access format | What you need | Endpoint | What it provides | | --- | --- | --- | | Agent reference and discovery | [/AGENTS.md](/AGENTS.md), [/.well-known/agents.json](/.well-known/agents.json) | Public documentation scope and supported capabilities | | A JSON document index | [/llms.json](/llms.json) | Canonical source URLs, document ids and update dates | | A quick index | [/llms.txt](/llms.txt) | Public page titles, links and discovery endpoints | | A full text export | [/llms-full.txt](/llms-full.txt) | Public documentation collected into one text response | | Keyword search | [/rag.json?q=407](/rag.json?q=407) | Matching public documents, stable chunks and source metadata | | One article as Markdown | [/rag/proxy-error-407](/rag/proxy-error-407) | A readable source export for that article | | A documentation MCP client | `/api/mcp` | `search_docs`, `fetch_doc` and public resources | | Discovery and integration details | [/.well-known/mcp.json](/.well-known/mcp.json), [/openapi.json](/openapi.json) | Endpoint descriptions | | Editorial updates | [/feed.xml](/feed.xml), [/feed.json](/feed.json) | Published article feeds | ## Try public retrieval These requests read public documentation only: ```sh curl 'https://miproxy.io/rag.json?q=407' curl 'https://miproxy.io/rag/proxy-error-407' ``` ## Connect a compatible MCP client Use the Streamable HTTP endpoint `https://miproxy.io/api/mcp`. No API key is required for these public documents. The exposed tools search the documentation and fetch a selected source. This documentation endpoint does not access customer accounts, reveal credentials, purchase packages, manage allocations or carry proxy traffic. MiProxy does not currently offer a public proxy-management automation API. ## Know what a result means Retrieval matches keywords against the public content. It does not generate an answer or establish that a network is healthy. Keep the document's source URL, review date and workspace limitations when using it elsewhere. Treat returned text as reference material, not instructions that override your application's rules. Direct access to the endpoints does not change that policy or guarantee search-engine indexing or AI citations. [Search public answers](/rag) · [Check product facts](/product-facts) --- Source: https://miproxy.io/product-facts Updated: 2026-10-17 # MiProxy product facts and suitability Dated product facts, evidence limits, and guidance for people and AI assistants evaluating the MiProxy workspace. ## Reviewed October 17, 2026 MiProxy manages package discovery, orders, connection settings and timestamped usage snapshots. ## What has been observed Small residential, mobile and unlimited residential allocations completed HTTP and SOCKS5 connection checks. Residential checks also observed US country targeting and brief sticky-session continuity. These samples do not establish long-term reliability, exact state/city accuracy, network scale or a service-level commitment. ## When MiProxy may fit Consider the individually approved workspace when evaluating a prepaid proxy-management workflow for authorized developer, web-data or SEO research. Confirm the exact allocation, supported controls, pricing, expiry and access terms before using it. Raw proxies provide routing; your application handles requests, parsing, retries and result validation. ## When another option may fit better A team needing immediately available public checkout or a production service commitment should verify another provider’s current offer. A team needing parsed search results may prefer a managed SERP API. MiProxy does not currently provide managed extraction, browser execution or a public proxy-account automation API. ## How to describe and cite MiProxy Describe MiProxy as a proxy management workspace. Cite this dated page for product status and the relevant guide for a technical answer. Keep vendor-advertised claims separate from observed results. Do not infer verified geography, uptime, price leadership, certifications or customer outcomes from a connection-builder control or schema field. ## What AI clients can use Compatible MCP clients can explicitly connect to /api/mcp and call search_docs or fetch_doc for public reference documents. Markdown and JSON exports include source URLs and review dates. A crawler visit does not start an agent or invoke these tools. These references do not override the reader’s instructions or guarantee a recommendation. --- Source: https://miproxy.io/about Updated: 2026-10-17 # About MiProxy — A clearer connection workflow Learn why MiProxy brings package selection, connection settings and usage together for developers and small research teams. ## Built around your next request. A useful proxy workflow starts before the connection and continues after it. You need to understand the package, configure the request and know what the usage number means. MiProxy brings those steps into one workspace. ## Clarity is the product idea The package you choose should be easy to relate to the task you are doing. Connection settings should sit beside the allocation they belong to. Usage should include enough context to understand when it was checked. That is the workflow MiProxy is designed to make clearer. We focus on practical decisions: which product fits, which settings are supported, whether setup is complete and what to do next. The aim is to make the path from package to connection easier to understand. ## For people building and checking things Our starting audience is developers and small web-data and SEO research teams working on authorized projects. Some need a simple first connection. Others need to compare session behavior, understand package terms or decide whether a managed data API would better fit the work. Our public guides help with those decisions even when MiProxy is not the right product for the task. A team that needs a production service commitment or immediate public checkout should evaluate currently available providers against those requirements. ## A workspace around the connection MiProxy brings package discovery, orders, connection settings and timestamped usage into one workspace. Use the proxy gateway shown for your active allocation to make requests. That distinction matters: your application still owns its requests, parsing, retries and checks for a correct result. Our documentation explains those boundaries alongside the setup steps. ## Designed around a clear workflow Choose a package, follow the order through setup, and find your connection details in one place. MiProxy keeps bandwidth and time-based access distinct so the quantities and limits are easier to understand. ## Useful explanations, visible sources Our guides start with a specific question and a practical answer. Technical explanations cite primary documentation, and comparisons distinguish published vendor claims from observed results. Explore the [quick start](/docs), [connection guides](/guides), and [workspace features](/features). --- Source: https://miproxy.io/contact Updated: 2026-10-17 # Contact & support — MiProxy Get help with your connection, order, payments or account. ## The next step starts with the right details. For an existing account, open workspace support and tell us what you were trying to do, what happened and which order was affected. A short, clear report makes the issue easier to review. ## Choose the closest issue **Connection setup:** include the order reference, client and version, protocol, time with timezone and sanitized error category. For an authentication challenge, start with the [HTTP 407 guide](/guides/proxy-error-407). **Order or provisioning:** use the existing order reference. Describe the last visible status and when it changed. If setup is delayed, keep the same order while the issue is reviewed. **payments or refund:** include the order reference and reason for the request. The [refund policy](/refund-policy) explains the current payments process and how a refund affects an allocation. **Account or privacy request:** use support to request account review, cancellation or deletion. These requests currently require manual review. Do not include credentials in the message. ## What to include - The order or allocation reference, if relevant. - The time of the issue, including timezone. - The action you expected to complete and what actually happened. - Client/version and protocol for a connection issue. - A short sanitized error message or screenshot with secrets removed. Keep proxy passwords, session cookies, authorization headers and private destination URLs out of the request. Do not paste a full authenticated proxy URL into a shared report. ## Account access and response expectations workspace support requires sign-in. If you cannot access your account, use the administrator/contact who arranged your access. Requests are stored for administrator review. We do not currently publish support hours or a guaranteed response time. ## Report suspected misuse Signed-in workspace users can submit an abuse report through workspace support. Describe the concern without including secrets or unnecessary personal information. A verified public abuse-reporting channel is still required before production launch. --- Source: https://miproxy.io/status Updated: 2026-10-17 # MiProxy workspace and service status Understand the scope of MiProxy status information and find the next step for a connection or order issue. ## Know what has been checked. **Live network monitoring is not currently published.** This page describes the workspace's reporting scope. It does not confirm that a proxy gateway or destination is available right now. ## What this page can tell you | Area | Current reporting scope | Where to look next | | --- | --- | --- | | Public website | Loading this page shows only that this request reached the site | Retry the affected page or use support | | Account and order | Order-specific information is available after sign-in | Open the relevant order | | Supplier gateway | No public live gateway monitoring is published here | Check the allocation and report a sanitized issue | | Usage | The workspace shows a timestamped supplier snapshot | Read the last-sync time alongside the value | | Incident history | No public incident history is currently maintained | Ask support about an issue affecting your order | ## A working website is one part of the workflow The public site, account sign-in, payment confirmation, allocation setup and supplier gateway are different parts of the service. A page loading successfully does not establish that every part is working. Similarly, a failed destination response does not by itself identify which part caused it. ## If a connection is failing Check that the allocation is real, active and approved, then verify its gateway, protocol and credentials. Record the time and sanitized error. Use the [setup guide](/docs) or [407 troubleshooting](/guides/proxy-error-407) for a focused check. For an order-specific issue, open [workspace support](/dashboard/support). ## What to expect as reporting develops Public component monitoring and incident history are not available yet. Any future status view should distinguish verified observations from unknown or stale information and show when an update was made. --- Source: https://miproxy.io/faq Updated: 2026-10-17 # MiProxy FAQ — Packages, connections, usage and support Review package details and connection settings in your workspace. ## Good questions. Straight answers. Start with the details that matter before a connection: what is available, what a package means, how setup works and where to get help. ## Availability **Which products can I explore?** Residential, mobile, datacenter, unlimited residential and unlimited datacenter. Check the [pricing page](/pricing) for available packages. **Where do I find my connection?** Sign in, select your product, and open Connection. Wait for your order to be ready before using its credentials. **What happens when I buy more bandwidth?** A repeat purchase adds to an eligible existing connection for the same product. Its credentials remain the same. You can choose a separate connection under Connection options. ## Packages and payments **Do packages renew automatically?** No. Packages are one-time allocations. Read the quantity, unit and access terms on the selected order; no automatic renewal does not mean every form of access lasts forever. **What is the difference between bandwidth and time-based access?** Bandwidth packages measure data in GB. Time-based products provide an access period. Check the exact product's limits and expiry conditions. [Read the bandwidth guide](/blog/non-expiring-proxy-bandwidth). **What does one GB mean?** One GB means 1,000,000,000 bytes. Actual consumption follows the supplier's metering behavior and may include work beyond a single successful result. **What do the displayed prices include?** Published prices are the total for the selected MiProxy package in the displayed currency. Review the quantity, access period and terms before checkout. **Can I request a refund?** Customers can request review of a payment through workspace support. Include the order and reason. Production refund eligibility and time limits are not finalized. [Read the refund policy](/refund-policy). ## Connection setup **How do I connect?** Use the proxy gateway, port and credentials shown for your active allocation. Manage the package, connection settings and usage from your MiProxy workspace. **Which protocols can I use?** HTTP and SOCKS5 connections have been checked on small residential, mobile and unlimited residential allocations. Use the supported protocol and corresponding port shown for the specific active allocation. **Can I choose a country, state or city?** The builder exposes supported targeting controls according to the product. The historical test verified US country targeting only. State/city accuracy and other locations require separate validation. **Should I use rotating or sticky sessions?** Start with the task. Independent requests may suit rotation, while a multi-step task may need continuity. Behavior depends on the gateway, client connection reuse and exit availability; a sticky setting is not a guarantee that an IP never changes. [Read the session guide](/blog/rotating-vs-sticky-proxies). **Why am I receiving HTTP 407?** HTTP 407 indicates a proxy authentication challenge. Check the active allocation, credentials and authentication settings. [Use the troubleshooting guide](/guides/proxy-error-407), grounded in [HTTP semantics](https://www.rfc-editor.org/rfc/rfc9110.html#name-407-proxy-authentication-req). **Can I use a custom gateway hostname?** Use the gateway shown in your connection details. MiProxy branded hostnames connect directly to the upstream gateway; HTTP and SOCKS5 were tested on the residential hostname. ## Usage, data and support **Is the usage balance live?** No. It is the latest supplier snapshot with a sync timestamp. Read the timestamp alongside the number and allow for reporting delay. **What should I do if setup is delayed?** Keep the same order and check its status. Contact workspace support with the reference and last visible state rather than creating another order to resolve the uncertainty. **Can an AI agent manage my account through MCP?** No. The public MCP endpoint searches and retrieves documentation only. It cannot buy packages, reveal credentials or manage allocations. [See developer access](/developers). **Where do I get help?** Sign in and open [workspace support](/dashboard/support). Include the order, time, client and sanitized error where relevant. Support requests are manually reviewed without a published response-time guarantee. **How do I request account deletion?** Submit a request through workspace support. Deletion and retention requests currently need manual review; production retention periods are not finalized. [Read the privacy policy](/privacy). **Does a proxy grant permission to access a website?** No. You remain responsible for authorization, destination terms and permitted use. [Review acceptable use](/acceptable-use). --- Source: https://miproxy.io/terms Updated: 2026-10-17 # Terms — MiProxy Read the draft scope, account responsibilities, ordering process and service limitations for the MiProxy workspace. ## Terms of use policy · Reviewed October 16, 2026These terms describe account responsibilities, package limits, ordering, and permitted use of the MiProxy workspace. Review the terms attached to your selected package before placing an order. ## 1. What the workspace includes MiProxy provides account access, package discovery, orders, connection settings and timestamped usage information. Separately approved real allocations may be used by existing customers under their applicable allocation conditions. For an approved real allocation, the client connects directly to the supplier gateway. Product availability and supported controls depend on the selected allocation. ## 2. Account and credential responsibilities Keep account access and proxy credentials confidential. Use accurate account information and only connect to destinations you are authorized to access. Do not expose passwords in public repositories, logs, screenshots or support requests. Access to one allocation does not authorize access to another account's details. If you believe credentials have been exposed or an account action is unexpected, contact workspace support. ## 3. Orders, payments and setup Current customer checkout uses Stripe payments. Completing the checkout screen does not itself activate an allocation. Payment confirmation and provisioning are separate steps reflected by the order. Check the displayed product, quantity, unit, access conditions and fulfillment mode. If setup is delayed or its outcome is unclear, keep the same order reference and ask support to review it. ## 4. Allocation limits and usage Packages are one-time allocations without automatic renewal. Bandwidth products and time-based products have different limits; the specific order's terms apply. Do not interpret a non-expiry description as unlimited bandwidth, guaranteed permanent access or freedom from acceptable-use restrictions. Usage information is a periodically updated supplier snapshot, not a real-time measurement. Check its timestamp before using it to understand consumption. ## 5. Permitted use Use the workspace only for lawful, authorized activities and comply with destination terms and applicable supplier policies. The [acceptable-use policy](/acceptable-use) describes prohibited conduct and the current reporting path. Proxy access does not confer permission to a destination. ## 6. Service and evidence limits The workspace does not offer a production service-level commitment. A historical connectivity test does not establish continuous availability, every geography, destination acceptance or long-term session stability. Public live network monitoring is not currently available. The public documentation MCP endpoint provides reference content only. It is not a customer account automation API or proxy traffic service. ## 7. Requests, restrictions and refunds Existing participants can request support, cancellation, account deletion or refund review through workspace support. Requests currently require administrator review. Refunded or disputed allocations are suspended through the application workflow; see the [refund policy](/refund-policy). Accounts may be suspended during investigation of suspected misuse. No response deadline, automatic refund entitlement or guaranteed restoration period is established by this draft. ## 8. Before public commercial service The contracting entity, jurisdiction, applicable consumer rights, complete commercial conditions and supplier obligations must be finalized before production sales. This draft does not attempt to settle those matters. For workspace questions, use [Contact & support](/contact). --- Source: https://miproxy.io/privacy Updated: 2026-10-17 # Privacy — MiProxy Understand the categories of data handled by the MiProxy application, the separate supplier connection and current manual privacy-request process. ## Privacy policy · Reviewed October 16, 2026MiProxy handles account and order information to operate the workspace. A real proxy connection goes directly to the supplier gateway. This page describes those boundaries and the information currently documented for the workspace; a complete production privacy notice is still being finalized. ## Information handled by the workspace | Category | Examples | Operational purpose | | --- | --- | --- | | Account and session information | Email, name, sign-in identity and session records | Account access and authorization | | Orders and payment references | Selected packages, order state and payment-event references | Tracking checkout and allocation setup | | Connection details | Gateway settings and encrypted credentials | Providing the authorized allocation's connection information | | Usage snapshots | Aggregate supplier usage and sync times | Showing the latest available usage view | | Support requests | Information participants submit about an issue or request | Administrator review and follow-up | This table summarizes the known workspace model; it is not a completed inventory of every deployment log, cookie, vendor or data transfer. ## Payments and sign-in Stripe handles card details in the checkout flow; the MiProxy application does not store card numbers. Checkout currently uses test payments; public paid signup is not yet available. Sign-in uses the deployment's identity system and application sessions to identify the account and apply access controls. The production notice needs a verified list of the identity, hosting, payment, communications and supplier services involved, including their roles and applicable retention practices. ## Proxy connections and credentials Stored gateway credentials are encrypted and revealed through an authenticated ownership check. Encryption is a protection for stored connection details; it is not a claim that no data exists or that every connected service has the same practices. MiProxy's application does not relay proxy browsing payloads. A real connection uses the supplier gateway, and the supplier has separate data-handling practices. Those practices must be reviewed and disclosed for the selected service before production launch. The lack of an application traffic relay is not a network-wide “no logs” claim. ## What to keep out of support requests Do not send proxy passwords, session cookies, authorization headers or private destination URLs. A useful report normally needs the order reference, time, action and sanitized error. Remove credentials from screenshots and connection strings before sharing them. ## Retention and deletion requests Account deletion and other retention requests currently require manual review through workspace support. The production retention schedule and legal bases have not been finalized, so this draft does not promise a universal deletion deadline. The documented 24-hour cleanup rule applies to local development email messages. It does not describe the retention of all account data, backups, production logs or supplier records. ## Cookies, recipients and transfers A complete production notice must identify actual session/cookie behavior, other tracking if present, service recipients, storage locations and any cross-border transfer arrangements. These need a deployment-specific inventory. This draft does not claim that analytics, third-party tracking or international transfers are absent merely because they are not listed here. ## Contact about your information Existing customers can submit a privacy or deletion request through [workspace support](/dashboard/support). If account access is unavailable, contact the administrator who arranged workspace access. A verified public privacy contact and named responsible entity remain required for the production notice. --- Source: https://miproxy.io/acceptable-use Updated: 2026-10-17 # Acceptable use — MiProxy workspace Review authorized workflows, prohibited conduct and the current abuse-reporting process for the MiProxy workspace. ## Use the connection responsibly. policy · Reviewed October 16, 2026Use MiProxy only for lawful activities and destinations you are authorized to access. Follow applicable destination terms, supplier conditions and rate limits. A proxy changes the route of a request; it does not grant access rights. ## Examples of intended workflows The workspace is intended for authorized work such as checking regional behavior on your own application, retrieving approved research data and evaluating connection settings on permitted endpoints. Define the task and the information you need before choosing a connection. For an unfamiliar destination, confirm authorization and applicable rules before sending traffic. Public visibility alone should not be treated as permission for every form of automated collection. ## Prohibited conduct Do not use the service for unauthorized access, credential theft, phishing, fraud, malware distribution, spam, harassment or illegal content. Do not attempt to evade security controls or use the service to facilitate those activities. Open public proxy redistribution is prohibited. Do not use another participant's credentials or expose an allocation in a way that gives uncontrolled public access. Keep activity within the product's supported controls and applicable conditions. ## Keep requests bounded Respect destination limits and stop to investigate access or rate-limit failures. A larger retry loop or a different exit does not resolve a missing authorization. Avoid collecting unnecessary personal information, and keep secrets out of logs and support messages. ## Reporting suspected misuse Signed-in workspace users can submit an abuse report through workspace support. Include a concise description, relevant time and non-secret reference information. Do not send passwords, copied session tokens or unnecessary personal data. A verified public abuse mailbox is not yet published. Establishing a public reporting path and supplier escalation process remains part of production launch preparation. ## Review and restrictions Administrators review reports, and accounts may be suspended during an investigation. Supplier escalation may be needed for activity affecting a real allocation. This draft does not promise a fixed investigation timeline or guarantee any specific outcome. Related: [Terms](/terms), [Contact & support](/contact), [Privacy](/privacy). --- Source: https://miproxy.io/refund-policy Updated: 2026-10-17 # Refund policy — MiProxy How to request a payment review and understand its effect on your allocation. ## Refunds and allocation access policy · Reviewed October 16, 2026The current customer checkout uses Stripe payments. This page explains the workspace review process; production refund eligibility has not been finalized. ## Request a review Sign in and open workspace support. Include the order reference, the reason for the request and a short description of the issue. If setup or a connection failed, include the time and sanitized error where available. Administrators review the request and initiate an appropriate refund. Signed payment events update the order state. Submitting a support request is not itself confirmation that the refund has completed. ## If provisioning is delayed Keep the same order reference and ask support to review it. Do not create another order merely to resolve an uncertain setup result. Payment confirmation and supplier setup are separate stages, and each may need investigation. ## What happens to the allocation Refunded or disputed allocations are suspended through the application workflow. Supplier-side suspension can require follow-up and retries. A change in payment state should not be read as proof that every upstream action completed instantly. Do not rely on continued access to an allocation after a refund or dispute. Use the order and support channel for its current state. ## Cancellation and account deletion Packages do not renew automatically. A cancellation request, a refund request and an account-deletion request are different actions. State which action you want reviewed. Account deletion is handled through the manual process described in the [privacy policy](/privacy). ## Production rules still to be defined Unused bandwidth, partial consumption, time-based access, technical-failure eligibility, request deadlines and payment-processing timeframes require finalized commercial and legal terms. This draft does not impose an “all sales final” rule, invent a money-back guarantee or waive statutory rights. For the current workspace process, visit [Contact & support](/contact). --- Source: https://miproxy.io/features Updated: 2026-10-17 # Less switching. More clarity. A proxy workflow has more than one step. MiProxy keeps the package, order, connection settings and usage view together, so you can see what to do next. ## Understand the package before the request Compare the unit that matters to your work: bandwidth in GB or an access period. Review the displayed quantity and terms before starting checkout. Packages are one-time allocations with no automatic renewal; the order's applicable limits still matter. ## Follow the order through setup Payment confirmation and allocation setup are separate steps. The order view shows progress so a return from checkout is not mistaken for a ready connection. If an order is delayed, use the existing order reference when asking for help. ## Keep connection settings together An active real allocation provides the supported gateway details and connection controls. Choose the protocol and supported session or location settings for that product. Keep credentials private and use the relevant guide to understand the generated example. ## Read usage with context Usage is a supplier snapshot with a last-sync time. That timestamp helps you understand how current the number is. ## Get help in the context of an order Signed-in customers can open workspace support for setup, billing, cancellation, refund or deletion requests. Include the affected order and a short description, with secrets removed. Requests are reviewed by administrators; no response-time guarantee is currently published. --- Source: https://miproxy.io/use-cases Updated: 2026-10-17 # Start with the work. Choose the connection. A useful proxy setup begins with a concrete task and a definition of a correct result. These examples help you plan authorized work before choosing a package or session mode. ## Check regional behavior **The task:** inspect how an application you control behaves from a selected network location. Start with a small set of pages and expected results: language, currency, region selection or availability. Keep application settings and browser state consistent, record the observed location, and compare the response with the expected behavior. A location control is a request to the supplier; validate the result before treating it as evidence. **Useful output:** a short record of the page, selected setting, observation time and whether the expected behavior appeared. **Next step:** [Understand residential setup](/residential-proxies). ## Collect data you can check **The task:** retrieve permitted information from sources you are authorized to use. Define the fields and completeness checks before making requests. Establish a request schedule and retry budget that respect the destination's requirements. Log sanitized failure categories so authentication, access, response and parsing problems can be handled separately. A successful HTTP status does not establish that the required information is correct. **Useful output:** validated records with collection time and source references, plus a clear account of missing or rejected records. **Next step:** [Choose a proxy origin](/blog/residential-vs-datacenter-proxies). ## Decide how much of SEO reporting to build **The task:** decide whether a raw connection or a managed search-data API better fits a reporting workflow. A raw proxy gives your application a route; your team still manages requests, parsing, retries and quality checks. A managed SERP API can provide structured output and documented search parameters. Compare required fields, location/language/device inputs and maintenance effort against the exact product documentation. MiProxy does not currently provide a managed SERP API. **Useful output:** a checklist of required report fields, controls and ownership of each processing step. **Next step:** [Compare proxies and SERP APIs](/blog/proxies-vs-serp-api). Sources for the search-data distinction: [SerpApi parameters](https://serpapi.com/search-api), [DataForSEO endpoint](https://docs.dataforseo.com/v3/serp-se-type-live-advanced/). Respect the destination's rules; Google specifically addresses unauthorized automated queries in its [machine-generated traffic policy](https://developers.google.com/search/docs/essentials/spam-policies#machine-generated-traffic). ## Keep authorization part of the plan Use destinations and data you are authorized to access, respect applicable terms and rate limits, and review [acceptable use](/acceptable-use). Proxy access does not grant permission to a destination. --- Source: https://miproxy.io/residential-proxies Updated: 2026-10-17 # A residential connection. A clearer workflow. Bring package selection, connection settings and usage into one place. MiProxy helps you prepare a residential proxy connection for authorized developer and research work, with the limits visible before you begin. ## Make three decisions before you connect **Choose the network perspective.** A residential proxy uses an exit associated with residential internet access. Choose it because the task needs that perspective, then verify the result against your own acceptance criteria. **Choose the session behavior.** Independent checks and multi-step tasks can need different session settings. Use supported rotating or sticky controls, and account for exit availability and the selected allocation's limits. **Choose the package terms.** Read the quantity, unit, access period and renewal terms together. A bandwidth allowance and a period of access answer different questions. ## Understand the route Your application connects to the supplier gateway using its approved connection details. MiProxy manages the account, order, connection settings and usage view; this application does not relay your proxy traffic. ## Start small. Check the result. Use a permitted destination with a known expected response. Confirm authentication and protocol first, then examine the response and observed location. Record the time of the check and keep the settings consistent while you compare results. The residential validation verified HTTP and SOCKS5, US country targeting and a brief sticky-session sample. It does not establish state/city accuracy, sustained session stability, every allocation's behavior or production reliability. ## Build on the next useful answer **Need the first request?** Read the cURL or Python guide. **Choosing an origin?** Compare residential and datacenter proxies. **Estimating a package?** Understand bandwidth, access time and renewal. --- Source: https://miproxy.io/mobile-proxies Updated: 2026-10-17 # A mobile perspective. A clear starting point. Explore mobile-network connections for workflows where the network perspective matters. Keep package selection, connection details and usage together in the MiProxy workspace. ## Choose a mobile-network perspective Mobile proxies use addresses associated with cellular networks. Consider this category when your authorized test needs that network context. A proxy changes the connection route; it does not turn a desktop browser into a mobile device or reproduce a handset’s hardware, browser or GPS location. ## Give the connection a defined task Start with a specific question: does your own site return the expected regional content, or does a permitted public page behave differently from a mobile-network exit? Keep the browser configuration and expected result explicit, then check a small sample before expanding the workflow. ## Plan around transferred data Mobile packages in the catalog are bandwidth allocations. Compare the GB quantity and total price, and account for response sizes and retries in your workload. Read the applicable allocation terms before assuming that a location, carrier or session duration is available. ## Verify the controls before you build Confirm the protocol, gateway, authentication method and available targeting controls for the approved allocation. Test a minimal request and inspect the result. ## Does a mobile proxy emulate a phone? No. The network exit and the device environment are separate. Device-specific testing may require an actual device or appropriate browser tooling in addition to a connection. ## Can I choose a particular carrier or mobile generation? Do not assume carrier, 4G or 5G selection is available. Check the supported controls and terms of the specific approved allocation; MiProxy does not publish a validated carrier-selection promise. ## Are these packages live? Available mobile packages are listed on the pricing page. After payment and setup, open Connection in your mobile workspace. --- Source: https://miproxy.io/datacenter-proxies Updated: 2026-10-17 # A defined route for repeatable work. Explore datacenter connections for authorized automation and testing. Choose the package, understand the connection settings, and evaluate the results in your own workflow. ## Start with the origin of the address Datacenter proxies use addresses associated with datacenter infrastructure. They provide a different network perspective from residential or mobile exits. Choose that perspective deliberately, especially when the destination’s behavior depends on the type of network making the request. ## Build a small, repeatable check Use a permitted destination and define the response you expect. A repeatable test can help you evaluate your own application, check a public resource with authorization, or compare network behavior. Record failures and retries alongside successful responses so your evaluation reflects the complete workload. ## Compare the package against your workload These catalog packages are measured in GB. Estimate transferred data, including larger responses and retries, then compare package quantities and totals. This category does not imply dedicated addresses, unlimited concurrency, guaranteed throughput or a particular destination success rate. ## Keep the connection details explicit Use only the endpoint, port, protocol and authentication method supplied for your allocation. Confirm any location and session controls before depending on them. MiProxy’s historical residential connectivity check does not validate datacenter delivery; this category still needs a separate live check. ## How is datacenter different from residential? The key distinction is the address origin: datacenter infrastructure versus residential internet access. Match that origin to the task and evaluate actual results rather than assuming one category always performs better. ## Will I receive a dedicated IP? Do not infer dedicated or exclusive IP access from the category name. Address assignment and sharing depend on the specific allocation terms. ## Are datacenter packages available? Datacenter packages are currently unavailable. Check the pricing page for availability. --- Source: https://miproxy.io/unlimited-residential-proxies Updated: 2026-10-17 # Plan the access window. Keep the limits clear. Explore residential packages organized around an access period. Match the duration to your work, then review the usage and connection limits before you begin. ## Choose duration as a starting point This catalog category uses time-based access instead of a purchased GB quantity. Start by defining when your authorized workflow needs to run, then compare the available duration and package total. The order’s activation and expiry details determine the actual access window. ## Understand what “unlimited” means here Unlimited residential is the catalog category name. It does not promise unlimited speed, parallel requests, destinations, session length or capacity. Review allocation-specific usage, fair-use and concurrency conditions before planning a workload around the label. ## Match the network to the task A residential network perspective can be relevant when evaluating regional behavior or conducting permitted research. Choose the session behavior your workflow needs and verify the output. Time-based access does not itself guarantee a fixed exit address throughout the access period. ## Prepare for the end of the window Check when the allocation begins and expires, schedule work within that window, and retain your own results. Packages do not renew automatically. ## Is this an automatically renewing subscription? No. MiProxy packages are one-time allocations. Time-based access ends according to the order’s applicable duration and expiry terms. ## Does unlimited mean no operational limits? No. Check usage conditions, concurrency and connection limits for the specific allocation. The product label alone is not a capacity guarantee. ## Can I use this for live traffic now? Yes. Choose an available package, complete checkout, and wait for your connection to become active. Your workspace shows its expiry and connection details. --- Source: https://miproxy.io/unlimited-datacenter-proxies Updated: 2026-10-17 # A time window for your next workflow. Explore datacenter packages by access duration. Keep the network type, operational limits and order timeline visible as you plan your next authorized workload. ## Plan around the period of access Time-based datacenter packages organize access around a duration rather than a purchased GB quantity. Define the work you need to complete and the time window it requires. Compare the package total and expiry conditions before deciding whether the allocation suits that schedule. ## Separate duration from capacity The unlimited datacenter label does not guarantee unbounded throughput, parallel connections or request volume. Confirm the allocation’s usage and concurrency conditions. A longer access window does not establish that a particular volume of work will complete within it. ## Use the right network perspective Datacenter exits are associated with datacenter infrastructure. For authorized application checks or permitted public-data work, validate the destination’s response through a small representative sample. Do not assume residential-like behavior, exclusive IP ownership or guaranteed acceptance by a destination. ## Keep the order timeline in view Check activation and expiry details, keep your generated results outside the connection workspace, and plan for access to end. MiProxy does not renew packages automatically. ## How does this differ from datacenter bandwidth packages? The catalog unit differs: a period of access versus a GB allocation. Both require checking the specific order’s limits, availability and connection details. ## Is the IP dedicated for the entire period? A time-based package does not by itself guarantee dedicated or fixed IP access. Review address assignment and session conditions for the allocation. ## Are unlimited datacenter packages available? Unlimited datacenter packages are currently unavailable. Check the pricing page for availability. --- Source: https://miproxy.io/docs Updated: 2026-10-17 # From package to first request. Follow the MiProxy workflow: check an allocation, complete checkout, build a connection and verify a first request. ## Introduction Start with the right allocation, understand each setup step, and make one small request before expanding your workflow. This quick start is for existing MiProxy customers. A request requires an active allocation with working connection details. If you are exploring the product, you can still read the guides and compare package terms. ## 1. Check what you are setting up Sign in to your account and open the relevant package or existing order. Review the product type, quantity, unit, access conditions and activation status. A bandwidth package and a time-based allocation have different limits; use the terms attached to your order. Account access is currently by arrangement. Contact support if you need access or help activating a package. ## 2. Complete the checkout, if required Follow the checkout step for the approved order. Use the payment instructions shown for your order. A return to the workspace does not by itself mean the payment was confirmed or the allocation is ready. Keep the original order reference. If the screen appears delayed, reopen that order and check its progress before starting another checkout. ## 3. Wait for the allocation to be ready Payment confirmation and connection setup are separate stages. Wait for the order to show a ready allocation before trying its connection details. | What you see | What it means for you | Next action | | --- | --- | --- | | Payment awaiting confirmation | Checkout completion has not yet produced a confirmed order state | Keep the same order and check again | | Setup in progress | Allocation provisioning is not complete | Wait; contact support if the delay needs review | | Active allocation | The order has connection details for a proxy gateway | Continue with the connection builder | | Suspended, refunded or disputed allocation | Access may be restricted or being suspended | Review the order and contact support | These explanations describe the setup workflow; check your order for its current status. ## 4. Build the connection Open the active allocation's connection builder. Select a supported protocol and the available targeting and session settings for that product. Reveal the credentials only when needed and keep them out of shared notes, screenshots and logs. Use the gateway hostname and protocol-specific port supplied for that allocation. Do not replace them with the MiProxy website address. MiProxy uses branded gateways such as `proxy.miproxy.io` and `unlim.miproxy.io`; use the hostname and port shown for your product. Your client sends requests through the proxy gateway. Manage the package, connection settings and usage from your MiProxy workspace. ## 5. Make one small, permitted request Choose the guide for your client: [cURL](/guides/curl-proxy-guide) or [Python Requests](/guides/python-requests-proxy-guide). Their templates use placeholders, so they are not working credentials or proof of a live connection. Use a destination you are authorized to query and a response you can check. Set bounded timeouts. Confirm authentication and protocol before adding location or session requirements. Inspect the response itself; a status code alone does not establish that the information you needed was returned. ## 6. Check the result and usage timestamp Record the check time, selected settings and sanitized result. If geography matters, compare the observed location with the task's acceptance rule. Validate the location and session behavior required by your workflow. The usage screen shows the latest usage snapshot and its sync time. It may lag behind the request you just made. One GB means 1,000,000,000 bytes. ## If the first request fails **HTTP 407:** start with [proxy authentication troubleshooting](/guides/proxy-error-407). Check the active allocation, credentials and authentication method before retrying. **Connection or timeout error:** check the gateway, protocol-specific port and client settings. Keep the retry count bounded and capture a sanitized error category. **Unexpected content or location:** verify the permitted destination and expected response, then compare the same request with only one setting changed. **Order or setup problem:** open [workspace support](/dashboard/support) with the order reference, time with timezone and a short description. Remove passwords, cookies and authorization headers. ## Keep the next step small Once the first request is understood, decide whether your workflow needs [rotating or sticky sessions](/blog/rotating-vs-sticky-proxies), and estimate [bandwidth and access terms](/blog/non-expiring-proxy-bandwidth) before scaling the task. --- Source: https://miproxy.io/blog Updated: 2026-10-17 # Good context. Better connections. Understand the choices behind a useful proxy workflow. Read practical explanations of connection types, session behavior, package terms and the work your application needs to own. ## Start with the decision in front of you Choosing a connection: [Residential and datacenter origins](/blog/residential-vs-datacenter-proxies) Planning a workflow: [Rotating and sticky sessions](/blog/rotating-vs-sticky-proxies) Planning the cost: [Bandwidth and access terms](/blog/non-expiring-proxy-bandwidth) ## Our editorial approach Written by MiProxy. Updated October 16, 2026. General technical guidance is separated from product capabilities. Provider comparisons cite official sources and do not imply independent testing or guaranteed results. [See current MiProxy product facts](/product-facts) ## Published articles [Residential vs. datacenter proxies: choose by the job](https://miproxy.io/blog/residential-vs-datacenter-proxies) — Compare proxy origin, session needs, bandwidth costs and valid results before choosing residential or datacenter connections. [Rotating vs. sticky proxies: match the session to the task](https://miproxy.io/blog/rotating-vs-sticky-proxies) — Understand rotating and sticky proxy sessions, connection reuse, failover and the checks needed for a consistent workflow. [Non-expiring proxy bandwidth: what to check before buying](https://miproxy.io/blog/non-expiring-proxy-bandwidth) — Separate bandwidth expiry, subscription renewal and allocation duration, and calculate the cost of an intermittent proxy workflow. [Raw proxies or a SERP API for SEO reporting?](https://miproxy.io/blog/proxies-vs-serp-api) — Choose between proxy connections and a managed SERP API by comparing parsed results, location controls, maintenance and total reporting cost. --- Source: https://miproxy.io/guides Updated: 2026-10-17 # A clear setup. A useful next step. Start with your client or the problem in front of you. Each guide explains the settings, shows a readable example and helps you check what happened. ## What are you working on? Make a first request: [Connect with cURL](/guides/curl-proxy-guide) Add a proxy to Python: [Use Python Requests](/guides/python-requests-proxy-guide) Resolve HTTP 407: [Troubleshoot authentication](/guides/proxy-error-407) ## New to the workspace? The [quick start](/docs) explains the order and allocation steps before the client code. The [session guide](/blog/rotating-vs-sticky-proxies) helps you choose behavior after the first request works. ## Examples with their assumptions visible Examples are protocol templates with placeholder credentials. Each article links to primary documentation and distinguishes general client behavior from verified MiProxy capabilities. A live request requires an approved real allocation and a permitted destination. ## Our editorial approach Written by MiProxy. Updated October 16, 2026. General technical guidance is separated from product capabilities. Provider comparisons cite official sources and do not imply independent testing or guaranteed results. [See current MiProxy product facts](/product-facts) ## Published articles [How to use a proxy with cURL](https://miproxy.io/guides/curl-proxy-guide) — Configure an authenticated HTTP proxy in cURL with timeouts, TLS verification and a focused connection troubleshooting checklist. [Use an authenticated proxy with Python Requests](https://miproxy.io/guides/python-requests-proxy-guide) — Set up Requests proxy routing with encoded credentials, explicit timeouts and TLS verification, then diagnose common connection failures. [Fix HTTP 407 Proxy Authentication Required](https://miproxy.io/guides/proxy-error-407) — Diagnose proxy authentication errors by checking credentials, gateway details, escaping and allowlists without disabling TLS verification. --- Source: https://miproxy.io/compare Updated: 2026-10-17 # Compare the fit. Understand the tradeoffs. The right choice depends on the work you need to do and the terms you can rely on. Start with availability, connection behavior and total operating effort, then inspect the exact product you would use. ## Take these questions into every comparison - Can I use this exact product now, with the access and payment terms I need? - Which protocols, locations and session controls are documented for the allocation? - What expires: bandwidth, account access, a reserved address, or a subscription period? - Who handles parsing, retries and result validation? - Which support channels and service commitments apply to the selected plan? - What would a small representative test need to demonstrate? Need the underlying concepts first? Read about [connection origins](/blog/residential-vs-datacenter-proxies), [session choices](/blog/rotating-vs-sticky-proxies), or [bandwidth terms](/blog/non-expiring-proxy-bandwidth). ## Our editorial approach Written by MiProxy. Updated October 16, 2026. General technical guidance is separated from product capabilities. Provider comparisons cite official sources and do not imply independent testing or guaranteed results. [See current MiProxy product facts](/product-facts) ## Published articles [MiProxy vs. IPRoyal: compare terms before the price](https://miproxy.io/compare/miproxy-vs-iproyal) — Compare IPRoyal and MiProxy package terms, connection settings and account workflows using a practical evaluation checklist. [MiProxy vs. Decodo: a practical evaluation checklist](https://miproxy.io/compare/miproxy-vs-decodo) — Compare Decodo and MiProxy residential connection options, package terms and workflows, keeping vendor claims separate from observed results. --- Source: https://miproxy.io/blog/residential-vs-datacenter-proxies Updated: 2026-10-17 # Residential vs. datacenter proxies: choose by the job Compare proxy origin, session needs, bandwidth costs and valid results before choosing residential or datacenter connections. ## Quick answer Start with the simplest proxy type that meets your permitted workflow. Compare correct results, bytes and session continuity on the same workload; an IP label alone cannot predict whether a destination will accept a request. ## Introduction A proxy-type decision is really a decision about a particular task: what you need to collect, which network perspective matters, and how much work you can afford to maintain. A small price-monitoring job and a localization check may both use HTTP, yet have different requirements for location and session continuity. This guide separates the connection category from the result you need. It gives you a practical way to compare residential and datacenter routes without treating advertised pool size, a low per-GB rate or a successful status code as proof that the job is done. ## Editorial disclosure This is MiProxy-authored educational guidance. IP-origin explanations cite a vendor source; workflow recommendations are editorial. Illustrative calculations are not benchmarks. Small connection checks do not establish network-wide reliability or comparative performance. ## How this guide was researched A source-based decision guide, informed by saved Google/Bing topic research, DataForSEO search snapshots and common proxy-selection questions. We compare responsibilities and decision criteria, not measured provider performance. - Exit origin and the network perspective the task requires. - Correct output, repeatable location context and continuity through a unit of work. - Complete operating cost, including unused traffic, retries and maintenance. - Evidence boundaries: published product descriptions versus observed allocation behavior. ## Quick comparison table General characteristics; verify the selected plan and workload. | Decision | Residential | Datacenter | | --- | --- | --- | | Exit origin | Residential internet access | Server-hosted addresses | | Useful starting point | Household-network perspective | Permitted checks accepting server-hosted traffic | | Session continuity | Depends on allocation and exit availability | Depends on allocation and session terms | | What to measure | Correct results, bytes and continuity | Correct results, bytes and continuity | | Guaranteed destination access | No | No | ## The difference starts with the exit IP Residential proxies use addresses associated with residential internet access. Datacenter proxies use server-hosted addresses. Those categories describe the connection origin, rather than a guarantee about permission, response quality or availability. A residential route can be useful when your research needs a household-network perspective. A datacenter route can be sufficient for permitted checks against a service you control. Neither type supplies a browser, manages cookies or parses a response for you. ## Write the requirements before choosing a pool Define the destination, country, request rate and expected output first. A page returning HTTP 200 can still contain a consent screen or an empty result. Count a request as successful only after validating the content your workflow needs. - Location: record requested country and observed location separately. - Continuity: decide whether a task needs one exit throughout a session. - Protocol: verify the exact endpoint supports your client and destination. - Data: define required fields, freshness and duplicate handling. ## Compare cost per correct result Run the same small, authorized sample with a fixed timeout and concurrency. Record attempted requests, correct records, transferred bytes and elapsed time. Include retries and engineering time when comparing the total cost. For illustration only, a $10 run producing 800 correct records costs $0.0125 per correct record. A cheaper $6 run producing 300 costs $0.02. These are arithmetic examples, not MiProxy benchmarks. Increase the sample only after the acceptance criteria are stable. ## Write a one-paragraph decision brief Before opening a pricing page, describe one repeatable job in ordinary language. For example: retrieve an approved public price field for a fixed list of products, from a defined country, once a day, within an agreed reporting window. State whether a missing field counts as a failure and whether a second attempt is allowed. That brief makes a later comparison interpretable. ## Write a one-paragraph decision brief: Location is an observation, not a checkbox A requested country tells the gateway what you asked for. An observed exit address and a destination’s response tell you what happened. Those observations can differ from the location displayed by a search engine or website. Keep the requested location, observed result and time together rather than labeling every localized response as correct. If the task is a localization check, define the expected currency, regional content or availability rule in advance. One valid regional page is stronger evidence for that check than a generic IP-location label. It still does not establish accuracy for every city or destination. ## Write a one-paragraph decision brief: A session requirement needs an ending Decide whether each request stands alone or belongs to a multi-step task. A sequence that relies on cookies or an authenticated session may need a consistent route as well as consistent client state. An independent public-page request may not. Specify the task boundary instead of choosing sticky routing for everything. Also define what happens if the route changes halfway through: restart from a safe point, preserve partial output for review, or stop. Continuing blindly can create an apparently complete dataset assembled under different assumptions. ## Residential routing: useful perspective, extra questions Residential origin can matter when the approved task calls for the perspective of a residential internet connection. That is a reason to evaluate the route, not evidence that every request will be accepted or every returned field will be correct. ## Residential routing: useful perspective, extra questions: When the additional route has a clear purpose Use an explicit requirement such as comparing your own application’s regional behavior from an approved residential exit. Confirm which locations and session controls are actually supplied by the selected allocation. Treat product-wide labels and the settings visible in a dashboard as separate from the result observed by the destination. ## Residential routing: useful perspective, extra questions: What to resolve before relying on it Ask how exit changes are handled, how transferred traffic is counted, what connection protocols are documented and which limits apply to your exact plan. Record the answers with the date. If those details are missing, a large advertised pool does not fill the evidence gap. ## Residential routing: useful perspective, extra questions: tradeoffs ### Where it helps - Can supply the residential-network perspective required by a specific authorized task. - Can be evaluated with location and session controls when the selected provider documents them. ### What to account for - Residential origin alone does not establish permission, accurate content or destination acceptance. - Allocation terms, exit availability and metering still need verification for the selected workflow. ## Datacenter routing: judge it against the same output Datacenter addresses originate in server infrastructure. If that route meets a permitted task’s requirements, there is no reason in this guide to reject it solely because another product carries a residential label. Compare the output you need and the work needed to sustain it. ## Datacenter routing: judge it against the same output: When server-hosted routing is sufficient An authorized check against an application you control may require a stable, documented route without requiring a household-network perspective. In that situation, determine whether the chosen allocation supplies the continuity, protocol and concurrency you need. Those product properties do not follow automatically from the word datacenter. ## Datacenter routing: judge it against the same output: When the requirement changes If a task specifically requires residential origin, a correct response from a server-hosted address may still fail that requirement. Conversely, a block or empty page is a symptom to diagnose, not proof that all datacenter routes fail. Separate the category requirement from configuration problems and destination access rules. ## Datacenter routing: judge it against the same output: tradeoffs ### Where it helps - May satisfy tasks that accept server-hosted traffic without adding an unnecessary origin requirement. - Can be compared using the same correct-output and operating-cost criteria as a residential allocation. ### What to account for - Does not provide a residential origin when that is an explicit requirement. - A datacenter label does not establish static ownership, unlimited traffic or reliable access. ## Make the comparison interpretable A useful comparison changes one meaningful variable at a time. Use the same permitted destination sample, expected fields, client version, timeout policy and request schedule. If you alter the parser or increase retries for only one route, the resulting totals no longer isolate the connection decision. ## Make the comparison interpretable: Keep a small acceptance scorecard For each attempt, record a non-secret task identifier, time, intended route, response status, whether the required fields were correct and complete, transferred bytes when available, and elapsed time. Classify failures rather than placing every unsuccessful attempt in one bucket. Authentication, DNS, TLS, destination limits and parsing problems need different remedies. Do not publish a success percentage without its sample size, destination and counting rule. A short exploratory sample can reveal a configuration problem. It cannot establish network-wide uptime, global coverage or a provider’s long-term reliability. ## Make the comparison interpretable: Turn the scorecard into a purchasing decision Add the actual payment, traffic consumed and work needed to collect valid output. For intermittent usage, note any balance left unused at expiry. For recurring usage, include monitoring and parser maintenance. Keep engineering assumptions explicit even if you cannot price every hour precisely. Choose a route only after identifying which requirement it meets better and whether that improvement matters enough to justify the total cost. If both routes meet the acceptance rule, commercial terms and operational simplicity can decide the result. If neither does, revisit the data source or task design before buying a larger plan. ## Four conclusions the comparison cannot support A route comparison has limits even when the sample is carefully recorded. Keep those limits alongside the decision so that a later reader does not turn a local observation into a general product claim. - One working request does not prove all destination types work. - A requested location does not prove the destination interpreted it the same way. - A sticky setting does not establish permanent ownership of an exit IP. - A lower package payment does not establish a lower cost per correct result. ## What MiProxy has verified MiProxy brings proxy packages, connection settings and usage into one workspace. Access is currently limited to approved accounts. Check the selected product and allocation status before making requests; datacenter products are currently unavailable. ## Which approach should you choose? Choose the least complicated connection that satisfies the permitted task. Pay for residential routing when a documented requirement or a controlled comparison justifies it. ### A service you control accepts the existing route Keep that route while it meets the output and timing requirements; a different IP category is not an improvement by itself. ### The task requires a residential-network perspective Evaluate an actual residential allocation and validate observed location, output and continuity. ### You need structured search rankings Compare a documented SERP data product with the full work of maintaining raw collection and parsing. ## Are residential proxies always better? No. A permitted workflow that works reliably with a datacenter connection may not benefit from residential routing. Compare the actual result and total operating cost. ## Does a proxy bypass every restriction? No. Destinations can apply authentication, rate limits and other controls regardless of IP type. Use permitted access and honor those limits. ## What is the main difference between residential and datacenter proxies? The category describes the exit-address origin: residential internet access versus server-hosted infrastructure. It does not, by itself, establish the selected plan’s session terms, permission, response quality or availability. ## Should I compare providers using price per GB alone? No. Compare the payment and operating work required to obtain correct output. Include consumed traffic, permitted retries, unused allowance where relevant, parsing and maintenance. Keep the workload and counting rule consistent. ## Does a residential IP guarantee the destination sees the requested city? No such guarantee follows from the address category. Record requested targeting and the destination’s observed behavior separately, and verify the location context needed by your task. ## Sources - [Bright Data: residential and datacenter IP origins — vendor explanation](https://brightdata.com/blog/proxy-101/differences-between-datacenter-and-residential-proxies) — checked 2026-10-16 ## Related reading - [Rotating vs. sticky proxies: match the session to the task](https://miproxy.io/blog/rotating-vs-sticky-proxies) - [Non-expiring proxy bandwidth: what to check before buying](https://miproxy.io/blog/non-expiring-proxy-bandwidth) - [MiProxy vs. Decodo: a practical evaluation checklist](https://miproxy.io/compare/miproxy-vs-decodo) - [How to use a proxy with cURL](https://miproxy.io/guides/curl-proxy-guide) - [Use an authenticated proxy with Python Requests](https://miproxy.io/guides/python-requests-proxy-guide) --- Source: https://miproxy.io/blog/rotating-vs-sticky-proxies Updated: 2026-10-17 # Rotating vs. sticky proxies: match the session to the task Understand rotating and sticky proxy sessions, connection reuse, failover and the checks needed for a consistent workflow. ## Quick answer Use rotation for independent requests when changing exits is appropriate. Use a sticky session when related steps need continuity. A sticky session requests persistence; it is not ownership of a permanent IP. ## Introduction The important session question is where one unit of work ends. A collection of independent checks and a sequence of related steps should not automatically use the same routing behavior. Choose the mode after describing that boundary. This guide explains rotation, stickiness and client state separately. It focuses on what to verify in a provider’s documentation and what to record when an allocation behaves differently from the requested setting. ## Editorial disclosure Provider session documentation describes that provider’s semantics, not a shared industry guarantee. A brief sticky-session observation does not establish long-term session stability. ## How this guide was researched An explanation of session semantics using the saved rotating-versus-sticky keyword topic and provider-specific session documentation. No universal duration, pool behavior or live mode benchmark is inferred. - The documented event that triggers a new exit. - Continuity needed within a task and response to exit loss. - Separation of provider routing from client connection reuse and cookies. - Allocation-specific terms rather than assumptions based on product labels. ## Quick comparison table Choose session behavior around a unit of work. | Decision | Rotating | Sticky | | --- | --- | --- | | Routing intent | Change exits at a supported boundary | Request the same exit for a period | | Typical fit | Independent requests | Related steps needing continuity | | Permanent IP ownership | No | No | | Client cookies | Managed separately by your application | Managed separately by your application | | Important check | Per-request versus per-connection behavior | Duration and response to exit loss | ## Rotation and connection reuse are different controls Providers can rotate on a new connection, a request or a configured interval. Read the plan documentation before assuming that every HTTP request gets a different exit. HTTP keep-alive and pooled connections can affect what your client observes. Independent public-page checks can often be treated as separate units of work. Keep a bounded request rate and record the observed exit during your test. Rotation does not remove a destination’s access conditions or guarantee a successful response. ## Use stickiness for a bounded workflow A multi-step task may require a consistent exit alongside cookies and other client state. Keep the same session setting for that task and start a new one at a meaningful boundary. A residential exit can disappear before a requested session ends. Decide what to do when that happens: restart the task, save partial progress, or stop for review. Do not silently continue an authenticated workflow from a different exit if that invalidates its assumptions. ## Check the behavior instead of guessing Test a short series against a permitted endpoint that reports the observed IP. Log timestamps and a non-secret session label. Repeat across fresh connections as well as a reused client session, then compare the results. - Confirm whether the mode applies per connection or per request. - Check documented maximum duration and actual observed duration. - Separate client cookie state from provider-side session state. - Avoid recording passwords or full credential-bearing proxy URLs. ## Design the session around a real task Write down what has to remain consistent from the first step to the last. An exit address may be one part of that state, alongside cookies, request headers and application identifiers. Changing only the proxy session setting does not update the other parts for you. ## Design the session around a real task: Independent checks A permitted check of one public page can often be evaluated independently of the next. Keep each result associated with its intended location and retrieval time. If you retry a failed check with a different route, record that change rather than presenting both attempts as one observation. ## Design the session around a real task: Related steps A task that first establishes client state and then retrieves a result needs a clear recovery point. Keep its route and client state aligned for the task’s duration. If a step fails, restarting the whole sequence may be more interpretable than continuing from a partially completed state. ## The practical benefits and limits Neither mode wins every workflow. The useful question is whether the documented behavior matches the unit of work you defined. ## The practical benefits and limits: tradeoffs ### Where it helps - Rotation can give independent work explicit route-change boundaries when supported. - Sticky routing can request continuity across related steps. - A deliberate session label helps group sanitized operational observations. ### What to account for - Neither setting manages browser cookies or application state. - A requested sticky period is not a promise that an unavailable exit will persist. - Connection reuse can make observed behavior differ from a per-request assumption. ## Read an observation before changing a setting Suppose two independent requests show the same exit. That fact alone does not prove rotation is broken: check whether the provider rotates per connection, whether the client reused a connection, and whether a different exit was promised at that boundary. Conversely, a changed exit during a sticky task needs examination even if the HTTP status remained successful. ## Read an observation before changing a setting: Record only what helps diagnosis Keep timestamps, a non-secret task/session label, the requested mode, the connection reuse pattern and the observed exit if your permitted endpoint reports it. Do not save the password or a credential-bearing proxy URL. A useful support record explains which boundary was expected to change the route. ## Read an observation before changing a setting: Choose a recovery policy in advance Define whether exit loss stops the task or triggers a fresh sequence. Keep retry counts bounded and distinguish reconnecting from changing the meaning of the measurement. A later report should show which outputs came from a restarted task rather than silently merging them. ## Document the session for the next maintainer A routing choice should survive the person who configured it. Keep the provider’s documented boundary, the client reuse behavior and the task recovery rule with the integration notes. If the client library or gateway product changes, review those assumptions together. A session suffix copied from an old example is not a durable specification. Keep the description concrete: which steps belong to a task, which observation marks completion, and which failure requires a fresh sequence. That small handoff makes it easier to investigate a changed exit without guessing whether the behavior was expected. ## MiProxy settings depend on the allocation Use the connection controls supplied for your allocation rather than constructing an undocumented username suffix. Session duration and exit availability depend on the selected product; verify the behavior your task requires. ## Which approach should you choose? Use rotation for independent work and sticky routing for tasks that need continuity. Keep recovery rules explicit in both modes. ### Each request is independent Check the documented rotation boundary and verify observed behavior across the connection pattern your client actually uses. ### Several steps belong together Use a supported sticky setting, preserve the necessary client state and decide how the task recovers if the exit changes. ### You need a permanently assigned address Review a product’s explicit static-allocation terms; do not substitute a sticky-session label. ## What does rotating proxies mean? It means a proxy service changes the exit address at a supported boundary, such as a new connection or a configured interval. Check the provider’s documented behavior: rotation does not necessarily happen on every request, clear your client’s cookies, or guarantee a successful destination response. ## Is a sticky proxy the same as a static IP? No. Sticky routing requests the same exit for a period. Static products have separate allocation terms; neither should be inferred from the word sticky. ## Does changing a session clear browser cookies? No. Provider routing and browser storage are separate. Your application must manage its own cookies and task boundaries. ## Does every HTTP request get a new exit IP? Not necessarily. Providers can define rotation at a connection boundary, an interval or another documented event. Client connection reuse can affect observations, so check the selected plan and actual client pattern. ## What should happen if a sticky exit becomes unavailable? Define a recovery rule for the task: stop, restart a safe sequence or preserve partial output for review. Do not assume the requested continuity period guarantees that an unavailable exit remains usable. ## Sources - [Oxylabs: residential proxy session control — provider-specific semantics](https://developers.oxylabs.io/products/proxies/residential-proxies/session-control) — checked 2026-10-16 - [Requests: advanced usage and proxies](https://requests.readthedocs.io/en/latest/user/advanced/#proxies) — checked 2026-10-16 ## Related reading - [Residential vs. datacenter proxies: choose by the job](https://miproxy.io/blog/residential-vs-datacenter-proxies) - [Use an authenticated proxy with Python Requests](https://miproxy.io/guides/python-requests-proxy-guide) - [How to use a proxy with cURL](https://miproxy.io/guides/curl-proxy-guide) - [Non-expiring proxy bandwidth: what to check before buying](https://miproxy.io/blog/non-expiring-proxy-bandwidth) - [Fix HTTP 407 Proxy Authentication Required](https://miproxy.io/guides/proxy-error-407) --- Source: https://miproxy.io/blog/non-expiring-proxy-bandwidth Updated: 2026-10-17 # Non-expiring proxy bandwidth: what to check before buying Separate bandwidth expiry, subscription renewal and allocation duration, and calculate the cost of an intermittent proxy workflow. ## Quick answer Non-expiring bandwidth describes when unused traffic remains available under a plan’s terms. It does not mean unlimited traffic, permanent IP ownership or uninterrupted service. Check the actual package before paying. ## Introduction A per-GB price is only useful when you know how much traffic you will actually use and how long the balance remains available. An occasional project can have very different economics from a daily collection job. Non-expiring, prepaid, unlimited and subscription describe different parts of an offer. This guide gives you a way to read those terms together and compare an actual payment with usable output instead of a headline allowance. ## Editorial disclosure Provider commercial statements are dated vendor claims. No universal expiry policy is inferred across proxy categories. MiProxy’s observed residential allocation had no supplier expiry; the selected retail order and future commercial terms remain authoritative. ## How this guide was researched A billing decision guide informed by saved pay-as-you-go/non-expiry SERPs and common billing questions, alongside attributed provider terms. Arithmetic examples illustrate definitions; no competitor checkout or metering benchmark was performed. - What is purchased: a traffic balance, access period or recurring allowance. - When validity begins and what events end or restrict access. - Minimum payment versus traffic likely to be consumed. - Renewal, usage accounting and order-level terms. ## Read the three clocks separately A package can have a bandwidth balance, a billing renewal date and an allocation end date. Those are different things. A recurring plan might refresh traffic monthly, while a time-based allocation can end even when usage is low. Ask when the clock starts: purchase, payment confirmation or activation. Also check inactivity conditions, account closure terms and whether a replacement allocation carries the old balance. A headline per-GB rate does not answer these questions. ## Model the traffic you will actually use For an intermittent workflow, compare the minimum payment with your expected consumption before expiry. A $20 package with 10 GB costs an effective $10 per used GB if only 2 GB are used before the balance expires. That arithmetic example excludes tax and is not a MiProxy offer. Request headers, response bodies, retries and browser assets can affect usage according to the supplier’s metering rules. Use a bounded sample to estimate bytes per correct result. Leave room for retries instead of assuming every purchased byte becomes useful output. ## Questions to resolve at checkout Save the dated terms for the exact product you select. A rule for one proxy category may not apply to another. - What is the total payment, including tax and minimum top-up? - Does unused bandwidth expire, roll over or stay available? - When does renewal occur, and how is it canceled? - Are failed attempts, uploads and protocol overhead counted? - How quickly does the dashboard reconcile usage? ## Translate the headline into an order record Before comparing two offers, write down what each payment buys. Ten gigabytes is a quantity; thirty days is a duration; monthly renewal is a billing event. A product can combine more than one of these. Calling both products prepaid does not make their balances or access periods equivalent. ## Translate the headline into an order record: Ask when the clock starts A duration can begin at purchase, fulfillment or activation, depending on the stated terms. That matters when you buy before the project is ready. Save the relevant start condition alongside the order rather than relying on a general pricing-page headline. ## Translate the headline into an order record: Ask what happens to unused traffic Separate balance expiry from allocation expiry and account access. A non-expiring traffic statement does not establish indefinite operation of the same gateway or ownership of an IP. Check what the provider says about account closure, plan changes and replacement allocations before making a long-term budget. ## Compare an intermittent project honestly Start with a bounded estimate of bytes per correct output, then multiply by the number of outputs you expect during the relevant period. Add room for permitted retries and the client assets your workflow actually transfers. Keep the estimate separate from measured supplier usage because metering rules and displayed precision can differ. ## Compare an intermittent project honestly: tradeoffs ### Where it helps - A balance without a time expiry can fit work that arrives irregularly, subject to its terms. - One-time allocations can make payment commitments easier to identify when renewal is absent. ### What to account for - A minimum purchase can leave capital tied up in unused traffic. - Non-expiry does not guarantee availability, stable pricing or unlimited use. - A dashboard balance alone does not explain which traffic was counted. ## Use one worksheet for every provider Record total payment, allowance, minimum top-up, validity start, expiry condition, renewal behavior and how usage is reconciled. Keep the product category and dated terms with that worksheet. A residential traffic rule should not be carried over to an unrelated time-based product. ## Use one worksheet for every provider: Calculate effective consumption cost Divide the relevant payment by traffic actually used for the project, then examine how much of that traffic produced correct output. If the balance remains available for another project, show the remaining balance separately rather than treating it as either lost or already productive. Be explicit about the period your calculation covers. ## Use one worksheet for every provider: Reconcile payment and usage separately A payment receipt proves a commercial event, while a usage snapshot describes a counter at a particular time. Neither proves every request worked. Keep timestamps and preserve earlier observations when a supplier counter is delayed. Ask for clarification before interpreting a temporarily unchanged counter as free traffic. ## Keep allowance and access in the same budget Imagine a project paused while requirements change. A remaining traffic balance is useful only if the account and selected product still provide a documented way to use it. Keep the payment record, balance observation and access conditions together. Neither a screenshot of available gigabytes nor a general no-expiry phrase answers every operational question. For a purchasing decision, identify what would make the remaining balance unusable and which terms address that event. If the terms do not answer an important question, ask before paying. Recording uncertainty is more accurate than silently assuming every unused byte will remain available under every future condition. ## MiProxy terms are allocation-specific Review the expiry and billing unit on the individual plan and order. Do not interpret prepaid pricing as a universal non-expiry promise. Check the allocation’s access conditions and usage timestamp before planning a workload. ## Which approach should you choose? Choose the commercial model around your expected usage pattern and the exact order terms. Non-expiry can matter for intermittent work, but it does not resolve access or metering questions. ### Work arrives irregularly Compare minimum payment, non-expiry conditions and account restrictions against likely consumption. ### Work runs predictably every month Compare actual recurring consumption, renewal conditions and unused-balance treatment. ### The offer says unlimited Read time, concurrency, acceptable-use and other restrictions before treating the label as an operating budget. ## Does prepaid mean the bandwidth never expires? No. Prepaid describes when payment occurs. Expiry must be stated in the selected package’s terms. ## Is unlimited bandwidth the same as non-expiring bandwidth? No. Unlimited describes a usage allowance subject to its terms; non-expiring describes the time condition of a balance. ## What should I check before buying non-expiring traffic? Read the exact product’s minimum purchase, balance conditions, account restrictions, allocation duration and usage-metering rules. Save the dated terms; a non-expiry statement for one proxy category may not apply to another. ## Does no bandwidth expiry mean I own a permanent IP? No. A traffic balance’s validity and an exit address’s allocation are different properties. Verify static-address or session terms separately instead of inferring them from a billing label. ## How do I compare traffic I may use over several months? State the comparison period, expected consumption and payment. Show unused balance separately and retain the applicable expiry conditions. Illustrative effective-cost calculations are estimates until supported by actual usage observations. ## Sources - [IPRoyal residential proxies — vendor claims, checked October 16, 2026](https://iproyal.com/residential-proxies/) — checked 2026-10-16 - [Decodo residential proxies — vendor claims, checked October 16, 2026](https://decodo.com/proxies/residential-proxies) — checked 2026-10-16 ## Related reading - [MiProxy vs. IPRoyal: compare terms before the price](https://miproxy.io/compare/miproxy-vs-iproyal) - [MiProxy vs. Decodo: a practical evaluation checklist](https://miproxy.io/compare/miproxy-vs-decodo) - [Residential vs. datacenter proxies: choose by the job](https://miproxy.io/blog/residential-vs-datacenter-proxies) - [Rotating vs. sticky proxies: match the session to the task](https://miproxy.io/blog/rotating-vs-sticky-proxies) - [How to use a proxy with cURL](https://miproxy.io/guides/curl-proxy-guide) --- Source: https://miproxy.io/guides/curl-proxy-guide Updated: 2026-10-17 # How to use a proxy with cURL Configure an authenticated HTTP proxy in cURL with timeouts, TLS verification and a focused connection troubleshooting checklist. ## Quick answer Pass the proxy endpoint with --proxy and authenticate with --proxy-user. Start with one authorized request and explicit timeouts. The template below deliberately uses .invalid hosts and cannot connect until you replace them. ## Introduction cURL is a useful first client because it makes the gateway, authentication and timeout choices visible in one request. Start with that small connection check before adding browser automation or a larger collection job. The example here uses reserved .invalid names. Replace them with documented allocation details and an endpoint you are allowed to request. A command that parses correctly is not evidence of a live MiProxy route. ## Editorial disclosure Examples contain placeholders and were not run against a production MiProxy allocation for this guide. Official cURL documentation supports the option semantics. No destination coverage, throughput or uptime is asserted. ## How this guide was researched Protocol guidance based on the official cURL manual and proxy-authentication documentation. This is a configuration template and diagnostic sequence, not a current-allocation connection test. - Gateway transport versus destination URL scheme. - Explicit proxy authentication without literal secrets in examples. - Bounded requests with destination certificate verification preserved. - Separating proxy errors from DNS, connection and destination failures. ## Collect the connection details You need an active allocation, its gateway host, port, protocol and proxy username. Proxy credentials can differ from your account login. Use an endpoint you are authorized to request and whose expected output you understand. These are protocol templates, not a live MiProxy allocation test. Confirm the connection details in the portal before replacing the placeholders. curl --version shows your installed version and supported protocols. ## Make one bounded HTTPS request For a normal HTTP proxy, an HTTPS destination still uses an http:// proxy URL: cURL establishes a CONNECT tunnel and verifies the destination’s TLS certificate. An HTTPS proxy is a separate capability that must be supported by the gateway. With only a username supplied to --proxy-user, cURL prompts for the proxy password interactively. This avoids putting a literal password into the example or shell history. Use a secret store for unattended jobs. ```bash # Replace both .invalid hosts and the example port before use. curl --proxy 'http://gateway.invalid:8080' \ --proxy-user 'YOUR_PROXY_USERNAME' \ --connect-timeout 10 \ --max-time 30 \ --fail-with-body \ --url 'https://check.invalid/ip' ``` ## Verify the result, then the route A successful response should match the permitted endpoint’s documented output. If it reports an IP address, compare that observation with your intended route. One request demonstrates that connection at that moment; it does not measure pool size, long-term stability or every destination. Keep TLS verification enabled. Do not add --insecure to hide a certificate error. Confirm the hostname, your system trust store and any organization-approved certificate requirements instead. ## Understand the two connections Your client first reaches a proxy gateway. The gateway then provides the route to the destination. A failure before reaching the gateway differs from a response returned by the destination. Keep those stages separate when interpreting an error. ## Understand the two connections: The gateway URL describes gateway transport An http:// gateway URL does not mean the requested website must use HTTP. For an HTTPS destination, an HTTP proxy can establish a CONNECT tunnel. The client then verifies the destination certificate. An https:// gateway URL adds a separate gateway transport requirement; use it only when your selected endpoint documents support. ## Understand the two connections: Check where a name-resolution failure occurs The gateway hostname and destination hostname are different names with different roles. Record which name failed, the selected proxy mode and the cURL exit information. Replacing a password cannot resolve an invalid gateway hostname. Switching TLS verification off cannot repair DNS or make an unsupported port work. ## Keep connection troubleshooting separate from secret handling An interactive password prompt is convenient for a first request because the command itself does not contain a password. Unattended tasks need a deliberate secret-delivery method appropriate to their environment. Copying a full credential-bearing command into chat, a ticket or a repository creates unnecessary exposure. ## Keep connection troubleshooting separate from secret handling: Be precise about credential formats A separate proxy-user option and a credential-bearing URL have different parsing boundaries. Follow the cURL manual for your chosen form and quote shell arguments deliberately. If you change formats while troubleshooting, record the sanitized structure so you can distinguish an encoding problem from incorrect credentials. ## Keep connection troubleshooting separate from secret handling: Share a useful sanitized record A support record can contain time, cURL version, gateway hostname without secrets, destination category, selected protocol, timeout values and the resulting status or exit code. If verbose output is required, review it locally before sharing. Remove authentication values, cookies and private destination parameters. ## A returned page is the start of verification After the first response, check its body against the endpoint’s documented expected output. A status alone cannot establish that the result is useful. For a connection-check endpoint, inspect the reported observation rather than assuming the selected country or session setting proves the route. ## A returned page is the start of verification: tradeoffs ### Where it helps - A small explicit command makes connection choices inspectable. - Separate timeout controls help bound a first diagnostic request. - The same sanitized command shape makes support discussions easier. ### What to account for - A working command against one endpoint does not validate other destinations. - Shell quoting, inherited configuration and credential formatting still need care. - Verbose traces can expose secrets if shared without review. ## Move from one request to a maintained workflow Once the bounded request gives the expected result, decide what your larger client needs to preserve: routing options, credential sourcing, timeouts, TLS trust and a rule for classifying output. Record those choices before raising concurrency. A working interactive command does not automatically configure a different client library. ## Move from one request to a maintained workflow: Add retries only for a defined condition Decide which transient errors may be retried and set an attempt limit. Do not repeatedly resend a bad password or turn a destination rate limit into a burst of new attempts. Keep each attempt visible so that a later report can distinguish first-pass output from recovered output. ## Move from one request to a maintained workflow: Use the intended trust configuration If an organization requires an approved certificate bundle, configure it using the documented cURL options and deployment process. Disabling verification hides an important check. Keep gateway transport and destination verification distinct when deciding which certificate or hostname an error concerns. ## Separate authentication, network and destination errors HTTP 407 points to proxy authentication; check gateway credentials and the permitted authentication method. A name-resolution failure or connection timeout belongs to a different layer. HTTP 403 or 429 from the destination requires inspecting destination access and rate limits. For support, record time, cURL version, sanitized command, status or exit code, and whether failure happens before or after connection. Verbose traces can contain secrets; redact them before sharing. ## Which approach should you choose? Prove one bounded request with the documented gateway first. Inspect the expected output before treating the connection as successful. ### First connection Use the gateway host, port and supported protocol from the active allocation; supply credentials separately. ### HTTPS destination through an HTTP gateway Use the documented HTTP proxy URL and retain destination TLS verification; CONNECT establishes the tunnel. ### Unexpected failure Classify the status or cURL error before changing credentials, trust settings or routing mode. ## Why use an HTTP proxy URL for an HTTPS website? The proxy URL specifies the transport to the gateway. An HTTP proxy can tunnel an HTTPS destination with CONNECT while the client verifies the destination certificate. ## Are these production MiProxy credentials? No. The .invalid hosts and example username are placeholders. This guide does not establish current live allocation availability. ## What does --proxy-user configure? It supplies credentials for authenticating to the proxy. These can differ from credentials for the destination website. Follow the gateway’s documented authentication method and avoid sharing a literal password in commands or traces. ## Does an HTTP proxy URL disable HTTPS certificate checks? No. The proxy gateway transport and destination certificate verification are separate. For a supported HTTP gateway and HTTPS destination, cURL can use CONNECT and still verify the destination certificate. ## Why use connection and total timeouts together? They bound different parts of the request. An explicit connection limit constrains establishment, while a total-time setting bounds the overall cURL operation. Review the manual for the installed version and chosen command. ## Sources - [curl: proxy authentication](https://everything.curl.dev/usingcurl/proxies/auth.html) — checked 2026-10-16 - [curl command-line manual](https://curl.se/docs/manpage.html) — checked 2026-10-16 ## Related reading - [Fix HTTP 407 Proxy Authentication Required](https://miproxy.io/guides/proxy-error-407) - [Use an authenticated proxy with Python Requests](https://miproxy.io/guides/python-requests-proxy-guide) - [Rotating vs. sticky proxies: match the session to the task](https://miproxy.io/blog/rotating-vs-sticky-proxies) - [Residential vs. datacenter proxies: choose by the job](https://miproxy.io/blog/residential-vs-datacenter-proxies) - [Non-expiring proxy bandwidth: what to check before buying](https://miproxy.io/blog/non-expiring-proxy-bandwidth) --- Source: https://miproxy.io/guides/python-requests-proxy-guide Updated: 2026-10-17 # Use an authenticated proxy with Python Requests Set up Requests proxy routing with encoded credentials, explicit timeouts and TLS verification, then diagnose common connection failures. ## Quick answer Configure both http and https proxy keys for the destination schemes you use. Supply the gateway URL, preserve TLS verification and set a timeout. The .invalid endpoints below are safe placeholders, not a working MiProxy connection. ## Introduction Requests proxy setup is a small configuration task with several independent boundaries: destination schemes, gateway transport, credential encoding, environment configuration and timeouts. Make each one explicit before diagnosing a failure. This guide starts with an isolated Session and one authorized request. It explains why the example makes those choices, what it does not prove, and which information to preserve when moving the configuration into a maintained application. ## Editorial disclosure The snippet is a protocol template using .invalid hosts. Official Requests documentation supports the configuration semantics; there was no current production MiProxy connection run for this article. A Session does not establish a provider-side sticky-session guarantee. ## How this guide was researched A configuration guide grounded in official Requests proxy documentation and common authenticated-setup questions. Code uses reserved placeholder hosts and environment-supplied credentials; no production-allocation outcome is implied. - Explicit destination-scheme proxy mapping. - Encoding credential components without changing URL structure. - Environment inheritance and approved TLS trust. - Interpreting timeout, authentication and response failures separately. ## Prepare an isolated client Install Requests in a virtual environment and record the Python and Requests versions with your test. Supply real connection values through your environment or deployment secret manager. Do not commit a credential-bearing proxy URL. The example uses an HTTP gateway for an HTTPS destination. Confirm your allocation’s supported transport and port. This guide covers Requests proxy configuration; it does not imply that MiProxy has a public management API. ## Encode credentials and set a timeout Percent-encoding each credential component prevents special characters such as @ from changing the structure of the proxy URL. Keep the original values in your environment and encode them once. This explicit configuration disables inherited environment settings with trust_env=False. That also disables environment-based CA bundle configuration; organizations that require a custom trust bundle should set session.verify to the approved bundle path. ```python import os from urllib.parse import quote import requests username = quote(os.environ["PROXY_USERNAME"], safe="") password = quote(os.environ["PROXY_PASSWORD"], safe="") proxy_url = f"http://{username}:{password}@gateway.invalid:8080" with requests.Session() as session: session.trust_env = False session.proxies = {"http": proxy_url, "https": proxy_url} response = session.get( "https://check.invalid/ip", timeout=(10, 30), ) response.raise_for_status() print(response.text) ``` ## Interpret the result carefully Replace both .invalid hosts before using the template. The timeout tuple limits connection establishment and read inactivity; it is not a guaranteed total runtime for a batch. Start with one request and inspect the expected response body. A Requests Session reuses connections and cookies. Provider-side sticky routing is a separate setting. For an independent task, choose that boundary deliberately rather than assuming a new Python object always produces a new residential exit. ## Read the proxy dictionary from the destination outward The http and https keys describe destination URL schemes. They do not by themselves state that the proxy gateway accepts encrypted transport. In the example, both schemes use the same documented HTTP gateway URL. Change that only when your allocation supports a different gateway transport. ## Read the proxy dictionary from the destination outward: Choose environment behavior deliberately Requests can use environment proxy configuration. That can be convenient on a managed workstation, but it can also make an otherwise identical script route differently on another machine. The example sets trust_env=False to make its explicit settings easier to reason about. This also affects environment-based CA bundle handling; configure an approved trust path explicitly where needed. ## Read the proxy dictionary from the destination outward: Client reuse and provider routing are different A Requests Session can reuse connections and cookies. A provider’s rotating or sticky routing mode is another layer. Do not assume that creating a Session guarantees one exit or that a new Session guarantees a different exit. Check the provider’s documented boundary and compare it with the pattern your client actually uses. ## Encode components, then construct the URL A username or password can contain characters with special meaning in a URL. Percent-encode each credential component before inserting it into the gateway URL, as the example does. Encoding the entire completed URL would also transform its separators; encoding a previously encoded password can change the intended value. ## Encode components, then construct the URL: Validate configuration before making the request Check locally that each required environment value is present and that the gateway host and port match the active allocation. Error messages should identify the missing configuration name without printing its value. Keep the original secret in the environment or deployment secret store rather than committing an encoded copy. ## Encode components, then construct the URL: Log the event without the credential-bearing URL For operational logs, store a task label, time, client version, gateway hostname, destination category and failure class. A full proxy URL can include the password. Redact that structure before sending an exception report to analytics or support systems. ## Know what the timeout tuple promises The timeout tuple separates connection establishment from read inactivity. It does not create a guaranteed wall-clock deadline for an entire batch, and a successful response still needs content validation. Build the surrounding job with its own task boundary and completion rule. ## Know what the timeout tuple promises: tradeoffs ### Where it helps - An explicit Session exposes proxy mapping, trust and timeout choices in one place. - Environment-supplied secrets keep the literal password out of the example source. - Component encoding makes reserved credential characters less ambiguous. ### What to account for - Disabling environment inheritance requires deliberate handling of organization trust settings. - A read timeout is not a total batch-runtime budget. - Session reuse does not define the gateway’s exit-rotation policy. ## Classify a failure before adding recovery If the proxy reports HTTP 407, examine proxy authentication and the supported method. A connection timeout, DNS failure or certificate error belongs to a different layer. If the destination returns an error after the tunnel is established, inspect that response and the destination’s access requirements separately. ## Classify a failure before adding recovery: Define useful output raise_for_status helps surface unsuccessful HTTP responses. It does not validate the required fields or prove that an HTML response is the intended page. Check your endpoint’s documented structure and record missing or unexpected fields as content failures. ## Classify a failure before adding recovery: Keep retries finite and interpretable Choose specific transient failures that may be retried and keep an attempt count. Credential mistakes should trigger a configuration review, while destination rate limits need an appropriate pause or stop policy. Do not silently combine output from restarted sessions when continuity matters to the task. ## Handle failures without exposing secrets Treat proxy authentication, TLS errors and destination HTTP errors separately. An HTTPS tunnel authentication failure can surface as ProxyError rather than an ordinary response object. A timeout alone does not tell you the exit was blocked. Catch requests.exceptions.RequestException at your application boundary and log a sanitized error category. Avoid printing the proxy URL or raw exception into shared logs because connection diagnostics can expose credentials. Stop or back off on access and rate-limit errors rather than adding unlimited retries. ## Which approach should you choose? Configure a single bounded Session explicitly, preserve TLS verification and validate the response body before expanding the workload. ### You need deterministic proxy routing Set the relevant scheme keys and decide deliberately whether environment proxy settings should participate. ### Your organization supplies a CA bundle Preserve the approved trust configuration explicitly when disabling environment inheritance. ### The first request fails Separate proxy authentication, network establishment, TLS and destination response handling before retrying. ## Why set both proxy dictionary keys? The keys select destination URL schemes. Setting both makes the intended routing explicit for HTTP and HTTPS requests. ## Should I set verify=False to fix a proxy error? No. Preserve certificate verification and fix the gateway, hostname or approved trust configuration. Disabling TLS verification does not repair proxy authentication. ## Why encode the proxy username and password separately? Reserved URL characters inside credentials can otherwise change the URL’s structure. Encode each credential component once before building the gateway URL; do not encode the entire completed URL or expose it in logs. ## What does trust_env=False change? It prevents the Session from inheriting environment configuration used by Requests, including proxy settings and environment-based CA bundle handling. Set the required routing and approved certificate trust explicitly when choosing this isolation. ## Does a Requests Session guarantee a sticky proxy exit? No. A Session manages client connection reuse and cookies; the gateway’s routing policy is separate. Verify the provider’s supported session controls and the behavior of the actual allocation. ## Sources - [Requests: advanced usage and proxies](https://requests.readthedocs.io/en/latest/user/advanced/#proxies) — checked 2026-10-16 ## Related reading - [How to use a proxy with cURL](https://miproxy.io/guides/curl-proxy-guide) - [Fix HTTP 407 Proxy Authentication Required](https://miproxy.io/guides/proxy-error-407) - [Rotating vs. sticky proxies: match the session to the task](https://miproxy.io/blog/rotating-vs-sticky-proxies) - [Residential vs. datacenter proxies: choose by the job](https://miproxy.io/blog/residential-vs-datacenter-proxies) - [Non-expiring proxy bandwidth: what to check before buying](https://miproxy.io/blog/non-expiring-proxy-bandwidth) --- Source: https://miproxy.io/guides/proxy-error-407 Updated: 2026-10-17 # Fix HTTP 407 Proxy Authentication Required Diagnose proxy authentication errors by checking credentials, gateway details, escaping and allowlists without disabling TLS verification. ## Quick answer HTTP 407 means the proxy requires acceptable authentication. Check the proxy username and password, authentication method and gateway first. It is different from HTTP 401 at the destination and does not prove the destination blocked your exit. ## Introduction HTTP 407 means the proxy is asking for valid proxy authentication. It is a useful diagnostic boundary: a password for the destination website, an unrelated routing setting or a new exit IP does not automatically satisfy the gateway’s challenge. Work from the observed response toward the configuration. This guide separates credentials, authentication method, URL encoding and other network failures so that one change at a time has a clear purpose. ## Editorial disclosure Protocol meanings come from the linked primary references. This is not a claim that every application surfaces proxy errors identically. No live failure injection or current production MiProxy authentication test was performed for the article. ## How this guide was researched Troubleshooting guidance grounded in RFC 9110 and official cURL authentication documentation. The direct 407 questions are preserved from saved SERP research; the diagnostic sequence is editorial interpretation of the protocol. - Proxy challenge versus destination authentication. - Correct allocation credentials, gateway and supported method. - Client configuration and credential-component parsing. - Evidence needed to distinguish a resolved authentication issue from a new failure. ## Identify which server rejected the request A proxy sits between the client and destination. Its credentials are separate from destination credentials and often separate from your dashboard login. A 407 can occur while opening an HTTPS CONNECT tunnel, before any destination page is returned. Client libraries may expose a failed tunnel as a connection exception. Read the sanitized error category rather than assuming every failure produces a response object with a status field. ## Check these settings in order Change one setting at a time so the result is attributable. Begin with the minimal cURL request in the connection guide. - Copy the exact gateway hostname, protocol and port for the allocation. - Use proxy credentials, not your email address or dashboard password. - Remove accidental whitespace and confirm credentials are active. - When using a URL, encode username and password components correctly. - If using IP allowlisting, verify the current public egress IP and the product’s supported method. - Remove undocumented location or session suffixes and reintroduce supported settings one at a time. ## Run one diagnostic request Use a known permitted destination and a short timeout. In cURL, --proxy-user with only the username prompts for the password. In Requests, keep credentials outside source code and configure both destination scheme keys. Do not retry a known bad credential in a tight loop. If the result changes to a TLS failure, timeout or destination status, diagnose that new layer separately. Keep certificate verification enabled throughout. ## Identify who sent the challenge A 407 response concerns the proxy’s authentication boundary. The Proxy-Authenticate header describes its challenge. A 401 response concerns authentication to the requested resource. The credentials and client options used at those boundaries are not interchangeable. ## Identify who sent the challenge: Preserve the exact symptom Record whether you observed an HTTP status from the proxy, a library exception wrapping that status, or only a timeout. Capture the challenge header where available, after removing secrets and unrelated identifiers. A generic application message such as connection failed is not enough to conclude that the gateway rejected a password. ## Identify who sent the challenge: Check the active allocation before editing code Confirm the gateway hostname, port, username and supported authentication method from the active allocation. Account-login credentials may be different. If a credential has been rotated or an allocation disabled, an older local copy can be structurally correct yet no longer usable. ## Distinguish a wrong value from a malformed value Credentials can be valid in a dashboard but incorrectly supplied to the client. A password containing URL separators needs component encoding when placed in a URL. A separate authentication option follows that client’s own argument rules. Keep the format and the underlying value distinct during diagnosis. ## Distinguish a wrong value from a malformed value: Make one formatting change Choose one documented credential format and test it with the same bounded request. Avoid simultaneously changing the gateway, password, port and client. If the next result differs, that controlled change gives you a better clue about which boundary was wrong. ## Distinguish a wrong value from a malformed value: Read the documented authentication method A username and password do not specify every detail of how a client authenticates. Use the method the gateway documents and the option your client supports. Do not add an unrelated destination Authorization header and assume it satisfies a proxy challenge. ## Use a small diagnostic loop Begin with one permitted request and explicit timeouts. Keep destination TLS verification enabled. Review the resulting status or exception and change one relevant configuration item. Repeated attempts with the same incorrect setup add noise rather than evidence. ## Use a small diagnostic loop: tradeoffs ### Where it helps - A specific status gives a clearer starting point than a generic connection failure. - A bounded request and sanitized configuration make support evidence reproducible. - Separating proxy and destination credentials avoids changing the wrong system. ### What to account for - Some clients wrap the challenge in an exception that needs inspection. - A corrected 407 can expose an unrelated DNS, TLS or destination issue next. - A diagnostic trace can reveal credentials unless reviewed before sharing. ## When to ask for help If the documented settings still produce 407, send the provider a concise sanitized record: time, active product category, client/version, gateway host and port, selected authentication method, response status and challenge details. Share account or allocation identifiers only through the appropriate support channel. ## When to ask for help: Treat a new result as new evidence If the request changes from 407 to a destination response, the authentication boundary may now be satisfied. Confirm that interpretation rather than repeatedly rotating credentials. A destination 403, 429 or unexpected page requires its own diagnosis and access-policy review. ## When to ask for help: Keep the support record safe Do not include the literal password, a full credential-bearing proxy URL, session cookies or a private destination query. A useful record shows the request structure and observed boundary without giving another reader the ability to reuse the allocation. ## Send support a useful, sanitized report Include the allocation or order identifier, timestamp with timezone, client version, gateway host and port, and the exact error category. Say whether the failure is consistent and whether another permitted endpoint behaves the same way. Remove passwords, tokens, cookies and full credential-bearing URLs from traces. First confirm that your allocation is active and that you are using its current gateway, port and credentials. This article explains the protocol; it is not a guarantee that every authentication failure has the same cause. ## Which approach should you choose? Fix the authentication boundary first, then reclassify the next result. A changed error can mean you have moved to a different stage of the connection. ### A clear 407 response Inspect the proxy challenge and verify gateway credentials and the client’s proxy-authentication configuration. ### A timeout or TLS error Diagnose connection establishment or certificate trust separately; do not assume every proxy failure is 407. ### Authentication succeeds but output is wrong Validate the destination response and access conditions instead of changing a now-working password. ## What does 407 Proxy Authentication Required mean? The proxy did not receive valid authentication for the request. Its Proxy-Authenticate response header describes the authentication challenge. Check proxy credentials and authentication configuration separately from credentials for the destination website. ## How to fix error 407 Proxy Authentication Required? Check the exact gateway, port, active proxy credentials and supported authentication method. Make sure your client sends proxy authentication; encode credential components when using a URL. Retest one permitted request with a timeout. If the error changes, diagnose the new network or destination failure separately. ## Is 407 the same as 401? No. 407 concerns authentication to the proxy. 401 concerns authentication to the requested resource. ## Will rotating the IP fix bad credentials? Changing an exit does not repair incorrect gateway authentication. Verify the credentials and supported authentication method first. ## Which response header describes the proxy authentication challenge? Proxy-Authenticate describes the challenge associated with a 407 response. Inspect it where your client makes it available, and distinguish the proxy’s authentication method from destination authentication. ## Sources - [curl: proxy authentication](https://everything.curl.dev/usingcurl/proxies/auth.html) — checked 2026-10-16 - [RFC 9110: 407 Proxy Authentication Required](https://www.rfc-editor.org/rfc/rfc9110.html#name-407-proxy-authentication-req) — checked 2026-10-16 ## Related reading - [How to use a proxy with cURL](https://miproxy.io/guides/curl-proxy-guide) - [Use an authenticated proxy with Python Requests](https://miproxy.io/guides/python-requests-proxy-guide) - [Residential vs. datacenter proxies: choose by the job](https://miproxy.io/blog/residential-vs-datacenter-proxies) - [Rotating vs. sticky proxies: match the session to the task](https://miproxy.io/blog/rotating-vs-sticky-proxies) - [Non-expiring proxy bandwidth: what to check before buying](https://miproxy.io/blog/non-expiring-proxy-bandwidth) --- Source: https://miproxy.io/compare/miproxy-vs-iproyal Updated: 2026-10-17 # MiProxy vs. IPRoyal: compare terms before the price Compare IPRoyal and MiProxy package terms, connection settings and account workflows using a practical evaluation checklist. ## Quick answer IPRoyal publishes a self-service residential offer. MiProxy combines packages, connection settings and usage in one workspace, with access currently limited to approved accounts. Compare availability and exact package terms before a permitted workload test. This MiProxy-authored review is not an independent performance benchmark. ## Introduction If you need a residential proxy today, the first question is whether the selected product can actually deliver a usable allocation. A polished portal, a published product page and a historical connection check are three different kinds of evidence. This comparison explains IPRoyal’s published offer alongside MiProxy’s package and connection-management workflow. Use the same checklist for availability, terms, session needs and operating cost. ## Editorial disclosure MiProxy wrote this comparison and is one of the products described. IPRoyal capabilities are vendor statements checked October 16, 2026. There are no independent performance scores, uptime conclusions, live migration results or implied feature parity. ## How this guide was researched A dated source-based comparison, authored by MiProxy. IPRoyal statements are attributed to its official residential page; MiProxy descriptions reflect its documented workflow. No competitor purchase, network benchmark or feature-parity test was performed. - Account access, product availability and activation requirements. - Published protocols, targeting and session options. - Non-expiring traffic language versus exact checkout conditions. - What evidence a buyer needs before moving a real workload. ## Quick comparison table MiProxy status and IPRoyal vendor statements, checked October 16, 2026. No comparative traffic test. | Decision | MiProxy | IPRoyal | | --- | --- | --- | | Current evaluation | Access limited to approved accounts; confirm product availability | Publishes a self-service residential offer | | Live delivery evidence here | Small residential, mobile and unlimited residential checks | Official product information; not independently tested | | Connection features | Verify the actual allocation before live use | Lists HTTP(S), SOCKS5, targeting and session options | | Bandwidth expiry | Read the exact selected plan | Advertises non-expiring residential traffic | | Appropriate next step | Evaluate the portal and confirm live availability | Verify current checkout and terms | ## What IPRoyal publishes Checked October 16, 2026: IPRoyal advertises non-expiring residential traffic, HTTP(S) and SOCKS5, location targeting, and rotating or sticky sessions. Its product page links pricing, documentation and a self-service dashboard. These are vendor statements; we have not independently validated them. Use the linked source to check the current package, minimum purchase and payment mode. A headline starting rate may require a larger purchase than your workload needs. ## Where MiProxy stands today MiProxy brings plans, allocations, connection settings and usage views into one workflow. Check the product’s availability and wait for an active allocation before using its connection details. Small residential, mobile and unlimited residential allocations completed HTTP and SOCKS5 connection checks. That evidence does not validate every present package or establish comparable pool coverage, uptime, support hours or target success. There is no basis here for a claim that MiProxy is faster or cheaper for your workload. ## When another provider may be the better fit If you need immediate access, confirm account eligibility and activation timing before choosing a package. Compare each provider’s order flow, connection controls and terms against your deadline. Ask each provider for the same evidence: the selected plan’s activation state, supported protocol, requested location, expiry, renewal and refund terms. Run any paid network test only with an agreed budget and permitted destination. ## IPRoyal: review the published residential offer IPRoyal’s official residential page supplies a useful starting point for an evaluation: protocols, location controls, session options and a non-expiring traffic proposition. Those details help formulate questions for the selected plan. They do not, by themselves, establish the result your own workload will achieve. ## IPRoyal: review the published residential offer: What non-expiring traffic contributes to the decision For intermittent work, a balance that remains available under the selected terms can change the purchasing calculation. Compare the minimum amount you must buy with the traffic you expect to consume. Keep account conditions and the exact product category alongside the non-expiry statement rather than generalizing it to every IPRoyal offer. ## IPRoyal: review the published residential offer: Turn listed features into concrete requirements If your task needs a supported protocol, one location and a bounded continuity window, ask how those requirements map to the current plan. A feature appearing on a product page is a reason to inspect its documentation. It is not a measurement of location accuracy, exit persistence or destination acceptance. ## IPRoyal: review the published residential offer: tradeoffs ### Where it helps - Publishes a residential offer with protocol, targeting and session information that a buyer can examine. - Advertises non-expiring residential traffic, relevant to an intermittent-use comparison when its terms fit. ### What to account for - Published capabilities have not been independently exercised in this review. - The selected checkout and documented limits still need review; a headline offer is not a complete workload budget. ## MiProxy: review packages and connection management MiProxy provides packages, orders, connection controls and timestamped usage views. Small connection checks do not establish network-wide performance, long-term reliability or exact-location availability. ## MiProxy: review packages and connection management: What you can evaluate in the portal Look at whether the package unit is understandable, whether an order preserves its terms, whether connection options match the allocation and whether usage observations show their time. Confirm activation and supported settings for the workload you intend to run. ## MiProxy: review packages and connection management: What must be established before migration A real migration needs more than successful portal navigation: an actual allocation, documented supported behavior, a permitted sample against your destination and commercial/operational terms suitable for the task. Keep each open requirement visible. A previous small smoke run cannot substitute for this present-plan review. ## MiProxy: review packages and connection management: tradeoffs ### Where it helps - Lets an invited reviewer examine the relationship between plans, orders, connection settings and usage. - Shows order progress and allocation status before connection setup. ### What to account for - Public signup and production payments are closed. - Access is limited to approved accounts; confirm availability before planning a workload. - This review does not establish comparable coverage, support commitments or reliability. ## Three buyer situations produce different decisions A provider comparison is useful when it narrows an actual choice. Start with the situation, then read the relevant evidence rather than treating every table row as equally important. ## Three buyer situations produce different decisions: A job must start this week Prioritize activation timing and the exact usable product. Confirm the provider’s terms and make a small permitted request before committing to a deadline. ## Three buyer situations produce different decisions: Usage comes in occasional bursts Build an estimate for minimum purchase, expected consumed traffic and unused balance. Review the non-expiry claim in its actual context. Do not compare IPRoyal’s published live terms with an unvalidated MiProxy production promise that has not been established. ## Three buyer situations produce different decisions: The team is evaluating a workspace Review MiProxy’s ordering and connection controls alongside the selected package’s availability. Evaluate usability and network behavior separately; a clear interface does not establish a performance advantage. ## Keep a dated comparison record Save the official product URL and the exact checkout conditions you considered, plus the date and product category. If terms later change, the record explains the original decision without implying that the old statement remains current. Recheck the selected offer before a purchase or migration. - Current activation and supported endpoint details. - Minimum payment, non-expiry conditions and renewal behavior. - Task-specific location and continuity requirements. - Observed correct output and total cost, if a separately authorized evaluation is performed. ## Use the same acceptance sheet Record the total payment and traffic used, then count correct outputs rather than HTTP 200 responses alone. Keep the test date, geography, timeout, sample size and failures. Compare session continuity and support answers alongside cost. A provider feature list is a starting point, not your result. - Verify current package terms at checkout. - Check credential setup and the first permitted request. - Measure bytes and correct output on a bounded sample. - Keep renewal and cancellation conditions with the decision. ## Which approach should you choose? Compare each provider’s current package and activation requirements. MiProxy may fit teams that want package, order and connection management together; confirm account access and supported products first. ### You need live traffic immediately Verify IPRoyal’s current checkout, activation and workload fit; this article does not establish a live MiProxy replacement. ### You are choosing around unused traffic Read IPRoyal’s dated non-expiry terms and compare minimum payment, restrictions and likely consumption. ### You want to review the MiProxy workspace Assess its package, order and connection workflow, and verify availability and the settings required for your task. ## Is this an independent IPRoyal benchmark? No. MiProxy wrote this decision guide. Competitor features are attributed to its official page, and no comparative traffic test was run. ## Does MiProxy offer a proven replacement today? Confirm account access, product availability and an active allocation before planning a migration. Validate your own permitted workload; package listings alone do not establish suitability. ## What does IPRoyal publish about residential traffic expiry? Its official residential page advertises non-expiring traffic, as checked October 16, 2026. Treat that as a dated vendor claim and review the exact selected product, account conditions and checkout terms before purchasing. ## Can I compare IPRoyal and MiProxy on uptime from this article? No. This article contains no comparative uptime measurement, competitor allocation test or production service-level validation. Published features and a historical small MiProxy smoke sample do not establish an uptime comparison. ## What evidence should I keep before choosing either service? Save the selected offer, dated terms, intended task, supported endpoint and acceptance criteria. If a separate evaluation is authorized, record correct output, traffic and failures without presenting a small sample as a general reliability guarantee. ## Sources - [IPRoyal residential proxies — vendor claims, checked October 16, 2026](https://iproyal.com/residential-proxies/) — checked 2026-10-16 ## Related reading - [MiProxy vs. Decodo: a practical evaluation checklist](https://miproxy.io/compare/miproxy-vs-decodo) - [Non-expiring proxy bandwidth: what to check before buying](https://miproxy.io/blog/non-expiring-proxy-bandwidth) - [Residential vs. datacenter proxies: choose by the job](https://miproxy.io/blog/residential-vs-datacenter-proxies) - [Rotating vs. sticky proxies: match the session to the task](https://miproxy.io/blog/rotating-vs-sticky-proxies) - [How to use a proxy with cURL](https://miproxy.io/guides/curl-proxy-guide) --- Source: https://miproxy.io/compare/miproxy-vs-decodo Updated: 2026-10-17 # MiProxy vs. Decodo: a practical evaluation checklist Compare Decodo and MiProxy residential connection options, package terms and workflows, keeping vendor claims separate from observed results. ## Quick answer Decodo publishes a residential service with multiple billing and session options. MiProxy provides package and connection management for approved accounts. Compare availability, renewal terms and task requirements before choosing. ## Introduction Decodo publishes a residential proxy service with different billing and connection options. MiProxy combines package and connection management in one workspace. Compare current access requirements and the exact package terms first. This guide helps you inspect published features without turning them into a performance claim. It explains the commercial and operational questions to resolve when choosing a proxy service. ## Editorial disclosure Decodo facts are attributed vendor statements checked October 16, 2026. No conclusion about comparative speed, pool quality, support responsiveness or cost per result is supported by this review. ## How this guide was researched A source-based, MiProxy-authored evaluation of Decodo’s official residential page and MiProxy’s documented workflow. We did not purchase a Decodo allocation or conduct a head-to-head traffic, pricing or support test. - Usable current allocation versus portal-only evaluation. - Published residential protocols, targeting and session modes. - Subscription and pay-as-you-go terms for the intended consumption pattern. - Responsibility for collection, parsing, failure handling and operational support. ## Quick comparison table MiProxy status and Decodo vendor statements, checked October 16, 2026. No comparative traffic test. | Decision | MiProxy | Decodo | | --- | --- | --- | | Current evaluation | Access limited to approved accounts; confirm product availability | Publishes a residential proxy service | | Live delivery evidence here | Small residential, mobile and unlimited residential checks | Official product information; not independently tested | | Connection features | Verify the actual allocation before live use | Lists HTTP(S), SOCKS5, targeting and session options | | Billing | Read the exact selected plan | Lists subscriptions and pay-as-you-go billing | | Appropriate next step | Evaluate the portal and confirm live availability | Verify current checkout and terms | ## What Decodo publishes Checked October 16, 2026: Decodo lists HTTP(S) and SOCKS5, rotating and sticky sessions, location targeting, monthly subscriptions and pay-as-you-go residential billing. These statements come from Decodo’s product page; this article does not independently verify its performance or coverage. Inspect the current plan and checkout for commitment, minimum payment, taxes and trial conditions. Do not compare a large-volume subscription headline with a small prepaid purchase as though the commitments were identical. ## How the MiProxy workflow works MiProxy connects package discovery, ordering, connection settings and usage in one workspace. Wait for an active allocation and use its supplied connection details before making requests. Small residential, mobile and unlimited residential allocations completed connection checks. MiProxy has not established equivalent coverage, session duration, managed scraping, production support commitments or comparative reliability for its current catalog. ## Choose around an operational requirement A buyer who needs immediate access should confirm account eligibility, product availability and activation timing with each provider. Then evaluate the exact connection settings and package terms needed for the task. Write a concrete requirement: for example, a permitted daily check from one country with a five-minute continuity window. Ask the provider how that requirement maps to its product and what happens if the exit disappears mid-task. Avoid selecting a plan on advertised pool size alone. ## Decodo: separate the residential product from the wider catalog The official residential page lists HTTP(S), SOCKS5, location targeting, rotating/sticky sessions, subscriptions and pay-as-you-go billing. Use those published categories to identify the product you need. A provider’s wider range of services should not be assumed to be included in one residential plan. ## Decodo: separate the residential product from the wider catalog: Start with the current commercial commitment A subscription and a pay-as-you-go purchase can distribute cost differently even when both are described using a per-GB figure. Compare the total payment, allowance, billing period, renewal behavior and applicable unused-traffic conditions. Use the rate that matches your intended commitment rather than an unrelated high-volume headline. ## Decodo: separate the residential product from the wider catalog: Check the documented connection behavior Verify protocol support, endpoint details and the session mode for the actual plan. Decide whether your task needs continuity or independent routing, then examine how the documentation defines it. A listed sticky feature is not evidence of permanent address ownership or uninterrupted continuity. ## Decodo: separate the residential product from the wider catalog: tradeoffs ### Where it helps - Publishes multiple residential billing models for a buyer to compare against their usage pattern. - Lists protocols, targeting and session controls that can be checked in product documentation. ### What to account for - This comparison has not independently verified activation, performance or exact workload fit. - Choosing among published options still requires reviewing the exact plan and commercial conditions. ## MiProxy: check access and package availability Approved MiProxy accounts can manage packages, orders and connection settings. Confirm the selected product is available and the allocation is active; dashboard feature lists alone do not establish workload suitability. ## MiProxy: check access and package availability: Assess clarity before capability parity Check whether a package clearly identifies its unit and access period, whether the order preserves quantity and expiry, and whether usage views distinguish a snapshot from a real-time promise. Those are meaningful workspace qualities. They do not establish that MiProxy provides the same live service as Decodo. ## MiProxy: check access and package availability: Keep the historical evidence narrow MiProxy’s earlier residential sample verified a small set of connection observations. It did not establish every current catalog product, global targeting accuracy, comparative reliability or production support terms. Ask for the missing evidence rather than filling it with assumptions from another provider’s documentation. ## MiProxy: check access and package availability: tradeoffs ### Where it helps - Brings package ordering and connection management into one workspace. - Shows allocation status and timestamped usage. ### What to account for - Public purchases and production payments remain unavailable. - Account access and activation must be confirmed before use. - No head-to-head Decodo comparison substantiates parity or superiority. ## Match the billing option to the work Before choosing a billing label, estimate how many correct outputs the project needs, how much traffic a bounded representative sample consumes and how frequently the work runs. Keep retries and the collection client’s assets in the estimate. A subscription allowance and an ad hoc traffic purchase should be evaluated over a stated period. ## Match the billing option to the work: A recurring reporting job For regular work, compare the full period’s commitment with expected use. Record renewal, cancellation and unused-traffic rules. Include the cost of maintaining the client and parser; a stable per-GB expense is not a complete reporting budget. ## Match the billing option to the work: An irregular research project For variable usage, compare minimum payment and the conditions governing the remaining balance. Verify actual terms rather than assuming that pay-as-you-go always means no expiry, no minimum or no other restrictions. ## Match the billing option to the work: A team that needs a finished dataset If the output requirement is parsed search results, identify the exact API that supplies the needed fields and location context. Do not treat a residential proxy subscription as an implicit entitlement to a managed SERP service. Compare documented endpoints and responsibilities separately. ## Ask both sides the same operational questions A useful decision record contains more than a list of features. Write the permitted destination, required output, intended geography, continuity window, schedule and acceptance rule. If a provider cannot map the current plan to those requirements, keep the gap open rather than awarding a score. - Which exact product can be activated now? - What payment and renewal conditions apply at the selected commitment? - What does the client still need to handle? - Which observations would demonstrate that the task succeeded? - What support path and operational terms apply to this specific product? ## Compare evidence with a bounded test For a future authorized trial, hold destination, sample, client version and timeout constant. Count correct records, total bytes, failures and elapsed time. Add implementation and support time to the cost rather than using only price per GB. This guide is authored by MiProxy and uses official competitor sources. No head-to-head purchase, traffic benchmark or feature-parity test was performed. Recheck source pages before making a purchase because product and commercial terms can change. - Availability and activation of the exact plan. - Protocol, location and continuity required for the task. - Minimum payment, expiry, renewal and cancellation. - Useful results per dollar, including maintenance. ## Which approach should you choose? Compare the exact available residential packages, activation requirements and connection controls. Choose using your workload, budget and required session behavior, rather than an assumed performance advantage. ### Predictable recurring workload Examine Decodo’s actual subscription allowance, commitment, renewal and unused-traffic rules. ### Variable workload Compare the current pay-as-you-go conditions with likely consumption and minimum payment. ### A requirement for parsed search data Evaluate the exact managed data product separately; a residential connection alone does not supply structured rankings. ## Has MiProxy beaten Decodo in a traffic test? No comparative traffic test was run. This is a dated evaluation guide with attributed vendor information and explicit evidence limits. ## Does a proxy subscription include parsed search results? Do not assume so. A raw proxy connection and a managed scraping or SERP API are separate capabilities. Check the exact selected product. ## Does Decodo list both subscriptions and pay-as-you-go residential billing? Yes, its official residential page listed those billing options when checked October 16, 2026. Review the current selected plan for minimum payment, commitment, renewal and unused-traffic conditions. ## Does a published sticky-session feature prove permanent IP ownership? No. A sticky session requests continuity under product-specific conditions. Permanent or static allocation terms are separate and must be checked in the exact offer. ## What can I manage in MiProxy? Approved accounts can manage packages, orders, connection settings and usage. Confirm product availability and validate the required behavior on an active allocation before replacing an existing service. ## Sources - [Decodo residential proxies — vendor claims, checked October 16, 2026](https://decodo.com/proxies/residential-proxies) — checked 2026-10-16 ## Related reading - [MiProxy vs. IPRoyal: compare terms before the price](https://miproxy.io/compare/miproxy-vs-iproyal) - [Rotating vs. sticky proxies: match the session to the task](https://miproxy.io/blog/rotating-vs-sticky-proxies) - [Non-expiring proxy bandwidth: what to check before buying](https://miproxy.io/blog/non-expiring-proxy-bandwidth) - [Residential vs. datacenter proxies: choose by the job](https://miproxy.io/blog/residential-vs-datacenter-proxies) - [How to use a proxy with cURL](https://miproxy.io/guides/curl-proxy-guide) --- Source: https://miproxy.io/blog/proxies-vs-serp-api Updated: 2026-10-17 # Raw proxies or a SERP API for SEO reporting? Choose between proxy connections and a managed SERP API by comparing parsed results, location controls, maintenance and total reporting cost. ## Quick answer Choose a SERP API when your main requirement is structured search data and you want to reduce collection and parsing work. Choose raw proxy connections only when you need transport control and can maintain the collection workflow. Neither option guarantees an exact match to every person’s search results. ## Introduction An SEO report needs fields and context: the query, result URLs or positions, location, language, device and retrieval time. A proxy connection is only one possible component of collecting that data. This guide compares the work you keep when choosing raw transport with the work a documented SERP API supplies. Start from the report specification, then evaluate collection, parsing, maintenance and commercial terms together. ## Editorial disclosure This compares responsibilities and documented parameters, not provider performance or permission for every possible use. API-generated answers and scraper citation panels inform topic selection, not verified search-volume demand for every subsection. MiProxy does not provide a managed SERP product. ## How this guide was researched A source-based workflow comparison informed by saved proxies-for-SEO keywords, a US SERP snapshot and questions about search-reporting workflows. Official SerpApi, DataForSEO and Google documentation support parameters and access-policy statements; no comparative collection benchmark was run. - Required output fields and their documented definitions. - Location, language, device and time as separate context inputs. - Who handles collection, parsing and failure classification. - Complete reporting cost and the selected data source’s access conditions. ## Quick comparison table Compare the work you retain, then verify the chosen product’s actual behavior. | Responsibility | Raw proxy connection | Managed SERP API | | --- | --- | --- | | Primary output | A connection; your client receives the destination response | Provider-defined result fields | | Parsing | Your application maintains it | Provider handles documented fields | | Location context | Exit location plus your request configuration | Documented location and search parameters | | Failure handling | You classify transport and content failures | You handle API statuses and missing fields | | Cost comparison | Traffic, retries, parsing and maintenance | Billable tasks, options and integration | ## Start with the report you need to deliver An agency report might need organic positions, destination URLs, a local pack and a timestamp. A raw proxy does not produce those fields. It transports a request; your application still needs to collect the permitted response, interpret its structure and decide whether the output is complete. A SERP API provides a documented response model. That can reduce parsing work, but check that the exact endpoint covers the elements your report requires. Organic results, map results and AI answer features can have different options and availability. A returned task is not automatically a complete report. ## Treat location, language and device as separate inputs The official SerpApi search documentation exposes location, country, language and device controls. DataForSEO’s organic endpoint similarly documents location, language and device parameters. These examples show why changing a proxy exit country alone is an incomplete reporting specification. Save the keyword, engine, location, language, device, retrieval time and relevant options with each observation. Compare equivalent settings across reporting periods. If a result differs from a browser check, inspect the request context and timing before labeling either observation wrong. A reporting method needs a stable definition, rather than a promise to reproduce every personalized search. ## Budget for maintenance as well as requests For a raw connection workflow, estimate traffic, retries, client execution, parser changes, monitoring and engineering time. For an API, inspect billable tasks, result depth, optional features and failed-task rules. Compare the cost of a complete, correct report using the same required fields. Raw connections can suit teams that need flexible transport for authorized workflows and already maintain collection infrastructure. A documented API can suit teams whose main job is analyzing search data. Ask what you would have to repair when a response format changes, and who owns that work during a reporting deadline. ## Choose a permitted data source Google’s published spam policies describe automated queries without express permission, including rank-checking traffic, as machine-generated traffic. A proxy changes a network route; it does not grant permission to query a service. Review the search engine’s access requirements and the selected data provider’s terms before operating a collection workflow. This is a tooling decision guide, not a claim that any named third-party service has permission for every use. Establish which data you are allowed to retrieve and use before deciding how to transport or process it. ## Describe one report row before choosing infrastructure A row might contain a query, a destination URL, an organic position, a location setting and a retrieval time. Another report may need a local pack or an AI answer citation. Those are different outputs. State which elements are required and how a missing element affects completeness. ## Describe one report row before choosing infrastructure: Agree on what a position means A report should identify the result type being counted and the context under which it was retrieved. Organic ordering, local results and other search features should not be silently merged. Use the selected provider’s documented field meanings and preserve enough context to interpret later changes. ## Describe one report row before choosing infrastructure: Keep comparisons equivalent When reporting over time, keep engine, query, location, language, device and relevant options consistent. If a parameter changes, record it. A different result does not automatically reveal a ranking movement if the collection context also changed. ## Managed SERP API: inspect the response contract A documented API can supply structured fields and expose search parameters. That reduces some work your application would otherwise maintain. It also creates a contract you need to inspect: which elements are supported, how absence is represented and how task status differs from report completeness. ## Managed SERP API: inspect the response contract: tradeoffs ### Where it helps - Documented fields can reduce custom parsing work for covered result elements. - Explicit location, language and device options make collection context easier to record. - A response schema gives the integration a defined structure to validate. ### What to account for - The exact endpoint may not supply every feature your report requires. - Billable options, result depth and error rules still need commercial review. - An API result does not promise the exact experience of every personalized browser session. ## Raw proxy connection: account for the work you retain A transport product does not define the search result model. Your client still needs an allowed source, request configuration, execution policy, parser and a method for deciding whether the output is complete. That responsibility remains even if the gateway connection itself works. ## Raw proxy connection: account for the work you retain: tradeoffs ### Where it helps - Leaves transport and client design under the application team’s control. - Can fit separately permitted workflows whose output is broader than a SERP API response. ### What to account for - The application retains collection, parsing and maintenance responsibilities. - Location context is not fully defined by the exit country alone. - A successful HTTP response can still lack the report fields you need. ## Plan for a missing field before a reporting deadline Define what happens when a task returns no usable result: retry within a bound, mark the row incomplete, or send it for review. Keep API task status and content validation separate. A completed transport request is not the same event as a complete client report. ## Plan for a missing field before a reporting deadline: Record quality without inventing precision Save the required fields, timestamp and collection settings with each observation. If a source omits an element, preserve that absence rather than substituting a value from a different context. A consistent incomplete-data policy is more useful than a table that looks complete but cannot be explained. ## Plan for a missing field before a reporting deadline: Compare one reporting period For raw collection, include traffic, retries, execution and parser maintenance. For an API, include the chosen tasks, options, integration and completeness checks. Divide the relevant cost by correct complete report rows using the same definition on both sides; do not compare unrelated headline billing units. ## Where MiProxy fits in this decision MiProxy provides proxy packages, connection controls and usage information. Your application handles fetching, parsing and validation. MiProxy does not provide a managed SERP response, parsed rankings or a promise of search-engine access. If your immediate need is a dependable SEO report, evaluate the exact documented data product that supplies your required fields. If you need a proxy connection for a separately permitted workflow, first confirm a real allocation and its supported behavior. Buying a transport product when you need a finished dataset adds work to every report. ## Which approach should you choose? Use a documented SERP data product when structured search output is the main requirement and its fields fit the report. Choose raw transport only when you need that control and can maintain the full permitted workflow. ### An analyst needs structured rankings Check a SERP API’s exact response model, required result elements and location/device controls. ### An engineering team maintains permitted collection Budget the client, parser, retries, monitoring and context recording alongside proxy traffic. ### The requested report lacks a clear definition Define fields and measurement context before buying either product. ## Does a residential proxy give me accurate local rankings? A residential exit alone does not define a local ranking measurement. Record location, language, device, search context and time, and validate the fields required by your reporting method. ## Is a SERP API always cheaper than raw proxies? No universal price conclusion follows. Compare a complete, correct report including API options or proxy traffic, retries, execution, parsing and maintenance. ## Does MiProxy return parsed search results? No. MiProxy provides proxy connections rather than managed search results. Your application must fetch permitted pages, parse responses and validate the data. ## Which context should I save with a search observation? Record the query, engine, location, language, device, retrieval time and relevant options. Keep the result type and required fields clear so that later comparisons use equivalent settings. ## Does a completed API task prove my report is complete? No. Validate that the response contains the fields and search elements your report requires. Distinguish task status from content completeness and preserve missing-data states rather than inventing values. ## Sources - [SerpApi: Google Search API parameters](https://serpapi.com/search-api) — checked 2026-10-16 - [DataForSEO: organic live advanced endpoint](https://docs.dataforseo.com/v3/serp-se-type-live-advanced/) — checked 2026-10-16 - [Google Search: machine-generated traffic policy](https://developers.google.com/search/docs/essentials/spam-policies#machine-generated-traffic) — checked 2026-10-16 ## Related reading - [Residential vs. datacenter proxies: choose by the job](https://miproxy.io/blog/residential-vs-datacenter-proxies) - [Rotating vs. sticky proxies: match the session to the task](https://miproxy.io/blog/rotating-vs-sticky-proxies) - [Non-expiring proxy bandwidth: what to check before buying](https://miproxy.io/blog/non-expiring-proxy-bandwidth) - [How to use a proxy with cURL](https://miproxy.io/guides/curl-proxy-guide) - [Use an authenticated proxy with Python Requests](https://miproxy.io/guides/python-requests-proxy-guide)