That would be an optimal solution in the current environment; essentially, it pushes the interaction with individual weather data consumers all the way back onto the original data provider (which kind of makes sense). I'm not sure how weather service providers are identifying individual API users right now, but if it's something like a parameter sent in with each request, that should be pretty easy to manage...