EXPERIMENT·PERSONAL BUILD·JUL 2026
SOXL market-monitoring agent
A scheduled AI agent that monitors a leveraged semiconductor ETF and delivers structured market updates through Telegram and WhatsApp.
Overview
This experiment tests whether a lightweight, scheduled agent can reduce the effort required to monitor a volatile investment position.
Rather than repeatedly checking charts, headlines, and market indicators throughout the day, I built an agent that runs automatically, evaluates the latest SOXL market context, and delivers a concise update through Telegram and WhatsApp.
The objective was not to create an autonomous trading system. It was to explore how scheduled AI workflows could turn fragmented market information into a consistent, reviewable decision-support experience.
The problem
SOXL is a leveraged ETF, which means its price can move quickly and amplify both gains and losses.
Monitoring it manually requires repeatedly checking several pieces of information:
- Current price movement
- Recent momentum
- Broader semiconductor performance
- Relevant market context
- Whether anything meaningful has changed since the previous check
Most consumer investing tools provide either raw market data or generic price alerts. They rarely explain why a movement may matter or summarize the information in a format that supports a decision.
I wanted to test whether an agent could bridge that gap without presenting itself as a financial adviser or automatically executing a trade.
Approach
I designed the system around three principles:
Scheduled, not reactive
The agent runs through a recurring cron job rather than depending on me to remember to check the market.
Structured, not predictive
The output organizes market signals and changes in context. It does not claim to predict SOXL's next movement with certainty.
Delivered where I already communicate
Instead of creating another dashboard, I used Telegram and WhatsApp as the product interface.
This kept the experience lightweight: the infrastructure runs in the background, while the output arrives as a familiar message.
What I built
A scheduled market-monitoring workflow that gathers current SOXL context, processes it through a defined analysis framework, and sends the resulting update to two messaging channels.
The four steps below show how the system moves from a protected cron trigger through structured market input, brief generation, and multi-channel delivery.
Manual monitoring
- Price chart
- Sector ETF
- News headlines
- Prior notes
- Messaging apps
Agent update
Telegram
SOXL Market Check
One structured brief with movement, context, and what changed since the last run.
System architecture
Cron triggers a protected endpoint. Market data is retrieved server-side, interpreted by the model, then delivered through messaging APIs.
Scheduled checks (sample day)
9:30 AM
Market open check
12:00 PM
Midday context
4:00 PM
Close summary
Trigger the market check
A Vercel cron job triggers the agent on a defined schedule. The endpoint is protected with a server-side cron secret.
Vercel Cron
Scheduled run
Protected API
CRON_SECRET validation
SOXL monitoring agent
Server-side execution
Sample prototype data, not live market values.
Gather and structure the context
Market signals are collected and normalized before any AI interpretation.
Market input pipeline
Data freshness · 2 min agoSOXL price
$42.18
Sample · Jul 21, 2026
Daily movement
+2.4%
Since prior close
Recent trend
3-day uptrend
Momentum context
Semiconductor context
SOXX +1.1%
Sector benchmark
Relevant headline
Chip demand outlook
News signal
Previous observation
Range-bound
Last agent run
Generate the market brief
Structured inputs become a concise update with a clear boundary between facts, interpretation, and user judgment.
Structured layers
- SOXL +2.4% today
- SOXX outperforming
- Volume above 10-day avg
- Momentum remains positive but leverage amplifies downside
- No material change vs prior observation
- Review only, no trade executed
- Agent does not advise or trade
Agent output preview
SOXL Market Check
- Current movement
- What changed
- Market context
- Risk considerations
- What to watch next
Supports judgment. Does not execute trades or provide definitive financial advice.
Deliver through messaging channels
The same analysis is routed to Telegram and WhatsApp with delivery status visible in the workflow.
Telegram
SOXL Market Check
Movement: +2.4% today. Context: semis firm, leverage risk unchanged. Watch: afternoon volume and SOXX relative strength.
Sample brief · review only
SOXL Market Check
Movement: +2.4% today. Context: semis firm, leverage risk unchanged. Watch: afternoon volume and SOXX relative strength.
Sample brief · review only
One analysis payload routed to Telegram and Twilio WhatsApp. No dedicated dashboard required.
What I learned
The highest-value part of the system was not the AI-generated opinion. It was the orchestration around it:
- Running consistently
- Gathering the same inputs each time
- Applying a repeatable analysis structure
- Delivering the result without requiring another app
- Making failures visible when data or messaging services were unavailable
I also learned that scheduled agents behave more like small production systems than isolated AI prompts.
Authentication, environment variables, cron configuration, messaging limits, error handling, and deployment state were as important as the model response itself.
Run reliability states
Scheduled agents need visible success, skip, failure, and retry states, not just a model response.
Key takeaway
Key takeaway
An agent becomes more useful when it owns the repetition of monitoring—not the final decision.
What's next
Add persistent storage so the agent can compare each update against prior observations rather than evaluating every run independently.
I would also explore:
- Threshold-based alerts for unusually large movements
- Separate morning, intraday, and end-of-day summaries
- A lightweight history of previous agent outputs
- Delivery-status monitoring across Telegram and WhatsApp
- Clearer confidence and data-freshness indicators
- User-configurable watchlists beyond SOXL
- Rules for suppressing messages when nothing meaningful has changed
The next product question is whether the agent should continue delivering every scheduled update or only interrupt the user when a material change occurs.
Tech stack
- NNext.js
- TTypeScript
- VVercel
- VVercel Cron
- OOpenAI
- TTelegram Bot API
- TTwilio WhatsApp
- MMarket data API
More from the Playground
Experiment
Building my portfolio like a product
Designed, built, and shipped a personal portfolio using AI-assisted development—not as a static collection of work, but as a living product system.
Prototype
Calmo Cafe — a reservation flow that skips the early SaaS bill
I built a branded site and request-to-confirm booking flow for a friend opening a café in Toronto, both to keep him off OpenTable fees before the room was proven and to learn a real stack end to end.