External agent data

External data for AI agents should arrive with evidence.

AI agents need current external information about companies, markets, policy, media, science, and other changing domains. Raw pages and search snippets are hard to route, cite, and audit.

Synorb turns watched external sources into Streams of Manifests, giving agents compact source-grounded objects instead of asking every workflow to rediscover the web.

MCP · REST · Source URLs · Stable IDs · Manifests

What should the data layer include?

For external source updates delivered as structured, cited objects for AI agents, the useful unit is not a loose search result. It is an object the agent can retrieve, cite, filter, store, and audit.

Freshness

Updated source context

Use feeds when the agent needs current information beyond model training data and static documentation.

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.

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"]
}

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.

Short answers for AI builders.

What is external data for AI agents?

External data for AI agents is current information from outside the application that the agent can retrieve, cite, route, and use in a workflow.

Why not let the agent search the web every time?

Search helps with unknown discovery. Watched feeds are better when your team already knows which sources or topics it needs to monitor.

How does Synorb deliver external data?

Synorb delivers current Manifests through Core MCP, REST APIs, and webhooks. S3 archive exports support historical backfills and replay.

What should external agent data include?

Useful external data includes source URLs, dates, stable IDs, summaries, tags, provenance, and delivery metadata.

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

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.