Freshness
Updated source context
Use feeds when the agent needs current information beyond model training data and static documentation.
Event detection feeds
News clustering for event detection should create citable workflow objects.
Event detection is hard when the application only sees isolated links. Agents need to understand what changed, which source supports it, and how the event should be routed.
Synorb Manifests give workflows stable source-grounded objects with Briefs, Signals, tags, source URLs, and dates that can support monitors, briefings, and retrieval.
MCP · REST · Source URLs · Stable IDs · Manifests
01 / Criteria
What should the data layer include?
For source-backed event updates for monitors, agents, and retrieval workflows, the useful unit is not a loose search result. It is an object the agent can retrieve, cite, filter, store, and audit.
Grounding
Evidence stays attached
Source URLs, dates, and stable IDs help the application cite, inspect, and audit what the model used.
Delivery
MCP, REST, webhooks, and archives
Agents can explore through Core MCP. Production systems use REST and webhooks for current delivery. The live window covers the current calendar month plus the previous three full months; S3 archive exports support historical backfills and replay for older months.
02 / Shape
A Manifest is the object the agent can use.
This JSON manifest is the source-grounded object delivered through MCP or REST. It is compact enough for an agent workflow and explicit enough for an application to store, cite, and audit.
Manifest excerptJSON
{
"manifest_id": "1777525429698648000",
"headline": "Source-grounded update for an AI workflow",
"summary": "What changed, why it matters, and what source supports it.",
"source": {
"name": "Watched source",
"url": "https://source.example/update",
"published_date": "2026-06-21"
},
"delivery": {
"mcp": "https://mcp.synorb.com/mcp",
"rest": "https://api.synorb.com"
},
"tags": ["company", "topic", "source-backed"]
}
03 / Fit
Where Synorb fits in the workflow.
Use Synorb when your team already knows the sources or topics it needs to monitor, and the workflow needs current context again and again. Use search or crawling for open-ended discovery.
Agents
Pull live context
Use Synorb MCP to discover Streams, inspect details, and retrieve Manifests inside an agent workflow.
RAG
Load before prompts
Push source-grounded Manifests into retrieval stores before users ask for current answers.
Apps
Render with citations
Build dashboards, feeds, monitors, and briefings with source URLs available at display time.
FAQ
Short answers for AI builders.
What is news clustering for event detection?
It groups related source updates so an application can detect and route meaningful events instead of isolated mentions.
What should an event object include?
It should include a summary, source evidence, published date, stable ID, tags, provenance, and routing metadata.
How does Synorb represent events?
Synorb represents source-backed updates as Manifests with Briefs, Signals, tags, source URLs, dates, and stable IDs.
Where can event feeds be used?
Use them in monitors, dashboards, alerts, RAG stores, briefings, and agent workflows that need current evidence.
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 your agent fresh source-backed context.
Start with keys, then connect through Core MCP while building or REST when your application owns the workflow.