get_indicator_history

ai.jawz/jawz · Verify this server

Any card of the Jawz Dashboard (get_dashboard), or one of its rows, over time, each at its own print dates: the weekly reads for the weekly cards, the release dates of the series behind a row for the rest. With no arguments it returns the catalogue: every card and indicator key with its kind, cadence, unit, source and the earliest date it reaches. card alone returns that card's badge (indicator defaults to 'badge'); card plus indicator returns that row. from and to (YYYY-MM-DD) set the window: to defaults to today and from to one year before to; the history reaches back 365 days (store of value starts 84 days later), and a clamped window is echoed as requested_from and effective_from. Every point carries Jawz's word for that date and point_in_time. What Jawz computes (the six badges, the four-bank money total, the dollar effect, US money, the growth vote) also carries the value and its display at every point. Published series that Jawz passes through unchanged (mood, jobs, BEA investment, prices, rates, credit, the dollar, gold, bitcoin, data centres, chips, builders' capex, power) carry Jawz's word per print plus the source (provider, series, link and, for FRED series, the ALFRED vintage link), because the full numbers stay with the publisher. The answer adds the rule in one sentence, transitions (every change of word), runs, and the current word with the date it has held since (for a badge, the card's own held_since). History applies today's rules to what was published by each date (rules: 'today'): method_events lists rule changes in the window that moved the card, and published_differs lists, for the regime and business-cycle badges, the dates where what Jawz published that day differs. The four-bank money rows add the coverage basis, a constant three-bank total and coverage and PBoC-statement events. An unknown card or indicator, a malformed or future date, or a date before the window returns an error naming the valid keys or range. A cold window that runs out of compute time returns the points ready with partial: true and pending_from; the same call again continues from the points already kept. Read-only, no account needed. Information, not investment advice.