Signal
Atomic claims
Each Signal is a claim with evidence, confidence, entities, dates, source metadata, and domain classification.
MCP / News
MCP Server For News.
Agents do not need another headline feed. They need source-grounded change in a format they can discover, inspect, pull, diff, and route. Synorb Core MCP exposes live Streams through three primary tools, with Advanced MCP for configured workflows and REST APIs for heavier Manifest retrieval.
Core MCP: 3 tools · Advanced MCP: configured workflows · REST API for volume
01 / Unit
News is not the unit. The Manifest is.
A news result tells an agent that something exists. A Manifest gives it the source event, the extracted claims, the compact Brief, the canonical Record, stable IDs, and provenance in one object.
Brief
Compact context
Each Brief keeps the important claims together so agents and humans can review the source event without parsing raw prose again.
Record
Canonical object
Each Record keeps joins, lineage, replay, and warehouse-grade use possible when the same event enters downstream systems.
02 / Streams
Three primary tools. Many Streams.
Connect once to Core MCP, then let the agent discover candidate Streams with synorb-catalog, inspect filters and coverage with synorb-details, and pull Manifests with synorb-manifests. Advanced MCP is a separate URL for configured workflows that need lower-level access.
synorb-catalog
Find candidate Streams
Search by topic, entity, source type, or domain and get the Streams most likely to match the user's intent.
synorb-details
Inspect filters
Read coverage, source channels, home domains, tag types, date ranges, media formats, and safe query options.
synorb-manifests
Pull Manifests
Apply filters, inspect counts, retry with broader Streams when needed, and return Briefs, Signals, and Records.
03 / Provenance
Source Channels preserve provenance.
Agents need to know where a claim came from before they can act on it. Synorb keeps source name, URL, published date, captured date, Stream routing, and lineage together so the agent can trace a Manifest back to the watched surface.
Manifest excerptprovenance
{
"manifest_id": "1777525429698648000",
"stream_names": ["mayfield"],
"source": {
"name": "Mayfield Blog",
"media_format": "text",
"published_date": "2026-04-30"
},
"lineage": {
"source_channel_id": "mayfield-blog",
"record_id": "1777525429649909800",
"brief_id": "1777527738510498300"
},
"delivery": {
"interfaces": ["REST", "MCP", "webhook", "S3"]
}
}
04 / Formats
Briefs, Signals, and Records do different jobs.
A single agent may need all three. Signals drive reasoning and alerts. Briefs fit context windows and operator review. Records keep the original source event structured enough for joins, replay, and audit.
Briefs
Readable context
Use Briefs when an agent needs compact narrative without losing the claims it was built from.
Signals
Reasoning atoms
Use Signals when the workflow needs claim-level matching, routing, confidence, and evidence.
Records
Durable source state
Use Records when the data needs stable IDs, source metadata, warehouse joins, and replay.
05 / Interfaces
Use MCP for discovery. Use REST for volume.
MCP is the right surface when an agent needs to reason through intent, discover Streams, inspect filters, run a Manifest query, observe the result, and refine. REST API is the explicit path for applications, jobs, tests, dashboards, and high-throughput retrieval.
MCP
Agent-native access
Give Claude, Codex, Cursor, Windsurf, Perplexity Computer, or a custom agent the Core connector URL and token. Use Advanced MCP only for configured workflows that need account, digest, sync ontology, label, prompt-template, or low-level content tools.
REST API
Code-owned access
Use REST for high-volume Manifest pulls, deterministic polling, tests, dashboards, data jobs, and latency-sensitive product paths.
06 / Access
Start with credentials, then choose cadence.
The free tier includes 1,000 manifests per month on monthly delivery. Streams scale by manifest volume and refresh cadence. Firehose is for platforms that need everything Synorb writes, the moment it is written.
FAQ
The short version.
Is Synorb a news API?
Synorb is a temporal context graph for AI systems. News and source events are part of what enters the graph, but the product unit is the Manifest.
Do I need MCP?
No. Core MCP is the agent-native discovery interface. Advanced MCP, REST API, webhooks, and S3 are available for configured or application-owned delivery patterns.
What does an agent get first?
Credentials return an API key, secret, MCP token, Core connector URL, and Advanced connector URL. From there the agent should run synorb-catalog, inspect candidates with synorb-details, then retrieve with synorb-manifests.
Access
Agents: curl the endpoint. Humans: enter your email.
Free tier: 1,000 manifests per month on monthly delivery. Agents can self-provision credentials and MCP config with one request. Humans can use the credentials page and receive the same key, secret, MCP token, Core connector URL, Advanced connector URL, and schema PDF by email.
Agent startcredentials
curl -s https://synorb.com/connect
Returns: api_key, api_secret, mcp_token, connector URL.