Is the data fresh, and are the APIs answering? This page is for anyone who builds on our feeds: if a stream looks stale or a call fails, start here. The site, the proof chain and the pipeline table are checked live from your browser. The two APIs run on demand, so their row and the freshness table come from our own daily health check, taken after the nightly refresh; press "Run a live check" to hit them yourself. Nothing here is account-specific.
Services right now
| Service | Now | Detail |
|---|---|---|
| Website (datasignalslab.com) | checking | reports, product pages, proof files |
| Events API (/v1) | checking | twelve filing and career-site streams |
| Jobs API (/jobs/v1) | checking | open jobs from company career sites |
| MCP servers | checking | datasignals-mcp and events-mcp on Apify, checked daily by our watchdog |
| Proof chain | checking | one hash per day over every published dataset, anchored in Bitcoin |
Checking.
Data freshness per stream
Every stream is refreshed on its own schedule: most nightly, Congress trades and NIH grants weekly, 13F institutional holdings once a quarter. "Fresh" means the last refresh is within that schedule. The nightly sources file on business days only, so a quiet weekend is not counted against them. "Last refresh" is plain elapsed time, as you would measure it yourself.
| Stream | Last refresh | Schedule | Events | Status |
|---|---|---|---|---|
| Loading the watchdog's latest /v1/health snapshot. | ||||
Nightly pipelines
The data on this site is produced by scheduled jobs on our own servers. Each job reports to RunVouch, the watchdog built by the same team: a missed run, a silent failure or a job that exits 0 without producing anything raises an alert there. This table is that watchdog's public view of our fleet.
| Job | Last run | Result | Last 30 days |
|---|---|---|---|
| Loading from api.runvouch.com. | |||
Check it yourself
You do not need this page to verify us: /v1/health and /jobs/v1/health answer with JSON and a last-refresh timestamp, /api/proof.json lists every sealed day with its hash, and the fleet feed is the raw data behind the pipeline table. Incidents are written up on the blog.