Freshness
Updated source context
Use feeds when the agent needs current information beyond model training data and static documentation.
Live RAG pipeline
A RAG pipeline with live web data needs clean context before retrieval.
A RAG pipeline is only as current as the data it ingests. Raw web pages can create noisy chunks and missing citations.
Synorb delivers source-grounded Manifests from watched Streams so live web context can move into retrieval with evidence intact.
MCP · REST · Source URLs · Stable IDs · Manifests
01 / Criteria
What should the data layer include?
For retrieval pipelines that use current web context with source evidence, 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.
How do you add live web data to a RAG pipeline?
Use a feed or API that delivers current source-backed objects, then route those objects into the retrieval store with citations preserved.
What makes live data safe for RAG?
Stable IDs, source URLs, dates, summaries, tags, provenance, and freshness metadata make live data easier to audit.
How does Synorb deliver live RAG context?
Synorb delivers Manifests through MCP, REST, and webhooks. S3 archive exports support backfills and replay.
Should every RAG system crawl the web directly?
Not always. Direct crawling can help with custom discovery, but watched feeds are cleaner for recurring coverage.
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.