Alpha Vantage limits and the Japanese stock gap

When I first went to wire up a stock data feed, Alpha Vantage looked like the obvious default: it's free, it's a real API, and it covers a huge swath of assets. So I wrote my pipeline against it — and then discovered two things that changed how I think about any free financial data feed. First, the free tier is rate-limited so tightly (I measured roughly 5 requests per minute) that any loop needs a sleep between calls. Second, and bigger for me: it doesn't cover Japanese stocks at all, which is the market I actually needed. Checked and confirmed in my own setup.

The free tier is a scheduling constraint, not a firehose

The headline "free" hides a real operational constraint. On the free tier I observed roughly 5 requests per minute, which is fine if your job makes a handful of calls. But if you write a loop that iterates over a list of tickers without throttling, you'll blow through the limit in the first few seconds and spend the rest of the run backing off.

My fix was boring and effective: a sleep between requests. I pace the loop to stay under the observed rate, and I treat the limit as part of the contract I'm designing against rather than a surprise. This is the same discipline I apply to any upstream that isn't mine to hammer — throttle, back off, and make the job idempotent so a partial run can resume cleanly.

What Alpha Vantage does cover well

To be fair, the coverage where it exists is broad. The API handles US and other global stocks, forex, crypto, commodities, and economic indicators. If your universe is US equities, a free-tier Alpha Vantage feed with a throttled loop is a perfectly reasonable place to start a research pipeline. The rate limit is manageable when your request volume is small.

That's exactly why the gap stung: the tool is good at the things it does, and the missing piece is precisely the market I needed. For Japanese equity data, Alpha Vantage simply wasn't the answer, and no amount of throttling fixes a coverage hole.

The Japanese stock gap

The hard lesson wasn't about rate limits — it was about coverage. Japanese stocks aren't on the free global feed, and that's a category problem rather than a config problem. You can't sleep your way to data the API doesn't have.

So for Japanese tickers I use a Japan-specific source instead, one that covers daily OHLCV going back years plus valuation and dividend data. Different endpoint, different rate budget, same throttling discipline. The point is that the two feeds serve different asset classes, and choosing between them is a coverage decision first and a pricing decision second.

The decision rule I now run with

Before I build any pipeline on a free financial feed, I check three things in order. Coverage: does it actually serve my market and asset class? Rate limits: can the free tier sustain my request volume once throttled, or will I be waiting all day? Officialness: is there an official source for this data that's more reliable and documented? Alpha Vantage fails me on the first question for Japan, which is enough to disqualify it for that job no matter how good the rest is — the same reasoning I applied when I replaced scraping with proper Japanese data feeds.

The rule generalizes beyond stocks. Any free API with a tight free tier and partial coverage is a candidate for the "check before you build" list. Read the limits, confirm the coverage actually includes your universe, and only then write the pipeline.

What's your go-to when a free API covers most of the world but not the one market you actually trade — do you tolerate the gap or switch sources entirely?

Originally published at agentjournal.dev.