Data Infra · 05
Curated technology and AI market news with two timestamps on every item: when it was published, and when we saw it. Trending detection and per-ticker sentiment as honest, dated series.
Accurate · Reliable · Source‑backed
What's inside
AI and technology market news, ticker-tagged, noise filtered before it reaches you.
Which stories are accelerating in coverage, and exactly when they started to.
Article-level and aggregate sentiment per ticker, as a dated series, not a mood.
Every item traces to its article. Nothing arrives as a paraphrase without a pointer.
The data, not a description of it
Every item ships with its article link and both timestamps, so backtests know exactly what was knowable when.
Bargo Verification Layer · Accurate · Reliable · Source‑backed
A story publishes. Here is what happens before it becomes a data point:
Timestamps are parsed strictly. When a source date cannot be read with confidence, the field stays empty, so the crawl time never impersonates the publish time.
Published and seen are separate fields on every row, forever. Point-in-time honesty is structural, not a disclaimer.
Sentiment is a model output, and it ships labeled as one, with the model version on the row. Trending scores are computed from counts.
Only then does the item ship: linked, double-dated, honestly labeled. News data you can put in a backtest without archaeology. See the full Verification Layer →
Access
News questions with receipts: what broke, what is accelerating, and how it reads.
Wire it into Claude, Cursor or your own agents, or pull straight into pandas.
Feed, trending and sentiment series as clean endpoints, ticker-tagged throughout.
Who runs on it
What broke overnight on your names, ranked by acceleration, each item linked to its article.
When a story started, how it spread, and how coverage tone shifted, with sources.
Dual timestamps kill lookahead at the schema level. Sentiment ships versioned, ready to be a feature.
Coverage & delivery
| Coverage | Curated AI and technology market news, ticker-tagged. |
| Latency | Continuous ingestion; items carry both published and seen timestamps. |
| History | Dated series suitable for point-in-time work, keyed on what was knowable when. |
| Formats | JSON over API, CSV / Parquet snapshots, digest-stamped. |
| Identifiers | Tickers on every item, for joins with the rest of the catalog. |
| Verification | Every row carries its source and its checks. Corrections are versioned, snapshots digest-stamped. How the Verification Layer works → |