Benchmark: search cars on mobile.de with an AI agent
On mobile.de, Wield's recipe passed 5 of 9 car searches, with a median of 2.1 seconds and no model cost. Four runs failed, and the causes are below. A browser agent (Browser Use driving Claude Sonnet 5.5) passed 0 of 9, and mobile.de blocked it in all nine runs. Both sides ran three make and price queries on 7 November 2026.
mobile.de Search used cars on mobile.de by make, price, year and mileage
Read-only, no loginRuns in your browser only
Parameters (7)
| Metric | Wield recipe | Browser Use + Claude Sonnet 5.5 |
|---|---|---|
| Success | 56% | 0% |
| Median time | 2.1 s | 14 s |
| Cost per run | $0 | $0.020 |
9 runs each, 7 November 2026. How we measure
The task
Each side ran the same three searches. Each search names a make and price or year limits.
| Query | Parameters |
|---|---|
| q1 | make = Volkswagen, price_from = 5000, price_to = 15000, year_from = 2018, max_km = 100000, sort = price_asc |
| q2 | make = BMW, price_to = 20000 |
| q3 | make = Audi, price_to = 25000, year_from = 2019 |
Pass check: at least five cars, each with a title and a price.
Results (7 November 2026)
| Wield recipe | Browser agent | |
|---|---|---|
| Runs passing the check | 5 of 9 | 0 of 9 |
| Median time per run | 2.1 s (2,109 ms) | 13.5 s (13,527 ms) |
| Model cost per run | $0 | $0.02 |
| Requests per run (median) | 1 | 5 (to the site: 1) |
| Blocked by the site | 0 runs | 9 of 9 runs |
Wield's fastest run took 665 ms and its slowest took 4.7 s.
Why the results differ
Wield's four failed runs had two causes. Some runs failed because the tab was redirected from suchen.mobile.de to www.mobile.de, and the recipe's origin setting did not yet cover that redirect. One run failed with no error text. Our recipe notes list a fix, a start_path change. This benchmark does not show that fix working.
The recipe runs from a mobile.de tab in your own browser, at human pace. When it works, it returns the listings in one request per run, with no model in the loop.
The browser agent ran in a fresh headless Chromium, the setup that cloud browser agents usually use. mobile.de's bot protection refused its requests. The log records nine HTTP 403 responses from www.mobile.de. A median run took 2 steps, 3,291 input tokens and 373 output tokens, and the agent never reached a list of cars.
Caveats
- Wield passed 5 of 9. The misses are real and counted in the results above.
- Small sample. Nine runs per side, on three queries.
- 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.
Terms of mobile.de
mobile.de's terms prohibit automated data extraction. The recipe runs one search page at a time that you start, from your own browser, with one request. Contacting sellers stays on mobile.de. Check the site's terms before any automated use.
FAQ
Does mobile.de block browser agents?
In these runs, yes. The browser agent received HTTP 403 responses and was blocked in all nine runs.
How fast is the Wield recipe for search cars on mobile.de?
The median run took 2.1 s across all nine runs, and five of them passed the check. The fastest run took 665 ms.
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.