Access our peer-hosted network of 100% residential IPs via a standard HTTP proxy interface. Route scraping, research, or automation through real home connections — never flagged, never datacenter-blocked.
Dreamcore uses a peer-hosted residential network. Real people install our app and share a small amount of idle bandwidth — you route your traffic through their IP, they earn $1/GB, and you get authentic residential exits.
Apply below, get approved within 24 hours, and receive your API key by email. No hardware to set up.
Point any HTTP library at our gateway (host:3002) using your API key as the proxy username. Works with any language.
By default you get a rotating residential IP. Add the X-Target-Country header to pin a country, or X-Target-Device-Id for a sticky session.
View your GB usage and cost in your dashboard. Billed per GB transferred — no monthly commitments on PAYG.
Residential IPs unlock access that datacenter proxies simply can't provide.
Bypass bot detection, CAPTCHAs, and IP blocks. Our residential IPs look like normal home users — no more failed requests from flagged datacenter ranges.
Access geo-restricted content, localized search results, and regional pricing data from any country. See what real users in each market see.
Test your app from real residential IPs across dozens of countries. Verify geo-targeting, localization, and CDN behavior as real users experience it.
Monitor for counterfeit listings, unauthorized resellers, and ad fraud from real residential vantage points that bypass automated detection.
Access financial data sources that restrict datacenter IP ranges. Gather pricing, rates, and market data reliably without blocks.
Manage multiple accounts without triggering rate limits or bans. Residential IPs are trusted by all major social platforms.
Pay only for what you use. No setup fees. No monthly minimums on PAYG.
• GB = bytes transferred — total of request + response payload. We count both directions.
• PAYG — billed at end of month per GB used at $9.99/GB. No minimum charge.
• Volume discounts automatically apply at 100 GB+. Contact us to lock in a rate.
• Failed requests (407, 403) consume no bandwidth — you're not charged for blocked connections.
• Fallback connections — if no residential node is available for your target country, the gateway falls back to the main server. This still counts as usage.
• No surprises — view real-time GB used in your dashboard at any time.
Standard HTTP CONNECT proxy. Works with every HTTP library in every language.
import requests PROXY_URL = "http://YOUR_API_KEY:[email protected]:3002" proxies = {"http": PROXY_URL, "https": PROXY_URL} # --- Rotating IPs (default) --- r = requests.get("https://httpbin.org/ip", proxies=proxies) print(r.json()) # {"origin": "residential.ip.address"} # --- Country targeting --- r = requests.get( "https://httpbin.org/ip", proxies=proxies, headers={"X-Target-Country": "GB"}, ) print(r.json()) # {"origin": "uk.residential.ip"} # --- Sticky session (always the same node) --- SESSION_DEVICE = "DEVICE_UUID" # from GET /api/b2b/available-nodes r = requests.get( "https://httpbin.org/ip", proxies=proxies, headers={"X-Target-Device-Id": SESSION_DEVICE}, ) print(r.json())
proxy.getdreamcore.com3002HTTP CONNECTProxy-Authorization: BasicYOUR_API_KEY:x (pwd)Base64(API_KEY:x)✅ Fully supportedProxy-Authorization: Basic <base64>Required. Auth your API key using HTTP Basic auth. Password can be anything (use "x").
X-Target-Country: USOptional. ISO alpha-2 country code. Routes through a residential node in that country.
X-Target-Device-Id: <uuid>Optional. Route through a specific node device for a sticky session.
Pass X-Target-Country to route through a node in that country. If no live node matches, the gateway falls back to the best available residential node globally.
USGBDEFRCAAUJPSGBRNLINSEITESMXPLKRUATRZANode availability is dynamic and depends on live peer connections.
Every new TCP connection may be assigned to a different residential node. This gives you a fresh IP address per request — ideal for scraping where you want IP diversity.
Always route through the same residential node by specifying its device ID. Use this when your target site requires session persistence (cookies, login state, etc.).
Contact [email protected] to get your available node device IDs.
200400403407504503The following destination ports are blocked at the gateway level to prevent abuse. Requests to these ports return HTTP 403 immediately and consume no bandwidth.
All other ports (80, 443, 8080, 8443, etc.) are allowed. HTTPS is fully supported.
The proxy uses HTTP Basic authentication via the Proxy-Authorization header. This is standard and supported by all HTTP libraries.
The format is YOUR_API_KEY:x (any string after the colon — we use "x" by convention). Base64-encode this string.
Most HTTP libraries handle this automatically when you provide the proxy URL in format http://API_KEY:x@host:3002. The library encodes the credentials and sets the header for you.
Built for professionals. Every feature you need to integrate confidently.
Restrict your API key to only be usable from specific IP addresses or CIDR blocks. If a request comes in from any IP not on your allowlist, the gateway rejects it instantly — even if the key is correct.
Poll real-time usage stats programmatically — integrate into your own dashboards, cost tracking systems, or alerting pipelines. No need to log in to a portal.
Go beyond country-level targeting. Route through nodes in a specific US state, Canadian province, or other sub-national region using the X-Target-Region header.
Issue separate API keys per project, team, or client. Track usage independently across keys. Revoke any individual key without affecting others. Keep your production and test keys separate.
Every layer of the Dreamcore stack is hardened against modern attack vectors. You can trust the infrastructure your business depends on.
Every API key issuer account requires two-factor authentication. No credential can be issued without 2FA verification.
API keys are generated using a CSPRNG with 192 bits of entropy. Statistically impossible to brute-force.
All API key comparisons use constant-time operations to prevent timing side-channel attacks.
Requests from high-risk jurisdictions are blocked at the edge before reaching any application code.
Lock your API key to specific IPs or CIDR ranges. A stolen key is useless without an allowlisted IP.
Every admin action is recorded with timestamp, actor ID, target, and IP. Full accountability.
All connections between your code, the gateway, and residential nodes use TLS 1.2+. No plaintext traffic.
We never log URL paths, query strings, request headers, bodies, or response content. Only hostname:port + bytes for billing.
All endpoints are rate-limited at the edge. Credential stuffing and brute-force attacks are blocked automatically.
A: 1 GB = 1,073,741,824 bytes of data transferred through the proxy — both request bytes (upload) and response bytes (download) combined. Failed authentication (407) and port-blocked (403) connections consume zero bytes.
A: Yes. The HTTP CONNECT protocol tunnels any TCP connection — including TLS. Your HTTPS requests are fully end-to-end encrypted. The proxy only sees the target hostname and port, never the content of encrypted traffic.
A: The gateway falls back to the best available residential node globally. If you need strict country enforcement (no fallback), contact us — we can configure per-key behavior for enterprise customers.
A: Use the X-Target-Device-Id header with a specific node's UUID. All requests bearing that header are routed through the same residential device as long as it's online. If the node goes offline, the gateway returns 503 — your code should fall back to a rotating request in that case.
A: All nodes are vetted by our gateway. We prefer residential IPs by design — our node selection algorithm explicitly prefers non-datacenter nodes. If only datacenter nodes are available (rare), the gateway will still route your request but you can verify IP reputation using any IP lookup API.
A: No. We log only: timestamp, bytes transferred, target hostname:port, and your API key — for billing and abuse prevention. We do not log URL paths, query strings, headers, request bodies, or response content. See our Privacy Policy.
A: There is no hard rate limit on PAYG or Volume plans. Concurrency is limited by available nodes in your target country — in practice, hundreds of simultaneous connections are supported. Enterprise customers can reserve dedicated node pools for guaranteed concurrency.
A: Residential peer latency averages 50–200ms to the proxy gateway. Add your target server's response time on top. Our node selection algorithm always picks the lowest-latency available residential node for your request.
A: No. .onion access is a VPN-side premium feature for end users, not available on the B2B proxy API. B2B proxy traffic is clearnet only.
A: Apply below and select 100–500 GB or 500+ GB. Once approved your account is automatically rated at $7.49/GB for Volume or custom rate for Enterprise. You can also upgrade an existing PAYG account — email [email protected].
Applications are reviewed manually to maintain quality. Most are approved within 24 hours. Credentials sent by email.
By applying you agree to our Terms of Service. No spam. Credentials sent within 24h.