Part of making an API publicly consumable is an informal commitment to maintain it. Most major API changes are announced far in advance, and legacy versions are

Part of making an API publicly consumable is an informal commitment to maintain it. Most major API changes are announced far in advance, and legacy versions are maintained to give developers the chance to switch. A company whose core value depends on consuming that API will likely be informed about future changes; I'd think it's the least of their worries.