Agent retrieval

A retrieval API for AI agents should return context the app can trust.

Agent retrieval is not only about finding text. The application needs to know where the context came from, when it was observed, and whether it can be cited.

Synorb lets agents retrieve source-grounded Manifests from Streams, then use those objects in RAG, dashboards, monitors, and operational workflows.

MCP · REST · Source URLs · Stable IDs · Manifests

What should the data layer include?

For retrieval of current source-grounded context for agent workflows, 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 a retrieval API for AI agents?

It is an API that returns context objects an agent can use while planning, answering, or taking action.

What should retrieval return?

Useful retrieval returns compact content plus source URLs, dates, stable IDs, tags, and provenance metadata.

How does Synorb retrieve context?

Core MCP lets agents discover Streams and retrieve Manifests. REST supports product dashboards, scheduled jobs, and server-side retrieval flows.

When is feed retrieval better than live search?

Feed retrieval is better for repeat coverage and known sources. Live search is better for open-ended discovery.

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.