Which scraping APIs handle PerimeterX (HUMAN) in 2026?
Two scraping APIs returned every request on the nine PerimeterX (HUMAN) sites in the October 30, 2026 Web Data Frontier Benchmark: Scrape.do and Firecrawl, 45 of 45 each. String and Context.dev were next at 97.8%, 44 of 45, then Scrapfly at 93.3%. The other twelve APIs scored between 91.1% and 6.7%. HUMAN Security owns the product now; it merged with PerimeterX in July 2022, and the sites still load scripts and cookies under the PerimeterX name.
On October 20, 2026 we sent one request to each of the same nine pages three ways. Python requests got the real page on 1 of 9. curl_cffi with a Chrome fingerprint got 3 of 9. String's fetch API got 8 of 9 on the first try and the ninth on a retry.
How the scraping APIs did on PerimeterX
Each site was requested five times per provider in the October 30, 2026 run, 45 requests per provider in total. A request counted only when the body contained text from the real page.
| Provider | PerimeterX success rate | Sites with 5 of 5 | Sites never returned | Overall rate, 100 sites |
|---|---|---|---|---|
| Scrape.do | 100% | 9 of 9 | none | 94.0% |
| Firecrawl | 100% | 9 of 9 | none | 81.2% |
| String | 97.8% | 8 of 9 | none | 98.6% |
| Context.dev | 97.8% | 8 of 9 | none | 93.0% |
| Scrapfly | 93.3% | 8 of 9 | none | 86.8% |
| Zyte | 91.1% | 7 of 9 | none | 79.6% |
| Oxylabs | 91.1% | 8 of 9 | none | 67.4% |
| ScrapingBee | 88.9% | 8 of 9 | skyscanner.net | 85.2% |
| Apify | 86.7% | 7 of 9 | skyscanner.net | 79.4% |
| Bright Data | 86.7% | 5 of 9 | none | 75.4% |
| Decodo | 86.7% | 7 of 9 | skyscanner.net | 71.2% |
| ScraperAPI | 82.2% | 6 of 9 | goodrx.com | 76.4% |
| Nimble | 82.2% | 6 of 9 | skyscanner.net | 68.0% |
| Browserbase | 73.3% | 3 of 9 | skyscanner.net | 43.0% |
| ZenRows | 73.3% | 5 of 9 | bloomberg.com, skyscanner.net | 41.8% |
| ScrapingAnt | 53.3% | 3 of 9 | goodrx.com, skyscanner.net | 40.0% |
| Scrapingdog | 6.7% | 0 of 9 | 7 of the 9 sites | 27.6% |
The nine sites are walmart.com, zillow.com, target.com, ashleyfurniture.com, carters.com, ralphlauren.com, bloomberg.com, goodrx.com and skyscanner.net. Eight of them are retail, real estate, finance or health pages. One is a travel search page.
The harness changed how it calls three providers for this run: ScrapingBee, which it now scores on its final status, Decodo and Browserbase. A move for those three since the September 16 run can come from the harness, not the product. ZenRows' own API closed the connection without a response on the last 43 targets of the suite, skyscanner.net among them, and those attempts count as failures here. The per-site grid is on the benchmark page and in the public harness.
PerimeterX was not the hardest wall in the run
In the October 30, 2026 run, the 17 APIs averaged 81.8% on the PerimeterX sites. Across all 100 sites they averaged 71.1%.
Fifteen of the 17 scored higher on PerimeterX than on the benchmark as a whole. Oxylabs rose 24 points, from 67.4% to 91.1%. Browserbase rose 30 points. String was one of the two that scored lower: 97.8% on PerimeterX against 98.6% overall. No anti-bot group in the run had a higher field average. The same 17 APIs averaged 70.8% on Cloudflare sites, 64.8% on Akamai sites and 68.7% on DataDome sites.
One site broke the pattern. In that run, skyscanner.net shut out 8 of the 17 APIs on all five attempts, ZenRows inside its API outage. Only Scrape.do, Context.dev, Scrapfly, Firecrawl and Oxylabs returned it every time. String returned it on 4 of 5; its fifth attempt hit the 90-second timeout. Leave skyscanner.net out, and 13 of the 17 APIs returned every one of the other eight sites at least once.
Nine sites is a small sample. HUMAN is configured per customer, so a pass on walmart.com says little about the next HUMAN site you meet. Run your own target list before you pick.
Want to check one of your own HUMAN-protected URLs now? curl -s https://request.usestring.ai/v1/fetch -H "Authorization: Bearer $STRING_API_KEY" -H "Content-Type: application/json" -d '{"url":"https://www.zillow.com/new-york-ny/"}' returns the page, and the first 20,000 standard fetches are free.
How to tell a site uses PerimeterX
Look for HUMAN's own cookie and host names. The status code alone can mislead. HUMAN's documentation lists these:
_px3is the risk cookie, an encrypted payload that carries a score from 0 to 100._pxvidand_pxhdare visitor IDs._px2is the older version of the risk cookie (HUMAN cookie list, HUMAN Enforcer docs).- Sensor data goes to
collector-<appid>.perimeterx.net. The challenge loads fromcaptcha.px-cdn.netorcaptcha.px-cloud.net. - The challenge is a "Press & Hold" button in an element with the id
px-captcha. HUMAN calls it the HUMAN Challenge. - HUMAN's Enforcer returns
403for a challenge or a hard block and429for a rate-limit block. Some sites answer with a200instead.
Our October 20 probe saw all four. Six of the nine pages answered plain Python requests with a HUMAN challenge page. Four came with a 403 and one with a 307 redirect. walmart.com sent its challenge with a 200: a 15 KB page that held the px-captcha element and no product. carters.com returned a 403 with no HUMAN markers. skyscanner.net returned a 200 and 708 bytes, an empty shell with no HUMAN markers at all.
A short check in Python catches the common shapes:
import re
import requests
HUMAN = re.compile(r"px-captcha|Press & Hold|Press & Hold|captcha\.px-c(?:dn|loud)\.net", re.I)
def looks_blocked(resp: requests.Response, expected_text: str) -> bool:
body = resp.text or ""
if resp.status_code in (403, 429):
return True
if HUMAN.search(body):
return True
# A 200 can still be a block: check for text that only the real page has.
return expected_text.lower() not in body.lower()
The last line matters most. On skyscanner.net the block carried no marker, so only the missing content gave it away. The same rule applies to blocks that come back as HTTP 200 on any wall.
What PerimeterX checks
HUMAN scores a request in two places. A JavaScript sensor runs in the page and collects browser and device signals. The sensor sends those signals to HUMAN, and HUMAN writes the result into the _px3 cookie with a risk score. A server-side Enforcer, installed at the CDN, load balancer or origin, reads that cookie and blocks or passes the request. When the cookie is missing or invalid, the Enforcer asks HUMAN's Risk API for a score instead (HUMAN Enforcer docs).
That design explains the failures people report. A client that never runs the sensor never earns a valid _px3. The Enforcer then scores it on what it can see: the TLS and HTTP/2 handshake, the headers, and the IP. A Python or Node client fails that first look on most HUMAN sites.
The cookie is also short. HUMAN lists the _px* cookies with a 5.5-minute expiry. A session that worked a few minutes ago can fail on its next request when it has not refreshed the cookie through the sensor.
Doing it yourself
A TLS-impersonating client is the cheapest first step. curl_cffi sends a Chrome handshake and Chrome headers. In our probe it moved the count from 1 of 9 to 3 of 9: zillow.com and carters.com opened, the other six did not. It is fast, and it stops working on any page that wants the sensor to run.
A real browser runs the sensor. Puppeteer, Playwright and Selenium do that, but HUMAN looks for automation traces, and a stock headless browser often gets the Press & Hold. A Puppeteer user put it plainly on r/webscraping in January 2026: "I tried many things but unable to bypass it" (thread). Stealth builds such as Camoufox, nodriver or Patchright close some of those gaps. Each HUMAN sensor update can open them again.
Residential proxies help with one signal. HUMAN scores IP reputation, so a datacenter IP starts behind. A clean IP with a library fingerprint still fails, and a _px3 cookie that moves to a new IP makes the session look more like automation. Keep one IP per session.
The problem is old. In October 2021 a user on r/webscraping who tried Walmart with Python requests and Selenium wrote: "They immediately block me before I am able to visit a single page" (thread). Five years later, walmart.com still served our probe a challenge on its first request.
For the general playbook across walls, see how to scrape a website without getting blocked. For the Press & Hold and other challenge types, see how to get past a CAPTCHA when scraping.
How String gets through PerimeterX
String is a web scraping API for developers and AI agents that returns protected pages in one request and bills only for successful requests. On HUMAN-protected pages, that means:
- String returned 44 of 45 PerimeterX requests in a public test. That was the October 30, 2026 run of the open benchmark, nine HUMAN sites at five attempts each (benchmark). Scrape.do and Firecrawl returned all 45.
- String returned skyscanner.net on 4 of 5 attempts. Eight of the 17 APIs tested never returned that page once.
- One request, no sensor work on your side. A
POSTto/v1/fetchwith a URL returns the page; String picks a plain request, a premium residential proxy or a real browser per page (fetch docs). - The site's own status comes back in a header. The
x-status-coderesponse header carries what the target returned, so you can see a HUMAN403when one happens. - A blocked request costs nothing. String bills only when content comes back (pricing).
- Agents get it as a tool. The hosted MCP server gives Claude, Cursor, ChatGPT and other MCP clients
web_access_fetch.
Here is the same request our probe sent, in Python:
import os
import requests
resp = requests.post(
"https://request.usestring.ai/v1/fetch",
headers={"Authorization": f"Bearer {os.environ['STRING_API_KEY']}"},
json={"url": "https://www.goodrx.com/advil", "format": "markdown"},
timeout=150,
)
print(resp.headers.get("x-status-code"), resp.text[:500])
goodrx.com answered plain requests and curl_cffi with a Press & Hold page in our probe. Through String it returned the real Advil page.
Where String fits
- For: teams that need product, listing or price pages from HUMAN-protected retail, real estate and travel sites, and would rather not run browsers and sensor handling themselves.
- Not for: a site that sells the same data through an official API or feed, or pages behind a login you do not own.
- Price: as of October 2026, Starter is $19 a month and Growth is $99 a month, plus usage. A standard fetch is $0.25 per 1,000 on Starter and $0.16 on Growth. A fetch on the premium residential proxy, used only when a page needs it, is $2.40 and $0.90 (pricing). The first 20,000 standard fetches are free.
- Integrations: a REST API for any language, an OpenAPI spec, an MCP server, and String Actors in the Apify Store.
- Limits: 15 requests a second on Starter, up to 90+ on Volume, and up to 10,000 concurrent fetches (pricing).
For every provider across all 100 sites, see the best web scraping APIs ranking. For the other walls, see DataDome, Akamai Bot Manager and Cloudflare. Start with the HUMAN page your scraper fails on today, and run it through the fetch call above with a free key.
FAQ
Which scraping APIs handle PerimeterX / HUMAN challenges?
In the October 30, 2026 run of the open Web Data Frontier Benchmark, Scrape.do and Firecrawl returned all 45 requests to nine PerimeterX sites. String and Context.dev scored 97.8%, and Scrapfly 93.3%. The lowest of the 17 APIs tested scored 6.7%. ZenRows' own API failed on the last 43 targets of that run, and its skyscanner.net attempts fell inside that outage.
Is PerimeterX the same as HUMAN Security?
Yes. HUMAN Security and PerimeterX merged in July 2022 under the HUMAN name. The bot product is now HUMAN Bot Defender. Protected sites still set _px cookies and call perimeterx.net hosts, so most scrapers still call it PerimeterX.
How do I know a site uses PerimeterX?
Look for _px3, _pxvid or _pxhd cookies, requests to collector-<appid>.perimeterx.net, or a page with a px-captcha element and a "Press & Hold" button. A 403 or 429 from the site is common. Some HUMAN sites answer with a 200 and an empty page, so check for content you expect.
What is the PerimeterX "Press & Hold" challenge?
It is the HUMAN Challenge: a button the visitor presses and holds while HUMAN checks the browser. A site shows it to a visitor HUMAN does not trust yet, in place of the page. In our October 20 probe, six of nine HUMAN sites answered plain Python requests with a HUMAN challenge page.
Why do I get a 403 from a PerimeterX site?
HUMAN's Enforcer returns a 403 when it shows a challenge or a hard block. Python requests triggers it on most HUMAN sites, because it has a TLS and HTTP/2 handshake that no browser sends, and it cannot run HUMAN's JavaScript sensor. So it never gets a valid _px3 cookie. In our own probe of October 20, 2026 (one request to each of the nine HUMAN sites in the benchmark), requests with default headers got the real page on 1 of 9. A Chrome-impersonating client (curl_cffi) got 3 of 9.
Does Puppeteer or Selenium get past PerimeterX?
Sometimes. A real browser runs the sensor, which a plain HTTP client cannot do. HUMAN also looks for automation traces, and a stock headless browser often still gets the Press & Hold. Stealth builds such as Camoufox or Patchright pass more often, and each sensor update can break them again.
What is the _px3 cookie?
_px3 is HUMAN's risk cookie. The sensor in the page earns it, and it carries an encrypted risk score from 0 to 100 that the server-side Enforcer reads to pass or block the request. HUMAN's documentation lists a 5.5-minute expiry for the _px cookies, so a session has to keep refreshing it.
Do residential proxies get past PerimeterX?
Not on their own. IP reputation is one signal in HUMAN's score, and a residential IP with a Python handshake still fails. Proxies help when the client also passes the fingerprint and sensor checks. Keep one IP per session, because a _px3 cookie moved to a new IP looks like automation.
Sources
- Web Data Frontier Benchmark, October 30, 2026 run: usestring.ai/benchmark, the October write-up and the raw results on GitHub
- HUMAN, Use of cookies and web storage: docs.humansecurity.com
- HUMAN, About Enforcers (risk cookie, hostnames, block responses): docs.humansecurity.com
- HUMAN, HUMAN Challenge: docs.humansecurity.com
- HUMAN, merger announcement, July 27, 2022: humansecurity.com
- r/webscraping, "Having hardtime bypassing perimeterx bot detection", January 2026: reddit.com
- r/webscraping, "Does anyone know how to bypass PerimeterX?", October 2021: reddit.com
- curl_cffi: github.com/lexiforest/curl_cffi
- String pricing: usestring.ai/pricing; fetch API docs: portal.usestring.ai/docs/fetch/overview