WAF COMPATIBILITY
Coverage across every major WAF.
Production-tested Cloudflare bypass, Akamai bypass, DataDome bypass, and 7+ more WAF types with low-latency repeat access.
Compatibility Matrix
| WAF / Protection | Coverage | API Access | Notes |
|---|---|---|---|
| Cloudflare L1-L2 | Supported | N/A | Production-tested |
| Cloudflare L3 (Turnstile) | Supported | N/A | Production-tested |
| Akamai Bot Manager | Supported | Untested | Production-tested |
| DataDome | Supported | Untested | Production-tested |
| PerimeterX / HUMAN | Supported | Limited | Compatibility varies by endpoint |
| Kasada | Supported | Untested | Production-tested |
| Shape (F5) | Supported | N/A | Production-tested |
| hCaptcha | Supported | N/A | Production-tested |
| reCAPTCHA v2 | Supported | N/A | Production-tested |
| X (Twitter) Auth Gate | Supported | Supported | Production-tested |
Performance Profile
The API automatically selects the optimal access method — balancing latency against WAF complexity for each target.
Cached Access
- Low-latency repeat access
- Best fit for already-established sessions
- Typical response time around 60ms
Full Access
- Higher latency, broader site coverage
- Used automatically when stricter protections are detected
- Typical response time around 3 seconds
Cached access responds in ~60ms. Full access adds latency but handles stricter protections automatically. The
auto mode selects the best method transparently.How It Works
1st request: Full access — clears protections, caches session
cost: 10 credits · 3-10 sec
2nd+ request: Cached access — reuses session
cost: 1 credit · 45-250 ms
cost: 10 credits · 3-10 sec
2nd+ request: Cached access — reuses session
cost: 1 credit · 45-250 ms