Watch
Source Channels
Synorb watches specific source surfaces such as filings, reports, feeds, releases, transcripts, notices, podcasts, and research pages.
Operator intent
Content Feeds For AI.
A content feed for AI is a structured stream of source-grounded updates that an agent can store, route, cite, and act on. It is most useful when the agent needs repeatable coverage, RAG data streams, or an alternative to repeated web scraping for known sources.
Synorb provides content feeds through watched Source Channels and Streams. The unit an agent receives is a Manifest: a source-linked object with Briefs, Signals, Records, stable IDs, provenance, and delivery paths for REST, MCP, webhooks, and S3 archive exports.
Source Channels to Streams to Manifests · REST + MCP + webhooks + S3 archives · Provenance by default
01 / Definition
A feed starts before the prompt.
Search begins after a user asks a question. A content feed starts when a watched source changes. That difference matters for AI systems that monitor companies, markets, policy, research, media, or other current-event surfaces.
Route
Streams
Streams scope coverage by topic, entity, source set, or saved query so an agent can listen to the areas it is responsible for.
Use
Manifests
Manifests package the source event, Brief, Signals, Record, source URLs, dates, stable IDs, and delivery metadata.
02 / Fit
Use feeds when coverage is repeatable.
Synorb is a fit when an agent or application needs recurring, source-grounded context. It is an alternative to repeated scraping for known coverage areas, not an arbitrary scrape-any-URL system. If the workflow depends on known sources or durable coverage areas, listening first is usually cleaner than asking an agent to rediscover the web.
| Use Synorb for | Still use web search for |
|---|---|
| Monitoring sources, companies, topics, policies, data releases, filings, research, and current-event Streams. | Unknown sites, exploratory discovery, long-tail questions outside watched coverage, and one-off human browsing tasks. |
| Keeping agent memory current with provenance, stable IDs, and source URLs attached. | Filling gaps when the agent needs a source Synorb has not been asked to watch. |
03 / Shape
The app receives structured source events.
AI systems can use a Manifest directly in retrieval, ranking, summarization, alerting, review, or workflow automation. The object is designed to carry enough context for both machine use and human audit. This JSON manifest represents a source-grounded feed record delivered through MCP or REST.
Manifest excerptcontent feed
{
"manifest_id": "1777525429698648000",
"stream_names": ["company-monitoring", "ai-infrastructure"],
"source": {
"name": "Observed Source Channel",
"url": "https://source.example/update",
"published_date": "2026-06-17"
},
"brief": {
"title": "Source-grounded update"
},
"signals": [
{
"claim": "Atomic claim extracted from the source event",
"domain": "technology"
}
],
"record": {
"stable_id": "record_1777525429649909800"
}
}
04 / Connect
Use MCP during build, REST in production.
MCP is useful when an agent is exploring Streams, asking for Manifests, or prototyping a workflow. Shipped applications usually call Synorb from server-side code over REST, accept webhooks for new items, or ingest S3 archive exports for historical backfills and durable storage.
MCP
Agent-native workflow
Use Synorb MCP when a compatible agent should inspect Streams, retrieve Manifests, and cite source URLs during development.
REST / Webhooks / S3 Archives
Production delivery
Use the docs for API calls and delivery options. Keep credentials on the server side and route feed items into your own storage or workflows.
05 / Access
Scope and cadence drive cost.
Streams are priced by manifest volume and delivery cadence. Self-serve plans deliver Daily Batch; Enterprise adds Continuous Delivery, dedicated support, and SLA. For historical backfills, older months are available through S3 archive exports.
06 / Build
Build a content feed app with the coding agent you use.
The app pattern is consistent: the agent can use MCP to inspect Streams and sample Manifests while you build, but the deployed app should call Synorb from server-side code. Pick the guide that matches your builder and app shape.
FAQ
The short version.
What is a content feed for AI?
A content feed for AI is a structured stream of source-grounded updates that an agent or application can store, route, cite, and use without re-discovering the same source every time.
Is Synorb a web search API?
No. Synorb is built around watched Source Channels, Streams, and Manifests. It helps agents listen to known coverage areas and use web search only when they need to fill gaps.
What does Synorb return?
Synorb returns Manifests: structured objects that can include Briefs, Signals, Records, stable IDs, source URLs, source metadata, Stream routing, and ontology tags.
Does Synorb provide source URLs and citations?
Yes. Provenance is part of the product shape: source URL, source name, published date, capture date, Source Channel, and lineage travel with the Manifest.
Can I use Synorb in a shipped app?
Yes. Use REST or webhooks from server-side code for production delivery, and use S3 archive exports when you need historical backfills beyond the live API and MCP window. MCP is useful for agent-native development and interactive workflows.
Test
Test Synorb feeds for free.
Want to connect to Synorb's graph to test source-grounded feeds for free? Start with free test credentials, then connect through Core MCP or REST.
Free test credentialscurl
curl -s https://synorb.com/connect
Start
Give the agent a feed it can cite.
Start with keys, read the API docs, or use the build hub if you are connecting Synorb inside an agent-built application.