Your argument would be valid, but the scenarios you cite are totally orthogonal. Here's why:
1) You don't pay Facebook for their API. If something isn't working, you can't question anyone, nor are they liable to answer you. In short, they are doing you a favor by letting you use their API free of cost.
2) A credit card processor like Visa/Mastercard takes your money, and returns you a service instead. IF something isn't working as it should, you can call them and ask them what's wrong and they are liable to answer you, you can even request a refund, failing to provide which you could possibly drag them to a court, which isn't the case with an free API provider like Facebook/Twitter.
3) When you integrate the Facebook platform as an additional feature to your site, it's totally fine as long as it doesn't affect the core business model, because even if something gets screwed, users will not worry about a tiny missing feature. But when you build a business on top of someone else's API, be it Twitter or Facebook, it's like building a sand castle at the scale of a real world house and expecting it to be there forever. That's how vulnerable your business model becomes, because there is SO much that you have no control over. In the case of a credit card processor, they don't control your business model, they just do you a service in exchange for money, which is totally different, and you can change providers at a later stage if you find them unsatisfactory, which isn't the case with building something on top of an API like that of Facebook's/Twitter's.