You already have a news API.
You don't have typed events.
Most teams hack together three or four tools: a news wire, a filings parser, a scraper, a LLM classifier. It kinda works — until it doesn't. Hyperfeed replaces the stack with one normalized event stream, source-cited and schema-versioned.
Headlines. Unstructured text. Good luck.
- ×Duplicate stories — same event emitted 4–8 times from different outlets
- ×No structured payload — regex your way through the prose to extract numbers
- ×Allegations, rumors, and confirmed facts all get the same severity
- ×No entity resolution — "Meta," "META," "Facebook" are three different rows
- ×Story updates break your database — new URL, new row, no link back
- ×No filings correlation — news + 8-K are separate products
Typed events. Sourced. Dedup'd. Replayable.
- ✓One event_id per event — all 8 sources attached as evidence, auto-merged
- ✓Typed payload with every material field extracted (headcount, dollars, dates, tickers)
- ✓assertion_type flag on every event: fact · allegation · trusted_report
- ✓Canonical entity graph — ticker, LEI, parent-child, subsidiaries all resolved
- ✓Story updates = lifecycle transitions on the same event_id
- ✓News + filings + WARN + regulator actions all in one stream
Where the gap shows up.
Every row below is a question your platform team will ask. Our answer in blue; the alternative in gray. No fine print.
| Question | Hyperfeed | The News API |
|---|---|---|
| How is a duplicate story handled?same event from Reuters, WSJ, Bloomberg | One event with 3 sources in evidence[] | 3 separate rows, 3 UUIDs, no linkage |
| Can I filter allegations from facts?pre-SEC investigation vs. confirmed charges | ?assertion_type=fact | No such field — must NLP the body |
| How do I know when a story evolves?FDA CRL → company 8-K response | Same event_id, status transitions via /lifecycle | New article, new URL, no reference back |
| What about SEC filings?8-K Item 1.05 cyber disclosure | Same stream. Same schema. Same event_id logic. | Separate product · separate contract · separate API |
| Entity disambiguation?"Meta Platforms Inc." vs. "Meta" | Canonical entity · ticker · LEI · parent | String matching only — you disambiguate |
| Historical replay by point-in-time?backtest with no lookahead bias | as_of parameter on every endpoint | Lookahead contamination common; no as_of |
| Typical latency (press release → your code)lower is more alpha | 108s p50 · 240s p95 | 3–6 min + your own parse time |
| Does it come with an audit log?for compliance and replay | Per-event transitions, source merges, and confidence changes | Article text only |
The same FDA rejection. Theirs vs ours.
Monday, 4:47pm ET. ALDX receives a Complete Response Letter for reproxalap. Here's what hits your systems from each API.
{
"id": "news_a8x3kqm",
"headline": "ALDX Plunges 58% After Regulatory Setback On Reproxalap",
"published_at": "2026-04-13T21:01:14Z",
"body": "Shares of Aldeyra Therapeutics cratered in after-hours trading Monday after...",
"source": "benzinga_newsdesk",
"symbols": ["ALDX"],
"sentiment": "negative"
}
// + 3 more entries with similar unstructured text
// different URLs, different IDs, no linkage
// no structured CRL reason, no drug_id, no filing class{
"event_id": "evt_20260413_aldx_fda_crl",
"event_type": "fda_approval_declined",
"assertion_type": "fact",
"status": "official_announced",
"priority": "critical",
"entity": {
"ticker": "ALDX",
"name": "Aldeyra Therapeutics",
"lei": "529900W0O7QKGDLPGW09"
},
"payload": {
"regulator": "FDA",
"action": "complete_response_letter",
"product_id": "reproxalap",
"submission_type": "NDA",
"cycle_number": 3,
"manufacturing_concerns": true,
"efficacy_concerns": false
},
"lifecycle": {
"detected_at": "2026-04-13T20:58:41Z",
"announced_at": "2026-04-13T20:59:49Z",
"confirmed_at": "2026-04-13T21:00:56Z"
},
"sources": [
{ "tier": "tier_1", "name": "Company PR" },
{ "tier": "tier_1", "name": "Reuters" },
{ "tier": "tier_1", "name": "Bloomberg" },
{ "tier": "tier_2", "name": "Benzinga" }
],
"confidence": { "overall": 0.99 }
}Three reasons, in their own words.
We stopped burning engineers on duplicates.
News APIs emit the same story from six outlets as six separate records. Every consumer team writes their own dedup logic. Hyperfeed merges on entity + event_type + effective_at and attaches all sources as evidence. One event, many sources.
After:
event_id is the only key we need.Allegations aren't the same as facts.
News wires flatten "WSJ reports" and "company confirms" into one severity level. That's fine for humans. It's a disaster for auto-execution. Hyperfeed tags every event with assertion_type — allegation, trusted_report, fact.
allegation to human review, auto-routes factto systems. We couldn't do that with a news wire.Stories change. Your database should too.
An FDA rejection reported at 4:47pm becomes "official_announced" at 5:03 when the company files its 8-K. Hyperfeed represents this as one event with status transitions. A news wire represents it as two unrelated stories with different URLs.
lifecycle object: detected_at, announced_at, effective_at, confirmed_at, refuted_at. You can replay any event from any point in time.“We were paying six vendors for the same data at six different latencies. We replaced five of them with Hyperfeed.”— Head of Market Data, L/S equity fund · $4B AUM
Swap in. Dual-run. Cut over.
We don't ask you to rip out your existing pipeline on day one. Most teams dual-run for two weeks, then cut traffic when they've validated the schema against their own backtests.
Subscribe to the family you need.
Pick a single event family — usually regulatory or leadership. Point a webhook at your queue. Done.
POST /v1/subscriptions
{ "family": "regulatory",
"webhook_url": "https://you.co/hook",
"assertion_types": ["fact","trusted_report"] }Dual-run and diff.
We ship a difftool that runs against your existing pipeline's output and highlights where hyperfeed caught events sooner, merged duplicates, or classified differently.
hf diff \ --their-export their_feed.jsonl \ --date-range 2026-03-01:2026-03-31 > 142 events - hyperfeed earlier > 38 duplicates collapsed > 7 class conflicts
Cut over. Keep the old feed as backup.
Flip your primary. Most teams keep the legacy feed on standby for 30 days. After that, the vendor contract lapses. Most teams find Hyperfeed replaces 2–3 existing tools at a fraction of the combined cost.
hf subscribe \ --families all \ --deliver kafka://your-cluster/events \ --replay-from 2026-01-01 > 14,207 historical events backfilled
Stop parsing headlines. Start reading events.
See the diff yourself. The 7-day delayed feed shows the same events your current vendor misses. Compare side-by-side, no meeting required.