Real examples
Seven situations agents hit every week — grouped by what you're trying to do, with what ordinary tools return and what Search returns instead.
Reach sources other tools can't
The blocked portal
Question to cited answer: the host's native fetch refuses the portal outright; Search reads the same page in a full browser — 803 live listings — and the agent answers with citations.
Worked example · question → cited answer →The quiet failure
A site is offline or hard-blocked. Ordinary tools serve the challenge page as "content"; Search reports an explicit failure — shown with a real captured error, both routes named.
Captured error · read the example →Control what reaches your context
Schema-first discovery
An unknown source's shape for pennies — select-ready paths for JSON, a heading outline for markdown; the cached follow-up extracts exactly what's needed.
Worked example · captured payloads →The oversized source
The compare endpoint answers with 1.26 MB — select trims it server-side to 28 KB, the fields alone, shape intact.
Read the example →Automate research runs
Queued reads
A captured run: four URLs queued, acknowledged instantly, all resolved in 29 seconds — three read, one genuine failure reported verbatim and retried.
Worked example · captured run →The nightly release digest
A production run from question to posted digest — the summary the team reads, its two selected reads (28 KB of 1.26 MB), and the measured cost.
Worked example · question → posted digest →