Trust begins with knowing where the data came from.

MacroFeed separates official observations from market context, preserves provenance, and makes missing information explicit.

Four operating principles

The methodology is designed for agents that need to reason about evidence quality, not merely display a populated calendar row.

01

Official truth first

Schedules, actual values, revisions, release documents, and timestamps come from publishing institutions wherever practical.

02

Market context stays typed

Consensus, user-supplied forecasts, official projections, model estimates, and market-implied values are different records.

03

Unknown remains unknown

Nullable fields and period-only history are preferable to an invented forecast or unverified release timestamp.

04

Verification is part of the interface

Coverage, field density, date ranges, source freshness, and gaps are designed to be inspected programmatically.

From institution to agent

Source adapters normalize different institution formats. The MCP then exposes focused read-only tools through CTX Protocol.

BLSECBBOEBOJ
MacroFeednormalize + verify
CTXProtocol API
LLMAgent answer

How fields are treated

Similar-looking numbers can represent very different kinds of evidence. MacroFeed keeps the distinction in the data model.

Actual / previousOfficial observation or confirmed official release sourceOFFICIAL TRUTH
Consensus forecastManual, user-supplied, or licensed-provider record with attributionMARKET CONTEXT
Schedule dateOfficial calendar preferred; curated rules labeled separatelySOURCE TYPED
Historical observationMay be period-only until its release timestamp is independently sourcedGAP DISCLOSED
SurpriseComputed only when a compatible attributed forecast is availableDERIVED