Picking an API

Thousands exist. Here’s how to choose without overthinking.

For any capability you want (weather, email, payments, AI) there are usually several competing APIs and no objectively right answer. Different pricing, different data, different quirks. The goal isn't the perfect choice; it's a working choice you can swap later. And you can: switching providers after the fact is usually an afternoon, not a rewrite.

Fastest route: ask the agent. “Is there a free API for [the thing]?” It's effectively read the docs for all of them, so it'll tell you what exists, what's free, and then just set it up.

Want to scout yourself? Every serious provider publishes developer docs, usually at an address like docs.stripe.com or developer.spotify.com. Don't read them like a textbook; skim for two answers: what can it do, and is there a free tier.

The three-point checklist before committing:

• –Free tier. Nearly every API has one, and for a personal project it's nearly always enough.
• –Rate limits. How many requests per day before they cut you off? Side projects fit comfortably in even stingy limits.
• –Setup complexity. Some APIs are one line of code; others want webhooks and OAuth ceremonies. When two options are equal, take the boring one.

Still stuck? Describe what you're building and let the agent pick. Analysis paralysis costs more than a wrong first pick that takes an afternoon to swap.

AI Clubhouse · Vibe Coding Guide