Updated source context
Use feeds when the agent needs current information beyond model training data and static documentation.
News-aware RAG systems fail when ingestion drops dates, source URLs, canonical IDs, or topic labels before the data reaches retrieval.
Synorb delivers Manifests from watched source coverage so RAG pipelines can ingest compact, current, cited objects instead of re-cleaning pages at query time.
MCP · REST · Source URLs · Stable IDs · Manifests
For a source-grounded ingestion path for current news and source events in RAG systems, the useful unit is not a loose search result. It is an object the agent can retrieve, cite, filter, store, and audit.
Use feeds when the agent needs current information beyond model training data and static documentation.
Source URLs, dates, and stable IDs help the application cite, inspect, and audit what the model used.
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.
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_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"]
}
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.
Use Synorb MCP to discover Streams, inspect details, and retrieve Manifests inside an agent workflow.
Push source-grounded Manifests into retrieval stores before users ask for current answers.
Build dashboards, feeds, monitors, and briefings with source URLs available at display time.
It is the ingestion path that keeps current news or source updates available to a retrieval system before prompts run.
Keep source URLs, dates, stable IDs, summaries, tags, provenance, and enough delivery state to refresh or replay the object.
Synorb supplies Manifests through MCP, REST, and webhooks so teams can route source-backed updates into retrieval stores or application databases.
No. Synorb supplies fresh source-grounded input. A vector database can still store embeddings and retrieve relevant objects downstream.
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.
curl -s https://synorb.com/connect
Start with keys, then connect through Core MCP while building or REST when your application owns the workflow.