Granting anonymous access would be a matter of organization precedent, but I can imagine a world where it's encouraged to dev against these services and notify upstream service owners when stuff is about to change reasonably ahead of time (too soon and too many chefs might come, unfortunate reality).
I think every service owner should know who their 'customers' are, it's important because of things like Pager Duty rotations for example. Remember that scene from Hackers, "God wouldn't be on this late?"... in a sense, the 6 page form might seem like overkill but it beats sifting through a conversational email thread asking for all the same pieces of information. They could gamify the form I suppose, if that's better than a paper form... but on their end there should be a spreadsheet used for op budgeting etc and they need the info.
I think every service owner should know who their 'customers' are, it's important because of things like Pager Duty rotations for example. Remember that scene from Hackers, "God wouldn't be on this late?"... in a sense, the 6 page form might seem like overkill but it beats sifting through a conversational email thread asking for all the same pieces of information. They could gamify the form I suppose, if that's better than a paper form... but on their end there should be a spreadsheet used for op budgeting etc and they need the info.