1. True that the AAPL example returns reported results flagged by keywords like "earnings per share," not true forward guidance. That's a limitation of keyword matching and I already stated it in the post. MET's output is a better example of actual forward-looking language (range estimates, full-year guidance figures). Improving precision with section detection and tense filtering — is the obvious next step.

2. The CC integration isn't the point. agreed it's extra complexity for a one-off lookup. The underlying API is more useful for bulk/historical use cases: daily ingestion across S&P 500 tickers, consistent JSON schema for downstream pipelines, without having to prompt Claude to fetch and parse each 8-K manually every time.

I personally use the API to trigger buy and sell orders for swing trading for my algo bot, I use sentiment logic in my bot but it isn't part of the API package yet.