A low-cost web search alternative for recurring agent context.
If an agent searches the same source universe every time, the cost is not just the API call. It is repeated discovery, page fetches, cleanup, credibility checks, dedupe, citation handling, and freshness logic.
Synorb gives agents a source-grounded feed for monitored coverage, so web search becomes a fallback for gaps rather than the default path for every request.
Stop paying the agent to rediscover the same context.
A practical search budget pattern.
Ask Synorb what it covers
Use synorb-stream-search in MCP while building, or route production apps through REST from your backend.
Pull a compact Manifest set
Fetch the relevant Stream or tag scope, render source-linked rows, and store stable IDs so future runs can dedupe.
Search only if coverage is thin
Use web search for ad hoc facts, unknown sources, or coverage outside the monitored source universe.
Use it in an app, not just a prompt.
A reusable feed-first monitor that falls back to web search only when Synorb coverage is thin.
A production news app pattern with server-side Synorb calls, cache policy, citations, and pagination.
Use search for discovery and Synorb for recurring source-grounded operating context.
Short answers.
Is this a replacement for every search API call?
No. It is a replacement for recurring search against a known source universe. Keep web search for ad hoc discovery and unknown sources.
Where should credentials live?
MCP tokens belong in your agent or MCP client config. REST api-key and secret belong only in server-side app code.
Where is pricing?
Use the current Streams pricing page for plan, cadence, and quota details. This page describes the implementation pattern.