Skip to main content
Documentation index: Fetch the complete index at developers.soax.com/llms.txt to discover all available pages.
SOAX is web access infrastructure: one platform that helps products access the public web reliably, at scale, in a world where the rules, defenses, and supply keep changing. In practice, that means you send your request through SOAX and it routes through one of our nodes instead of your own IP. The target website sees the node’s address, not yours. This lets you collect data at scale, access geo-restricted content, and avoid IP bans that would otherwise stop your requests.

​
What we offer

SOAX provides two proxy types today, plus two additional product surfaces in closed alpha.

​
Proxies

Residential proxies route your traffic through real home internet connections. We maintain a pool of over 155 million residential IPs across 195+ countries. These IPs belong to genuine ISP subscribers, which makes them very difficult for websites to detect and block. Residential proxies are the best choice for most web scraping, ad verification, and price monitoring tasks. Mobile proxies route traffic through real mobile carrier connections on 3G, 4G, and 5G networks. The mobile pool includes over 30 million IPs from carriers worldwide. They’re useful when you need to access mobile-specific content or when your target site treats mobile traffic differently from desktop. Not sure which one fits your use case? See Choosing the right proxy type.

​
In closed alpha

Headful Browser gives you stateful browser runtimes co-located with our exit nodes. It’s shaped for:
  • Long-horizon agent execution where each step waits on the previous response and latency compounds.
  • JavaScript-heavy or DOM-stateful targets that need a real browser, not a transport-level request.
  • Workflows that need cookies, scroll position, modal stacks, or conversation context preserved across multiple actions.
Web Data API provides structured retrieval for common public-web targets, so you can request data directly without writing or maintaining parsers. It’s shaped for:
  • Web-data API products reselling structured retrieval to their own developers.
  • Pipelines where parsing, deduplication, and schema management are non-trivial engineering work you’d rather not own.
  • AI products grounding inference on a small number of high-cardinality target shapes.
To trial either surface, get in touch via your existing account contact or email partnerships@soax.com.
What “closed alpha” means here:
  • Not a feature flag on your existing plan. You can’t toggle Headful Browser or Web Data API from the dashboard the way you toggle mobile network on a package. Both run on separate provisioning today.
  • Direct contact with engineering, not just Sales. Closed-alpha customers work with the product team during integration, share workload telemetry that informs the GA scope, and get visibility into the roadmap. The trade-off is that the contract surface is still evolving: endpoint signatures, schema shapes, and rate-limit behavior may change before GA.

​
How it works

You connect to SOAX using standard proxy protocols: HTTP, HTTPS, and SOCKS5. There’s nothing proprietary to install. If your tool or code supports proxy connections, it works with SOAX. Every connection points at the same gateway: 
proxy.soax.com:1337
A connection string has three parts: rules, a package key, and that gateway. 
country-us-session-job42:pk_abc123@proxy.soax.com:1337
  • The rules (country-us-session-job42) describe what you want: where to exit, whether to hold a session, how to handle errors. They’re sent as the proxy username.
  • The package key (pk_abc123) authenticates you. It’s sent as the proxy password.
  • The gateway is what you connect to.
You put the rules straight in the connection string — there’s nothing to configure in the dashboard first. The dashboard’s Quick Connect builder can generate the string for you, or you can write it by hand. You can manage everything from the dashboard or integrate directly using your preferred language. We have working examples for Python, Node.js, Go, and curl.

​
Who SOAX is for

SOAX is built for products with public-web workloads: companies whose product depends on fresh public-web data as a runtime input. Their customers feel it when data is stale or fails. Typical workloads include:
  • RAG-grounded LLM products, AI search, and agents that operate on the public web.
  • Web-data APIs and infrastructure sold to other developers and products.
  • Marketing, SEO, and competitive-intelligence products where continuous crawl is the product surface.
  • Pricing intelligence, ad verification, threat intelligence, and brand protection embedded inside an AI or SaaS product.
  • High-scale e-commerce monitoring and regulatory monitoring.
You’ll get the most out of SOAX if you need:
  • High success rates on difficult targets. Residential and mobile IPs come from real consumer connections, which makes them much harder for anti-bot systems to flag.
  • Granular session control. Rotate on every request, hold a session for a multi-step task, rotate on a timer or request count, or lock to a single node, all configured in the connection string.
  • Scale without infrastructure overhead. You don’t need to build or maintain your own proxy infrastructure. We handle the pool, rotation, and node health.

​
Next steps

Quickstart

Make your first proxy request in under 5 minutes.

Choose a proxy type

Compare proxy types and pick the right one for your use case.