API & MCP Changelog

Data freshness: new GET /api/v1/status (free) and MCP status://current resource report how current the data is (ingestion / enrichment frontier), the Daily World Brief status, and an Operational / Delayed / Degraded roll-up.

Schema clarity: severity_score and geoint_score are documented with their 0–10 range; escalation_trend now publishes its enum (escalating, de-escalating, stable, new); the /signals parameters observability, open_data, min_information_gain, updated_since, and created_since are documented; sample responses were corrected to include the intelligence block. The machine-readable spec at /api/v1/openapi.json is the source of truth.

Signal filters (observability, min_information_gain, min_severity, markets, escalating) now apply across the full result window before ranking and pagination — a matching event deeper in the feed is no longer dropped, so filtered queries stop returning an empty result when matches exist. REST and MCP behave identically.

The Daily World Brief now passes a deterministic quality gate before publishing; a truncated or structurally-incomplete brief is held back and the previous good brief keeps serving.

Plan access clarified: the REST API, the MCP server, and the AI tools (assess_signal / ask_analyst) are available on every plan, including Free — the only gate is your token balance. get_world_brief and get_usage are free.

MCP: serverInfo.icons[].sizes is now an array per the MCP spec (SEP-973), so strict clients no longer fail to initialize. MCP surface version is 1.3.1.