Typically, api is charged based on usage, which means you use the api first, then you pay. It’s likely that some users sign up, use the api, and never pay, e.g

Typically, api is charged based on usage, which means you use the api first, then you pay. It’s likely that some users sign up, use the api, and never pay, e.g., use a debit card with low balance. Turn the table. If you were running such an api, what would you do to avoid situations like this? I operate a podcast api business [1]. Initially we allowed anyone to sign up. Then we got tons of malicious users who abused the api and never paid us. Then we have to manually review every signups. [1] https://www.listennotes.com/blog/how-i-accidentally-built-a-podcast-api-business-46/ https://www.listennotes.com/blog/how-i-accidentally-built-a-...