We've identified what's causing this issue and have rolled back the change. Affected predictions will have completed successfully and you can re-request their status through the API.

We're investigating a problem where users are receiving garbled responses from requests to the API.