Auto-generated. This article is rebuilt from FastAPI route introspection by scripts/build_api_kb.py. Edit the route docstring in app/ and re-run the script — do not edit this file directly.

POST /api/v1/signals/base-rates/compare

Handler: app.signals.routes.compare_base_rates
Methods: POST

Description

Historical Base Rate Engine — compare an arbitrary signal vector against history.

Sibling to GET /signals/base-rates. Key difference: the GET route always matches today’s latest row, this POST route lets a caller (typically the MCP compare_to_history tool) match a hypothetical signals_dict — “what if VIX were 35 and DIX were 0.38?”. When signals_dict is omitted, falls back to the GET route’s behavior (read latest live row).

Optional response-shape switches:

• include_analogue_dates: when true, append analogue_dates (per-analogue date, distance, weight, forward returns) sorted by distance ascending. Off by default to keep responses small.
• horizon (1, 3, or 5): adds a top-level headline shortcut block for the requested horizon. The full forward_Nd blocks are always returned.

Unknown signals_dict keys are accepted but logged at WARNING and ignored — the matcher already tolerates missing dims (each contributes nothing to the distance sum). Loud-fails silent dimension drift (a renamed column shows up as “unknown key” in logs).

Curl

curl -s https://bigclawd.com/api/v1/signals/base-rates/compare