Multiple domains using TLDs as workaround for no global keys in reCAPTCHA v2

My client has a hosted CMS serving >250 clients from a single codebase. We were successfully using reCAPTCHA v1 with a global key, but want to use v2 now, and of course that does not support global keys. Needless to say, I don't want to have to create >250 different API keys. It's not just creating the keys either, of course; I'd need to create a mechanism for storing on a per-site basis, and add the generated keys to each site :-( However, what seems to work, based on preliminary testing, is adding TLDs as the domains. So I've got the following domains listed for my key: "com, net, org, co.uk, org.uk, net.uk …". That said, I'm wary of suggesting this as a workaround, because I'm sure this is not what Google had in mind. Presumably they disallowed global keys for a reason. I hoped that this post might catch the attention of a Google reCAPTCHA team member, who could tell us if this is Very Definitely A Bad Thing, and unsupported behaviour that Google might suddenly break. Thoughts? (I would be happy with the sensible suggestion of an API to manage reCAPTCHA keys, but I assume that's not going to happen immediately!) Thanks in advance, James -- You received this message because you are subscribed to the Google Groups "reCAPTCHA" group. To unsubscribe from this group and stop receiving emails from it, send an email to recaptcha+unsubscribe@googlegroups.com. To post to this group, send email to recaptcha@googlegroups.com. Visit this group at http://bit.ly/1dkFnYd. For more options, visit http://bit.ly/P65DvS.