AI-Driven Access with Proxy Simplicity
%20(1).png)
For data teams, proxies are the backbone of many scraping operations, but modern sites are pushing their limits. JavaScript-heavy pages, dynamic content, and evolving site architectures make traditional proxy networks unpredictable and inefficient.
Unlocker Proxy bridges this gap: a simple proxy endpoint backed by Nimble’s advanced unlocking stack.
Why We Built It
We saw a clear need from our Proxy API customers:
- They wanted higher success rates on complex, dynamic sites.
- They didn’t want to rewrite integrations or run heavy browser setups.
- They needed fine-grained control - country, locale, parsing, rendering - all through a familiar proxy interface.
Unlocker Proxy was built to meet these needs, combining proxy ease-of-use with the full power of Nimble’s Browserless Drivers and AI infrastructure.
How to Use It
Here’s how simple it is to upgrade:
import requests, base64
auth = base64.b64encode(b"user@example.com:your_password").decode()
res = requests.get(
"https://www.ipinfo.com",
proxies={"http": "http://unlocker.webit.live:8888"},
headers={
"Authorization": f"Basic {auth}",
"x-nimble-country": "US",
"x-nimble-parse": "true",
"x-nimble-render": "false",
"x-nimble-format": "json",
"x-nimble-locale": "en-US",
"x-nimble-no-html": "true",
"x-nimble-session-id": "my-session-123"
}
)
print(res.json())
See full header options in the docs
When to Use It
Unlocker Proxy shines when you:
- Want to upgrade proxy workflows without rewriting code
- Need reliable access to dynamic, JavaScript-driven sites
- Want to eliminate or avoid browser infrastructure and save on operational costs
Best Practices
- Use session IDs for persistent sessions when scraping multi-step flows
- Turn rendering off if you only need static data for speed and cost savings
- Leverage locale and parsing controls to fine-tune requests for your use case
Access It Instantly, No Setup Required
Unlocker Proxy is available to all Nimble customers. Just switch your proxy endpoint and start scaling smarter. No new integration, no extra complexity, just better results.
FAQ
Answers to frequently asked questions