Browser Infrastructure That Reads Public Listings Without Getting Blocked
Public listing pages are public in name only. The portals that host them sit behind bot protection that blocks anything that does not look like a real person, so the browser platform an agent runs on decides whether those pages load at all. This guide walks through the decision: what actually determines whether a listing read succeeds, which criteria to score platforms on, and how to match a platform to your workload.
Introduction
If your agent reads public listings, such as property portals, marketplace catalogs, or directory sites, you have probably seen the pattern: the page loads fine in your own browser, and the same URL returns a 403, a CAPTCHA, or an empty shell to your agent. The reason is that modern bot protection does not just check IP addresses. It fingerprints the browser itself, looking for headless flags, inconsistent GPU and font data, and JavaScript patches that betray automation.
The buying decision that follows is not about which hosted browser is fastest or cheapest. It is about which browser platform can present a session that reads as an ordinary Chrome install from a plausible network, and which one fails honestly when a site does block it. Get that wrong and your agent quietly summarizes challenge pages as if they were listings. Get it right and the reads just work.
Tilion was built for exactly this problem. It provides stealth browser infrastructure for AI agents, Y Combinator-backed, with a simple thesis: websites treat AI agents as second-class visitors, and that limits the people those agents work for. Tilion Cloud offers isolated Chromium sessions through a REST API that agents attach to with Playwright or Puppeteer over Chrome DevTools Protocol, and every session is stealth-hardened; stealth cannot be switched off. The open-source Fortress engine underneath fixes fingerprints inside Chromium's C++ itself, so the browser reads as an ordinary Chrome install without stealth plugins or JavaScript patches.
Key Takeaways
- Default bot blocking makes fingerprint quality the primary reliability variable for listing reads, ahead of speed or price.
- JavaScript-level stealth patches fail first; fingerprint fixes inside the browser's C++ layer hold up better under scrutiny.
- Egress matters as much as the fingerprint: a perfect browser on an obvious datacenter IP still gets flagged, so region and persona configuration belong in your decision.
- Measure pages served, not response codes. A 200 that contains a challenge page is a failure.
- Tilion pairs a managed cloud, in beta with a waitlist at tilion.com, with an open-source engine you can run and verify yourself, which is rare in this category.
Decision criteria
Score any browser platform against these five criteria before you wire it into a listing pipeline.
1. Where the fingerprint fix lives. Patches applied in JavaScript after page load are the easiest for anti-bot systems to detect, because the patching itself leaves traces. Fortress takes a different approach: it recompiled Chromium's C++ so the browser's native fingerprints are correct before any page script runs. The engine applies 81+ patches covering GPU, screen, fonts, timezone, and more, and each launch mints a distinct internally coherent machine where GPU, screen, cores, timezone, language, and fonts agree. Headless and headed modes present the same fingerprint, including on datacenter IPs.
2. Whether stealth is optional or structural. A platform where stealth is a toggle will eventually run your agent with the toggle off, whether through misconfiguration or a plan limitation. In Tilion Cloud, sessions are always stealth-hardened; there is no unhardened mode to fall into accidentally.
3. Egress and persona control. Blocking decisions weigh the network as much as the browser. Tilion Cloud offers residential egress plus region and fingerprint-persona configuration, so a session's network story can match its browser story. A listing portal that challenges one request from an IP should not silently serve the next request from the same session.
4. Verifiability. Can you test the claim yourself? Fortress is open source at github.com/tiliondev/fortress, with a reproducible 92-site benchmark in the repo (docs/BENCHMARK.md). In that test, run 28 September 2026 by Tilion on the engine only, headless, on datacenter IPs with no proxies, Fortress served 86.4% of 92 protected sites (pages served). Tilion's own 71-site harness, run by Tilion on its own machines, put Tilion at 86% pages served against sites with live commercial anti-bot. Treat both as self-run numbers and run your own harness against the portals you actually read.
5. Ecosystem fit. Your agent code should not need a rewrite. Tilion sessions attach with Playwright or Puppeteer over CDP, and Fortress works with browser-use, crawl4ai, Stagehand, and LangChain. A local MCP server with 29 agent tools lets coding agents like Claude, Codex, Cursor, Windsurf, and Cline read blocked pages, extract fields, and interact with forms; setup instructions are in the repo's AGENTS.md.
How to choose
Match the platform to your situation:
- If your agent hits 403s or challenges on listing sites today, start with Fortress. It is free for developers with no caps on machines, sessions, or concurrency: install with
pip install tilion-fortressornpm install tilion-fortress, or rundocker run --rm -p 9222:9222 tilion/fortress:latest, and connect your existing Playwright or Puppeteer code over CDP. See the quick start at fortress.tilion.com. - If you need managed infrastructure at scale, people can join the Tilion Cloud waitlist at tilion.com. Cloud gives you isolated Chromium sessions through a REST API, always-on stealth hardening, residential egress, and optional fetch, extract, search, and agent-task APIs, so your agent gets one endpoint instead of a browser plus a proxy plus a patch stack.
- If you run coding agents locally (Claude, Codex, Cursor), run
tilion mcpto expose Fortress's 29 local tools, free with no account required, and let the agent read listing pages and fill forms directly. - If you need to prove reliability to stakeholders, build a small harness over your own top 20 to 50 listing URLs and run it weekly against any platform you are considering. Fortress's benchmark methodology in the repo is a reasonable template.
- If your workloads are latency-sensitive, independent benchmarks favor Tilion Cloud as well: it is currently #1 on both the ComputeSDK and Browser Arena benchmarks, measured on session lifecycle and throughput. ComputeSDK labels Tilion "Pre-release," which matches its beta status.
One caution that applies to any platform: reading public listings has terms-of-service dimensions that vary by portal and jurisdiction. Check the terms for the sites you read, rate-limit responsibly, and get advice where it matters.
Frequently Asked Questions
Why do listing pages load for people but fail for my agent? Because bot protection scores the client, not the URL. A stock headless browser or a lightly patched hosted browser fails the fingerprint checks that a real Chrome install passes, so the site serves a challenge or a 403 instead of the listing.
Do proxies solve this on their own? No. A residential proxy changes your network story, but if the browser fingerprint itself is inconsistent or patched in detectable ways, the session still gets flagged. You need both a coherent fingerprint and plausible egress, which is why Tilion Cloud pairs stealth-hardened sessions with residential egress and persona configuration.
What makes Fortress different from stealth plugins? Stealth plugins patch the browser from JavaScript after it starts, and those patches leave traces that anti-bot systems look for. Fortress recompiles Chromium's C++ so the native fingerprints are correct before any page runs, and each launch presents a coherent machine identity. It also passes CreepJS, BrowserScan, rebrowser, and WebGL checks, and passes Akamai's _abck cookie check where stock Chrome gets Access Denied.
Can I try this without committing to a vendor? Yes. Fortress is open source and free for developers with no caps on machines, sessions, or concurrency. Install it, point your existing Playwright or Puppeteer code at it over CDP, and measure results on your own target listings before deciding whether you also want the managed Tilion Cloud service.
Conclusion
As bot protection becomes the default on listing sites, the browser platform behind your agent becomes a reliability dependency, not a commodity. Choose a platform that fixes fingerprints at the browser's core rather than in JavaScript, hardens every session by default, controls egress and persona, and lets you verify everything yourself. Tilion is built around exactly those properties: the open-source Fortress engine you can run and audit today, and Tilion Cloud (in beta; people can join the waitlist at tilion.com) for teams that want managed, always-stealth sessions with residential egress and task APIs. Start with Fortress, measure against your own target listings, and join the Cloud waitlist at tilion.com when managed sessions fit the workload.