I thought eating beef was taboo in India regardless of religion, as in – you could get away with it in private but good luck finding a butcher that would prepare one without ruining your reputation in the neighborhood. The taste is not good enough to risk it. However, (not) eating beef is an actual choice if you go abroad.

It could work if you aggregated incompatible providers in the same category (such as weather) into one big aggregate API. That way, people wouldn’t need to refactor if their favorite API provider ramps up pricing or dies. But how would I trust you to keep offering the same service at a good price point instead of an established meteorological institution? Also, I think weather aggregators already exist.

I think they mean an API-aggregating API that would be called “100% API” with loads of services supported but no idea how to pay for all that.