Makes sense. The problem I have with it is that there's no way they could have determined if an API key was stolen or not, even to this day. Basically, their

Makes sense. The problem I have with it is that there's no way they could have determined if an API key was stolen or not, even to this day. Basically, their docs (which seemed auto-generated) pointed to a domain they did not own (verified this). So if you ran any API examples you sent your keys to a 3rd party. I know because I did this. There's no way to know that the domain in the docs is simply wrong. I tried explaining this to the support people, that I needed to talk with a software engineer but they kept stonewalling. I think it was fixed after 24 hours or so.