CHANGELOG
Only things that affect an integration are here. Site copy, design and Record research are not: they belong on the Record status page, which is where coverage movement is reported.
The promise. Inside /api/v1, fields are added and never removed, types never change, and a value never quietly starts meaning something else. A change that would break a client gets a new path. A deprecated field keeps returning its old value for at least 90 days after it appears here as DEPRECATED.
2026-08-27 · ADDED
A Streamable HTTP MCP server carrying all 18 capabilities as tools, authenticated with the same bearer key as the REST API. Stateless: no session id is issued. Previously MCP was stdio only and shipped in a private repository, so no external client could connect.
2026-08-27 · ADDED
A free plan and a key management surface at /developers/keys. An email address and a sign-in link are the whole signup. Keys are shown once, hashed at rest, and can be rotated and revoked by their owner.
2026-08-27 · ADDED
Generated from the capability manifest rather than hand-written, so an operation cannot be missing for a capability that exists. The servers entry is derived from the request host.
2026-08-27 · ADDED
Overview and quickstart at /developers, MCP setup, full reference, the evidence model, and integration recipes. Every code example is executed by the test suite against the built Worker.
2026-08-22 · ADDED
Confirmed Signals in release order, newest first, with cursor paging and filters for product, brand, dimension and category. It orders on release rather than on the observation window, because a change observed in 2024 and released in 2026 is new to a client that has never seen it.
2026-08-22 · CHANGED
Six surfaces read the CONFIRMED filter directly rather than the publication gate, so they disagreed about which deltas a Signal may state. Every surface now renders one projection. Values a client received before this that the gate refuses are no longer returned.
2026-08-09 · ADDED
Twelve capabilities over the Record behind API keys, scopes, plan entitlements, rate limits, usage metering and a daily distinct-entity budget.