Freshness
Updated source context
Use feeds when the agent needs current information beyond model training data and static documentation.
Agent web access
Web access for AI agents should be more than page retrieval.
An agent with web access can fetch pages, but a production workflow also needs evidence, dates, summaries, tags, and enough structure to make the context reusable.
Synorb gives agents feed-first access to watched sources through Manifests, so current web context arrives with provenance attached.
MCP · REST · Source URLs · Stable IDs · Manifests
01 / Criteria
What should the data layer include?
For current web context delivered to agents with citations and structure, 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 web access for AI agents?
It is the ability for an agent to use current web information while planning, answering, monitoring, or taking action.
Why is raw page access not always enough?
Raw pages can be stale, duplicated, hard to chunk, and difficult to cite after the model has processed them.
How does Synorb provide web access?
Synorb watches source coverage and delivers source-grounded Manifests over MCP, REST, and webhooks, with S3 archive exports for older history.
Where does this fit in an agent architecture?
Use Synorb as the live context layer before retrieval, planning, alerting, briefing, or dashboard rendering.
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.