Scripts or screenshots: which way should an agent pull data from a website?
Plain and in-browser scripts both got 60 of 60 books with full titles, screen reading kept only 10 of 20 full titles; the token figures could not be measured.
Verdict
Partly reproduced41
Access needed
L0 Public web onlyRun 29 Oct 2026
Score and verdict differ. Every claim we could test held up, so the score is 10, but the token numbers were not measurable, which caps the verdict at Partly.
4
claims scored
1 not tested
4 of 4
held up in full
1
sites and APIs touched
about 1 minute
run time
Claim by claim
Plain script extracts the data with no model workcoreHeld up
60 of 60 books in 1.8 seconds.
Script inside the browser reads the page accuratelycoreHeld up
Same 60 records, identical.
Scripts keep full titles that screen reading shortenscoreHeld up
Screen reading: full title for 10 of 20; scripts 20 of 20.
Screen reading costs about 4x the tokens (213K vs 51K)coreNot tested
Token meter not visible to us; not measured.
Screen reading gets price, rating and stock rightHeld up
20 of 20 on page 1.
Open a claim to see what we checked.
- Access it needs
- L0 Public web only
- Run on
- 29 Oct 2026, 08:17 to 08:18 (UTC+8)
- Run by
- Grok Bot
- Check again by
- 28 Nov 2026
What was claimed
'I asked Grok Bot to extract data from the same website three ways ... Computer use: 213K tokens ... Browser plus script: 51K tokens ... Plain script: no model tokens during execution ... The scripts also preserved full titles that computer use shortened.'
@Michael_Fenech_ on X. Original post
What we found
Mostly held up. Both scripts got all 60 books with full titles, while reading the screen gave the full title for only 10 of 20 books on page 1 because the page cuts long titles with '...'. Prices, ratings and stock were read correctly from the screenshots. We could not check the token numbers (213K vs 51K), because Grok Bot's token count is not visible to us; the screenshots were about 270 times larger than the script's output.
How we checked it
Both scripts' output, the comparison and the screenshots saved under runs/2026-10-29/web-extraction-script-vs-screenshots/. Answer key written before the run.
What the agent did
- Plain script: 60 of 60 books, all 4 fields, 1.8 seconds
- Script inside headless Chrome: the same 60 records, identical
- The page itself cuts 34 of 60 titles with '...'
- Reading page 1 from screenshots: full title for 10 of 20 books; price, rating and stock 20 of 20
- Size proxy: 9 screenshots (2.5 MB) vs 9,330 characters of JSON from the script
Sites and APIs touched: books.toscrape.com.
Where it went wrong
- Token counts were not measurable, so the 213K vs 51K figures are untested.
- We used a different practice site than the post (it did not name one).
- Reading the screen silently drops the end of long titles.
Try it yourself
Extract every book (title, price, rating, availability) from the first 3 listing pages of the practice site books.toscrape.com three ways: (1) by looking at screenshots of the page, (2) by running a script inside a real browser, (3) with a plain script and no browser. Compare completeness, accuracy and how much the model had to read.
Lowest-access way to try it
L0 on a public site. Ask the agent to write a script that reads the page's HTML (or runs inside the browser) and to show the record count, instead of reading screenshots; spot-check a few long titles.
Run details
How to cite
TriedAgents, "Scripts or screenshots: which way should an agent pull data from a website?", partly reproduced, checked 2026-10-29, https://triedagents.com/cases/web-extraction-script-vs-screenshots/
Get one re-run case every weekday
One agent use case we actually re-ran, every weekday. Free.
We only store your email address. Every issue has a one-click unsubscribe link. Privacy