The corollary is that you consume an API that charges you Bitcoin. You don't notice right away, but something goes wrong, and API returns bad or null data for thousands of requests, meanwhile you are still micropaying Bitcoin. You ask for a refund, but the company running the API doesn't respond to your emails.
The threat of chargebacks disciplines the market to provide reasonable customer service.
This is why we'll be using ACs to pay for things. Load up an autonomous corporation with $5, make its job paying for API calls. If something goes South, it's last job is to pay an alert mechanism that triggers a human response.
These models turn existing models on their heads, so be aware of other pitfalls. Productive paranoia is good, but only practice it after you innovate first.
Say you created an API that takes users' data and stores it on S3. Some random user then comes, pays you $10k to store his data, but a week later does a chargeback. You're left to pay the costs to AWS.
Finally, with CCs you need to strike deals with payment processors like Braintree. If you're a private developer it will be impossible. But even as a company - payment processors are not ready to process payments via command line. They will ask you where your terms of service are, what's your website, what's your refund policy and so on.