A scoring change that moves your numbers is a breaking change even when the schema is identical. Those are flagged, versioned and opt-in — you pin a methodology version and move when you choose to.
policy_events[].approved_by now returns null explicitly when a multisig change has no recorded approval, instead of omitting the field. Alert on null — this is the finding that matters most.withheld[] array returns candidates that were screened out, each with a reason code. Previously they were silently absent, which made an empty routes[] impossible to debug.X-FTAI-Scoring-Version: 3 to stay on v3 until Q1 2027. Nothing moves under you without opting in.PEEL_CHAIN and CROSS_CHAIN_LAYERING. Additive — existing integrations are unaffected.coverage object stating which chains were consulted and whether any were stale. You should no longer need this website to know if an answer was complete.as_of parameter reconstructs a profile as it would have been on a past date, so backtesting is a fair test instead of hindsight.X-FTAI-RateLimit-Remaining and -Reset on every response, including errors.code alongside the message. Match on the code; the message is for humans and may be reworded.Releases before v2.9 are in the archive, available from the docs. Deprecations are announced at least 90 days ahead and never removed inside a minor version.
Breaking-capable releases go out by email 30 days ahead, with the expected impact on your own alert volume where we can measure it.