Updated source context
Use feeds when the agent needs current information beyond model training data and static documentation.
RAG quality starts before retrieval. If ingestion loses the source URL, date, tag, or stable ID, the answer layer has less to cite and audit later.
Synorb delivers source-grounded Manifests that can enter retrieval stores, vector indexes, or relational tables with provenance still attached.
MCP · REST · Source URLs · Stable IDs · Manifests
For fresh source-backed inputs for retrieval stores and answer 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.
A RAG ingestion API sends current, structured content into retrieval systems before prompts ask for answers.
It should include source URL, source date, stable ID, summary, tags, and provenance fields that survive embedding and retrieval.
Synorb emits Manifests from watched Streams so teams can ingest current source-grounded objects into vector stores or databases.
No. Synorb supplies fresh, cited input. Your retriever decides how to index, rank, and return it.
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.