A site is offline or hard-blocked. What the agent does next decides whether anyone can trust the answer. ## Without Search — the failure nobody sees The dangerous case isn't an error — it's a **200 with the wrong body**. The site serves its anti-bot challenge page, the tool delivers it as "content", and the agent summarises it as if it were the article (illustrative): ``` fetch("https://forum.example/thread/4471") ← ordinary fetch tool Just a moment... "Checking your browser before accessing forum.example. Please enable JavaScript and cookies to continue." → 200 OK. The agent now "summarises" a checking-your-browser page — and presents it as the source. No one can tell. ``` ## With Levirge Search — failure is a result Search detects challenge and error content and never serves it as a page. If the full browser can't get through either, the failure comes back explicit — naming both attempts. Captured 8 Aug 2026 from Claude Code over MCP, verbatim (a retired host whose TLS certificate no longer validates): ``` fetch("https://deno-was-retired.example.dev/changelog") FAILED: Error: fetch failed for https://deno-was-retired.example.dev/changelog: direct (blocked/error content: {"error": 500, "detail": "{\"error\":\"Internal server error\",\"correlation_id\":\"15a074e1ae81\"}"}); stealth (Error: stealth 502: Page.goto: net::ERR_CERT_AUTHORITY_INVALID …) ``` Both routes tried, both named, and a correlation id ties the attempt to the service's own logs. ## The answer the agent can now give > I couldn't read the source. Both routes failed — direct fetch hit error > content (HTTP 500), and the full browser hit an invalid TLS certificate. > **No summary was produced.** The failure is recorded (correlation id > `15a074e1ae81`); the domain is on the investigation queue. Want me to try > an archived copy, or another source? ## Measured improvement, and where this came from Without Search: a confident summary of a checking-your-browser page, presented as the source — a wrong answer no one can detect. With Search: **zero fabricated answers** — an explicit failure with both routes named, on the record, with a next step. - **Client:** Claude Code over MCP; captured 10:03:53 UTC, 8 Aug 2026, in [the queued-reads run](/search/examples/queued-reads.md) - **Trace:** correlation id `15a074e1ae81` ties the attempt to service logs - **Recorded:** workspace activity + `stealth_failures` queue with failure count — a regressing source gets noticed, never quietly re-failed ## Run it yourself [Try a live read](/search#try) — a page that can't be read is reported with the reason, never summarised from nothing.