Source event
What changed
A watched Source Channel emits an update: filing, report, post, release, transcript, notice, feed item, or data change.
API / Structured News
Structured News API For AI.
AI systems do not need another list of links. They need source-grounded change in a shape they can reason over. Synorb turns news and source events into Manifests with Briefs, Signals, Records, stable IDs, provenance, and Stream routing.
REST API + MCP + webhooks · Briefs / Signals / Records · 12-domain ontology
01 / Structure
Structured news is source-grounded change.
Headlines are written for human browsing. Agents need the change, the claims, the evidence, the source state, and the lineage. Synorb structures source events so AI systems can listen instead of search.
Manifest
What to use
The source event becomes a Manifest with a Brief, Signals, Record, stable IDs, provenance, and Stream routing.
Agent state
What to remember
The agent stores claims and source state instead of scraping pages again or relying on a prompt-sized summary.
02 / Unit
The API returns Manifests, not loose articles.
A Manifest is the product unit. It keeps the source event and the AI-ready structure together, so the same object can support agent reasoning, operator review, warehouse joins, audit, replay, and downstream workflow routing.
Brief
Readable context
A compact explanation of the event, grounded in the source and fit for human or agent review.
Signals
Atomic claims
Structured claims with evidence, entities, dates, confidence, and domain classification.
Record
Durable source state
The canonical object for joins, replay, source metadata, stable IDs, and lineage.
03 / Signals
Signals are atomic claims.
News APIs usually return documents. AI systems need claims they can compare, route, and score. Signals make a source event usable for monitoring, ranking, retrieval, alerts, and workflow decisions.
Manifest excerptstructured
{
"manifest_id": "1777525429698648000",
"stream_names": ["ai-infrastructure"],
"source": {
"name": "Observed Source Channel",
"media_format": "text",
"published_date": "2026-05-05"
},
"brief": {
"title": "Source event summary"
},
"signals": [
{
"claim": "Atomic claim extracted from the source event",
"domain": "technology",
"confidence": 0.91
}
],
"record": {
"stable_id": "record_1777525429649909800"
},
"lineage": {
"source_channel_id": "observed-source-channel"
},
"delivery": {
"interfaces": ["REST", "MCP", "webhook"]
}
}
04 / Review
Briefs keep the event human-legible.
Structured does not mean unreadable. Briefs keep the compact narrative close to the claims, so teams can inspect what an agent used and decide whether the source event should move into a workflow.
Briefs
Readable context
Use Briefs when an agent needs compact narrative without separating the summary from source-grounded claims.
Signals
Reasoning atoms
Use Signals when the workflow needs claim-level matching, routing, confidence, evidence, and comparison.
Records
Durable source state
Use Records when the data needs stable IDs, source metadata, warehouse joins, and replay.
05 / Records
Records keep joins and replay possible.
Agents are not the only consumer. Internal tools, warehouses, alerts, dashboards, and evaluation jobs need stable IDs and durable source state. Records keep the structured news API useful outside the immediate context window.
Stable IDs
Repeatable joins
Use stable identifiers when the same source event needs to move through agent memory, product surfaces, and data systems.
Lineage
Replayable context
Keep source URL, Source Channel, capture date, published date, Stream routing, and Record lineage attached.
06 / Streams
Streams keep coverage scoped.
Choose Streams when the product knows what it needs to listen to: entities, topics, domains, source sets, or saved queries. Use Firehose when the platform needs the full context graph and archive.
FAQ
The short version.
Is Synorb a news API?
Synorb is a temporal context graph for AI systems. News and source events enter the graph as structured Manifests.
What is structured?
Briefs, Signals, Records, stable IDs, source provenance, Stream routing, and 12-domain ontology tags are structured around each source event.
What does an agent get first?
Credentials return an API key, secret, MCP token, and connector URL. From there the agent can list Streams and fetch 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, connector URL, and schema PDF by email.
Agent startcredentials
curl -s https://synorb.com/connect
Returns: api_key, api_secret, mcp_token, connector URL.