v3.4 changelog.

v3.4 adds three high-signal fields to the alert record. effective_jurisdictions resolves the working set of jurisdictions an alert applies to, computed from the regulator and the alert text rather than left as the regulator’s home. confidence_score is a numeric score for how confidently PERCIVAL classified the alert, exposed for downstream filtering. related_alerts is an array of alert IDs that LADI has linked through shared regulators, regulations, or topics.

A new POST endpoint, /v3/relationships, returns the LADI graph for a given anchor (an alert, a regulator, or a regulation). Use it for ‘what else does this connect to’ queries without writing a graph traversal in your own code. The response shape is documented in full at docs.regalytics.ai.

The MCP server exposes the new endpoints automatically. We have also expanded the tool definitions to include richer parameter descriptions, which improves agent reasoning materially in our internal benchmarks. If you’re calling MCP through Claude or ChatGPT, you will see better tool-selection behaviour without changing anything on your side.

v2 enters maintenance-only on 1 July 2026 and end-of-life on 31 December 2026. Migration is straightforward for most customers: field names align, and the migration guide at docs.regalytics.ai/migrate-v2-v3 covers every breaking change with a side-by-side example. Customer success engineers can run the migration with you on request.

Authentication is unchanged. Pagination is unchanged. Rate limits are unchanged. The MCP server URL is unchanged. Webhook payload schemas are additive: existing fields keep their shape, new fields appear alongside them.