- What I scheduled: At 4:15 pm EST (right after market close), my script pulls my stock/ETF positions from two Schwab accounts via Schwab's API. Because Schwab's positions already include the field currentDayProfitLossPercentage, it is easy to return the top 5 daily % gainers and bottom 5 daily % losers. Via Perplexity's API, these 10 tickers are reported along with a brief summary per the Perplexity prompt: "In 2-3 concise sentences, explain the likely reason {symbol} stock is up/down about {abs(pct_change):.2f}% today. Focus on recent news, earnings, analyst actions, or sector trends if relevant. Be specific and brief." - What surprised me about how the agent ran without your input? This is a deterministic workflow: Fetch positions via Schwab API; Sort by currentDayProfitLossPercentage; call Perplexity with fixed prompt; dump to .md file. Attached is today's report. Except that the option positions confused Perplexity, it totally works. The ultimate version of this report will be really helpful to me. I don't spend all day every day looking at my portfolio. Like many "part time investors" that means this happens a lot a lot: among the daily trash heap of noise, you miss big news that moves your stocks. This report almost captures something I do manually on many (but not all) days: sort daily % moves, if only to cull out the news I might want to know. It's really exciting to believe that with APIs, Claude can build almost anything that I can imagine. Just like the website build assignment, Claude basically did everything on its own. We got stuck on Schwab's sandbox restriction, but Claude just told me what to do in python from the terminal. So, unlike all my previous coding experiences, I never felt actually stuck. As a *mediocre* coder sincerely, the difference between getting frustrated when stuck versus feeling like you won't really get stuck is such a big difference. That's the (artificial?) confidence that enables the feeling that "hmmmm ... I could maybe build anything I want!".