1,000 calendar rows contain 23 distinct schemas and only 2.7% carry a title. The filters discriminate server-side even though the columns are not projected — so filter, do not parse. Updated at 25 August 2026. FinUties Study · Calendar · Twenty-three row shapes behind one endpoint By FinUties · organization byline · The organization reports no position in any instrument named. Informational only — not investment advice, and no claim is made about domains outside the P0 surface. Scope P0 domain: calendar. The question in one sentence: should an integrator parse /api/v1/calendar/events rows or filter them? This study measures schema heterogeneity, enrichment coverage, and whether the documented filters discriminate. It does not forecast any release, does not interpret any scheduled event, and does not treat any non-P0 domain as covered. The reading it arrives at: the endpoint is a union of provider-native row shapes, so parsing is the wrong instinct — but the filters work server-side, so filtering is the right one. Question This is answerable from P0 data because both halves are directly observable: row shapes are the key sets of returned rows, and filter behaviour can be tested by comparing a real value against a nonsense value on the same parameter. It would become unanswerable if the question shifted to whether the schedule is correct, which requires checking each publisher's own calendar rather than FinUties. Evidence manifest This study rests on 8 pulls from the calendar domain between 19:43 and 19:52 UTC on 2026-08-18. Every row below is re-runnable. | | Pulled (UTC) | Domain | Endpoint | Query | Rows | Freshness | Replay | |---|--------------|--------|----------|-------|-----:|-----------|--------| | 1 | 2026-08-18 19:48 | calendar | /api/v1/calendar/events | limit=100, offset=0…900 (10 pages) | 1,000 | not recorded — probe resolved no table | REST GET /api/v1/calendar/events?limit=100&offset=0 · MCP {"domain":"calendar","resource":"events","limit":100} | | 2 | 2026-08-18 19:52 | calendar | /api/v1/calendar/events | country=US, limit=100 | 100 | as row 1 | REST GET /api/v1/calendar/events?country=US&limit=100 | | 3 | 2026-08-18 19:52 | calendar | /api/v1/calendar/events | country=ZZZZ, limit=100 | 0 | as row 1 | REST GET /api/v1/calendar/events?country=ZZZZ&limit=100 | | 4 | 2026-08-18 19:52 | calendar | /api/v1/calendar/events | importance=high,…
Pipeline-assisted research note with publish gates. Informational only — not investment advice.
Continue to interactive article · Data API · MCP · Pricing · About