Rotating residential
For workloads that need residential routing and session configuration. Estimate traffic from retries and browser assets alongside compute and maintenance costs.
Explore residential proxies →Choose between a managed scraping API, your own crawler with proxies, and interactive Browser/MCP tasks. Compare inputs, outputs, operating responsibility and costs.
Official sources and review dates are listed in each guide.
| Dimension | Crawler API | Proxy | Browser / MCP |
|---|---|---|---|
| Input | Interface key + parameters | Your HTTP requests + proxy credentials | AI instructions + browser actions |
| Output | Task status, result and credits | Proxied responses; your parser extracts the data | Browser observations and task-specific output |
| Responsibility | Service executes; you validate the result | You own scheduling, rendering, parsing and retries | AI client orchestrates tools; you handle verification |
| Best fit | Scheduled collection and content pipelines | Custom crawlers and existing infrastructure | Multi-step interaction, testing and human takeover |
| Cost unit | Credits by interface and parameters | Traffic or IP/time/bandwidth, by product | Current MIYAIP guidance: one call per successful task start |
| Connection | HTTPS + console login token | Proxy authentication in your own client | Streamable HTTP + dedicated MCP key |
A credit is not a useful result. Compare actual spend against data that passes your acceptance checks. Read the cost guide →
A proxy supplies a network route. Your application still chooses URLs, runs a browser if needed, parses data, limits retries and stores results. This fits teams with an existing crawler or custom execution requirements.
For workloads that need residential routing and session configuration. Estimate traffic from retries and browser assets alongside compute and maintenance costs.
Explore residential proxies →Consider this option when datacenter routing meets the target requirements. Compare IP and duration terms; routing alone does not guarantee target acceptance.
Explore datacenter proxies →Use an AI client to operate a remote browser for navigation, extraction, screenshots or testing. Choose this model when the task needs interaction rather than a single predefined data interface.
Connect with a dedicated MCP key over Streamable HTTP. Current product guidance counts a successful browser_start_task or browser_run_test start as one call; actions within that task do not add calls. Each running task uses a concurrency slot.
Explore Browser/MCP →Set an adequate tool timeout, validate the output and use human takeover for CAPTCHA, QR or SMS verification. A created key does not imply available task credits or concurrency.
Configure your MCP client →Start with the product you use: compare network types, session behavior and purchase requirements.
Compare rotating residential traffic and fixed ISP access separately.
Map your proxy settings and understand the Smartproxy rebrand.
Choose between datacenter, static ISP and rotating residential access.
Choose the proxy or managed scraping product your workload needs.
Separate proxy access, crawler tasks and interactive browser work.
Evaluate residential or mobile access, locations and session behavior.
Match a supported task, its request contract, usable output and billing model.
Compare package costs and request formats for small projects.
Compare JavaScript rendering, credits and concurrency.
Review rendering requirements, billing and request migration.
Compare your scraping configuration and result contract.
Match required fields, asynchronous tasks and workload costs.
Map request options, rendering needs and the full job lifecycle.
Review the interface, choose a package and test the pages you actually need.