Somewhere around your third automation script, you'll get hit with a bill you didn't expect. That's usually the moment it clicks: your $20/month subscription and your API key were never billed the same way.
I wrote up a full breakdown on this for Devlycan, but here's the short version for anyone building with AI:
- A product subscription and API access are billed separately — paying for a plan doesn't grant you free API credit.
- Subscriptions still carry usage limits. "Unlimited" rarely means unlimited.
- API accounts have their own rate limits too — paying per token isn't paying for unlimited throughput.
- Prompt caching and batch processing can meaningfully cut API costs, but only show up if you're calling the API directly.
- A lot of coding agents today let you draw from your subscription's usage pool OR bill against the API for the same tool — it's not always two separate products.
My rule of thumb: subscriptions for direct, everyday work with AI. Pay-as-you-go for anything that needs to run inside a system you're building. If you do both, running them side by side is usually the most practical setup.
The article is available in both English and Thai.
Devlycan - Technology & Programming Insights
Devlycan - Technology, programming, AI, lifestyle, and future trends—simple insights for the new digital generation.
devlycan.com
Top comments (1)
This is the right split. I would add one more line item to the mental budget: variance. Subscription pricing buys a ceiling for human-paced work. API pricing buys automation, but it also moves the risk into every loop, retry, and forgotten cron job. The mean cost matters less than the surprise tail.