Is it out yet? (release status)
Use this when you need to know whether a scheduled US release (CPI, PPI, payrolls, JOLTS, GDP, PCE, FOMC, retail sales, claims) or an S&P 100/NASDAQ-100 earnings 8-K is out, when it was first seen, and actual vs prior vs revision.
What it is
For each macro release: scheduled time, state (scheduled / due_not_seen / due_untracked / out / out_untimed = actual present but released before the watcher saw it), detection method and URL, first_seen_at from the cev-os watcher (polled every minute 8 AM-3 PM ET weekdays), the publisher's own timestamp when it states one (BEA RSS pubDate), latency in seconds, actual and prior (from the macro calendar, official publishers) and the revision of the prior vs its first-reported value (ledger-based; null until the ledger has seen the prior release). With ticker=, returns the latest SEC 8-K Item 2.02 acceptance time (EDGAR) for that issuer.
Endpoints
- REST:
GET /v1/release-statusonhttps://api.cev-os.com - Legacy host (same service):
GET /v1/release-statusonhttps://cev-os.com - MCP tool:
get_release_statusonhttps://mcp.cev-os.com/mcp
Parameters
| Name | Type | Description | Constraints |
|---|---|---|---|
event | string | Comma-separated event types: cpi, ppi, employment_situation, jolts, eci, gdp, pce, retail_sales, jobless_claims, fomc_decision, fomc_minutes, ism_manufacturing, ism_services, trade_balance, productivity | example cpi,employment_situation |
from | string | Start date (ET) YYYY-MM-DD, default 7 days ago. | pattern ^\d{4}-\d{2}-\d{2}$ |
to | string | End date (ET) YYYY-MM-DD, default 2 days ahead. | pattern ^\d{4}-\d{2}-\d{2}$ |
ticker | string | S&P 100 / NASDAQ-100 ticker: adds its latest 8-K Item 2.02 (earnings) acceptance time. | example NVDA |
Example request
No account and no key. Query values below are the examples or defaults from the registry. An optional free key (header x-api-key) raises the limits; create one at https://cev-os.com/#api_keys after signing in with a verified email (Google sign-in is already verified).
curl -s "https://api.cev-os.com/v1/release-status?event=cpi%2Cemployment_situation&ticker=NVDA"
Example response
Every /v1 response is a JSON envelope (schema_version, product, timestamps, license, attribution, data). The registry example is the data member:
{
"releases": [
{
"event_id": "cpi:2026-11-10",
"eventType": "cpi",
"scheduled_at": "2026-11-10T13:30:00.000Z",
"state": "scheduled",
"detection": null
}
]
}
Update frequency
Watcher every minute 8:00 AM-2:59 PM ET weekdays (macro) and every 2 minutes 6 AM-9 PM ET weekdays (SEC).
- Public cache:
30seconds (Cache-Control: public, max-age=30).
Sources, license and usage
License status: cleared. US Government works (BLS, BEA, Census, Fed, DOL, SEC); timing measurements are cev-os's own.
Attribution (show this wherever you display the data):
- Sources: BLS, BEA, U.S. Census Bureau, DOL, Federal Reserve Board, SEC EDGAR. Detection timestamps measured by cev-os. This service uses BEA data but is not endorsed or certified by BEA.
Privacy class: public-derived. Access: public. Price: free (price is null; pay-per-call is not active).
Gaps
- first_seen_at granularity is about 1 minute (Cloud Scheduler).
- actual comes from the macro calendar snapshot (official publishers, re-read up to every 30 min after a release), so it can lag the release by up to ~30 min.
- Retail sales and claims have no machine-readable publish signal: marked out when the calendar snapshot has the value.
- Revisions start with this ledger (2026-10-17); no keyless vintage source exists.
Related
- Data API hub (all products, limits, license notes)
- MCP Registry listing
com.cev-os/data - OpenAPI 3.1
- Machine product list:
/v1/products
Reference data, not investment advice.