TL;DR: If you need infinite scroll pagination through a scenario, use the standard premium or datacenter proxies: stealth_proxy is incompatible with infinite_scroll. Do not combine mode=auto with explicit tier parameters like premium_proxy or stealth_proxy; the API rejects the combination with a 400. Either let the API auto-select the tier or name one tier explicitly, not both.

```text
ScrapingBee mode=auto plus an explicit tier param is a 400
```

## Fix
1. If you need infinite scroll pagination through a scenario, use the standard premium or datacenter proxies: stealth_proxy is incompatible with infinite_scroll.
   Expected: the request routes instead of erroring.

## Details
Do not combine mode=auto with explicit tier parameters like premium_proxy or stealth_proxy; the API rejects the combination with a 400. Either let the API auto-select the tier or name one tier explicitly, not both. Read a failed request's error body for the parameter name; most 400s are one of these conflicts.

## When to use
You hit exactly this: ScrapingBee mode=auto plus an explicit tier param is a 400.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
the tool named in the title.

## Edge cases
- Also know that passing wait_for turns JavaScript rendering on even if you did not ask for it, which changes the cost and behavior of the request.