API-First or API-Dependent.

Every modern system leans on APIs it doesn't own. The question isn't whether to use them — it's whether the architecture survives when one of them changes its terms, its prices, or its mind.

API-dependent means the business logic assumes a specific vendor and can't function without it. Pull that vendor and the whole thing collapses. API-first means the vendor sits behind an interface you control, swappable when the terms turn hostile.

The difference is an abstraction layer — a thin boundary between what the system needs and which vendor happens to provide it this quarter. It costs a little to build and buys sovereignty over the stack.

You don't have to own the whole supply chain. You do have to own the seams — the points where a vendor could otherwise own you.

This is defensive architecture for a solo operator who can't absorb a surprise 10x price hike or a deprecated endpoint. Every external dependency gets wrapped, so replacing it is a config change, not a rewrite.

Convenience today, captivity tomorrow — that's the trade the platforms are selling. API-first is how you take the convenience without signing the captivity. There's a difference between using an API and being controlled by one.