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. Everything below is checked live from your browser against the same public endpoints you use; nothing 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.
| Stream | Last refresh | Schedule | Events | Status |
|---|---|---|---|---|
| Loading from /v1/health. | ||||
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.