Benchmark: search rentals on ImmoScout24 with an AI agent
On ImmoScout24, neither side passed the rental search in this benchmark. Wield's recipe passed 0 of 2 runs. Both stopped at a bot check (AWS WAF) that the site showed instead of search results. The browser agent (Browser Use driving Claude Sonnet 5.5) passed 0 of 9 runs, and the site blocked it in all nine. We report these results as measured.
ImmoScout24 Search rental flats or houses in a German city with rent, rooms and size filters
Read-only, no loginRuns in your browser only
Parameters (10)
| Metric | Wield recipe | Browser Use + Claude Sonnet 5.5 |
|---|---|---|
| Success | 0% | 0% |
| Median time | 9.6 s | 103 s |
| Cost per run | $0 | $0.024 |
9 runs each, 7 November 2026. How we measure
The task
Each side ran the same three rental searches.
| Query | Parameters |
|---|---|
| q1 | city = Leipzig, max_rent = 800, min_rooms = 2 |
| q2 | city = Köln, max_rent = 1200, min_rooms = 2 |
| q3 | city = Hamburg, max_rent = 1000, min_area_m2 = 40 |
Pass check: at least five listings, each with a title and a rent.
Results (7 November 2026)
| Wield recipe | Browser agent | |
|---|---|---|
| Runs passing the check | 0 of 2 | 0 of 9 |
| Median time per run | 9.6 s (9,606 ms) | 102.9 s (102,930 ms) |
| Model cost per run | $0 | $0.02 |
| Requests per run (median) | 4 | 21 (to the site: 1) |
| Blocked by the site | 0 runs | 9 of 9 runs |
Why the results differ
Both Wield runs stopped at the same bot check. The site answered with an AWS WAF challenge (HTTP 401) instead of data. Wield reports this as site_challenge and does not try to solve it. The recipe sent four requests per run, all to the site, before the check appeared.
The browser agent met the same protection. The log records nine HTTP 401 responses from www.immobilienscout24.de. A median run took 2 steps, 3,309 input tokens and 401 output tokens, and then the protection stopped it.
The benchmark does not show this recipe returning listings on ImmoScout24. According to our recipe status notes, the recipe has been verified only in a Chrome session that a person drove.
Caveats
- Small sample. Two Wield runs and nine browser-agent runs.
- Preliminary. The benchmark was still running on 7 November 2026.
- Paced. Runs are paced at about 30 site requests per hour, so counts are low on some sides.
- Check stops both sides. When the WAF challenge appears, the user loads the site normally in their own browser. Wield does not try to get past it.
Terms of ImmoScout24
ImmoScout24's terms forbid automated querying and data collection. The recipe runs one search page at a time from the user's own browser, with two requests. It never tries to solve the WAF challenge, and it does not return listing contact data. Check the site's terms before any automated use.
FAQ
Does ImmoScout24 block browser agents?
In these runs, yes. The browser agent received HTTP 401 responses and was blocked in all nine runs. Wield's two runs also stopped at the same AWS WAF bot check.
How fast is the Wield recipe for search rentals on ImmoScout24?
The median run took 9.6 s, between 6.4 s and 12.8 s. Neither run returned listings, so these timings do not measure a successful search.
Can I rerun this benchmark?
The method, the task file and the raw logs are described on the benchmark page. The logs record destinations, timing, tokens and checks. They hold no page contents.