Benchmark: search products on Zalando with an AI agent
Neither side passed on Zalando. Wield's recipe passed 0 of 9 runs. The tab was redirected to en.zalando.de, and the run failed with a tab error. A Claude browser agent also passed 0 of 9 runs, with a median of 294.9 s and $0.12 per run, and the benchmark flagged all 9 as blocked. These results are as of 7 November 2026.
Zalando Search fashion products with optional size and price filters
Read-only, no loginFailed the last daily check
Parameters (6)
| Metric | Wield recipe | Browser Use + Claude Sonnet 5.5 |
|---|---|---|
| Success | 0% | 0% |
| Median time | 991 ms | 295 s |
| Cost per run | $0 | $0.122 |
9 runs each, 7 November 2026. How we measure
The task
Each side ran the same three searches. A run passes when it returns at least five products with a name and a price.
| Query | Parameters |
|---|---|
| q1 | query = sneakers, sizes = ['42'], max_price = 80 |
| q2 | query = regenjacke herren, max_price = 150 |
| q3 | query = winterstiefel damen, sizes = ['39'] |
Results
| Wield recipe | Browser agent | |
|---|---|---|
| Runs passing the check | 0 of 9 | 0 of 9 |
| Median time per run | 991 ms | 294.9 s (294,897 ms) |
| Model cost per run | $0 | $0.12 |
| Requests per run (median) | 0 | 60 (to the site: 7) |
| Blocked by the site | 0 runs | 9 of 9 runs |
The browser agent took a median of 11 steps per run, with 14,667 input tokens and 1,980 output tokens. The site returned HTTP 403 to the agent on its homepage, on a category page, and on tracking and manifest requests.
Why the results differ
The agent's failure comes from Zalando's bot protection. Akamai is the vendor named for zalando.de in our notes. Its 403 responses blocked the browser agent's page loads and tracking calls.
Wield's failure came from its own side. The recipe's origin did not match the redirected page, so the tab error ended the run. This is a Wield result, not a block by Zalando. Our recipe notes say the recipe passed its in-page checks.
Caveats
- Wield failed outright here. This is one of the tasks where Wield scored 0 of 9. We report it as measured.
- HTML fallback not counted. A second recipe, zalando.de/search-products-html, also scored 0 of 9 with the same redirect error. It reuses the browser agent runs above, so we count those runs once.
- Small sample. The benchmark is still running and is paced at about 30 site requests per hour.
- Keep it human-paced. Akamai scores automated traffic. In one test run, an automated test browser was tagged as an aggressive crawler. Wield runs one search at a time from the user's browser.
Terms of Zalando
Zalando's terms forbid automated extraction of content. The recipe makes one search at a time that the user starts, from the user's browser, with 2 requests. Buying stays on zalando.de. Check the site's terms before you use any automation.
FAQ
Does Zalando block browser agents?
In our runs, yes. The browser agent was flagged as blocked in all 9 runs, and the site returned 403 responses throughout. Wield also failed on this task, so this page does not show a Wield win.
How fast is the Wield recipe for search products on Zalando?
The median run took 991 ms, and every run failed on the tab redirect. Speed does not count for a failed run, so the number is shown for transparency only.
Can I rerun this benchmark?
The method and per-task rows are on the benchmark page. The raw logs hold destinations, timing, tokens and check results, not page contents.