Twitter viewers are everywhere. Almost none of them work for AI agents.
By Steven Van ·
Unif API's curl test of eight viewers found none readable by a script, and its own free viewers allow 20 lookups per 10 minutes with no key.
Unif API tested eight Twitter viewers the way an AI agent would, using curl with no cookies and no JavaScript, and found that none of the viewer pages could be read by a script. Unif API published the results in a post by its Unif SEO team, tested on October 7, 2026 and updated October 10.
What the test found
Each viewer was asked for a public @NASA profile page, or the closest equivalent, with the default user agent. Where a site blocked that, the team retried with a Chrome user agent string. The results:
- Sotwe and Twstalker returned HTTP 403 with a Cloudflare "Just a moment" challenge.
- xcancel.com, a Nitter instance, returned HTTP 451 for every path, RSS included. Nitter itself gave no response.
- twitterviewer.net returned a 5 KB JavaScript shell with no data. Its llms.txt says its pages are not feeds and points agents to an MCP server behind OAuth 2.1 registration.
- TwitterShots returned a form-driven page, and /twitter-viewer/NASA was a 404. Snaplytics returned a landing page that redirects to a form.
- FxTwitter (api.fxtwitter.com) returned JSON, but only for single posts and users. It has no search or trends and prints no rate-limit headers.
- x.com returned a 147 KB JavaScript application.
On Nitter, the post says it stopped working in January 2024 when X removed guest accounts and returned in 2025 running on real accounts. In August 2026 the project and its largest public instances received cease-and-desist letters from X Corp.
Seven failures for agents
The post lists seven recurring problems: no deep-link URL, HTML-only output, data rendered by JavaScript, bot walls, silent rate limits, unstable field names, and no path to a documented, metered API with the same fields.
What an agent-friendly viewer looks like
Unif API's specification puts the request in the URL, for example ?q= with a handle on a profile viewer or a post URL or ID on a tweet viewer. The same URL should return a machine format: ?format=json for programs, or ?format=md or Accept: text/markdown for a model reading text. It should also print its rate limit in headers and share field names with a metered API.
The Twitter viewer series on UnifAPI is built this way. Every page is free to use with no login, account or API key, and is rate-limited to 20 lookups per 10 minutes per visitor.
