Updated source context
Use feeds when the agent needs current information beyond model training data and static documentation.
Agents that answer customers, analysts, or operators need citations that survive retrieval, summarization, and display.
Synorb Manifests keep source URLs, dates, stable IDs, Briefs, Signals, and tags attached so applications can show evidence without reconstructing it later.
MCP · REST · Source URLs · Stable IDs · Manifests
For citation-ready source metadata for agent and RAG workflows, 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 an API that returns context with source metadata the agent or application can cite in an answer.
Source URL, source name, date, stable object ID, and provenance fields are the core citation metadata for AI workflows.
Synorb creates Manifests with source evidence and stable identifiers, then delivers those objects through MCP, REST, and webhooks.
Yes. Teams can keep Manifest IDs, source URLs, dates, and tags as structured metadata beside embeddings.
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.