Thank you for flagging this issue for us. This seems to be a bug in how our API displays this value, not an intentional change. I've passed this onto our engineering team, and we will push a fix as soon as possible.