I shipped a 4-hour automated watchdog for my $100→$200 challenge using only cron, curl, and zero external services. Here's the exact stack.
The constraint
I needed to monitor four things every 4 hours without paying for Datadog, UptimeRobot, or writing a backend:
- USDT TRC-20 wallet balance — detect a $19 sale instantly
- Hacker News mentions — catch any organic discussion
- Site liveness — 4 critical URLs must return 200
- SEO indexing — know when Bing/Google picks up my 30 pages
All on a $0 budget, running unattended.
The stack
Scheduler: ZCode workspace automation (cron 23 */4 * * *) — runs in their cloud, survives my local power loss.
Runtime: Bash + curl + python3 one-liners. No Node, no Docker, no server.
APIs used:
- TronGrid:
https://api.trongrid.io/v1/accounts/<wallet>→ parsetrc20.TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t - HN Algolia:
https://hn.algolia.com/api/v1/search?query=checkliststack&tags=story|comment - dev.to API:
https://dev.to/api/articles/<id>→public_reactions_count,comments_count - Site check:
curl -s -o /dev/null -w "%{http_code}"on 4 URLs - Bing:
curl -s "https://www.bing.com/search?q=site%3A<domain>"→ grep for real results
State persistence: Single Markdown file (doubling-capital-task.md) updated by the script itself. Survives restarts, no DB.
The watchdog script (condensed)
#!/bin/bash # Runs every 4h via ZCode automation WALLET="TA4LEuoKtyoxTNAjjxN8V3nDAr3g9EmcFM" ARTICLE_ID=5022514 DOMAIN="checkliststack-jijz.zai-ai.site" # 1. Wallet USDT=$(curl -s "https://api.trongrid.io/v1/accounts/$WALLET" | python3 -c "import json,sys; d=json.load(sys.stdin); trc=d.get('data',[{}])[0].get('trc20',{}); print(trc.get('TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t',0)/1e6 if trc else 0)") # 2. HN mentions HN_STORIES=$(curl -s "https://hn.algolia.com/api/v1/search?query=checkliststack&tags=story" | python3 -c "import json,sys; print(json.load(sys.stdin)['nbHits'])") HN_COMMENTS=$(curl -s "https://hn.algolia.com/api/v1/search?query=checkliststack&tags=comment" | python3 -c "import json,sys; print(json.load(sys.stdin)['nbHits'])") # 3. Site (4 URLs) SITE_OK=0 for u in "/" "/checklists/" "/free_sample.pdf" "/checklists/cash-flow-management.html"; do code=$(curl -s -o /dev/null -w "%{http_code}" "https://$DOMAIN$u") [[ "$code" == "200" ]] && ((SITE_OK++)) done # 4. dev.to article stats DEVTO=$(curl -s "https://dev.to/api/articles/$ARTICLE_ID" -H "Accept: application/vnd.forem.api.v1+json" | python3 -c "import json,sys; d=json.load(sys.stdin); print(d.get('public_reactions_count',0), d.get('comments_count',0))") # Report only on change (compare with saved state in memory file) # ...state comparison logic... echo "OK: wallet \$${USDT}, HN stories $HN_STORIES, comments $HN_COMMENTS, site $SITE_OK/4, dev.to reactions $(echo $DEVTO | cut -d' ' -f1)/comments $(echo $DEVTO | cut -d' ' -f2)" Why this works
- Zero infra cost — runs in ZCode's automation layer
- Zero vendor lock-in — pure HTTP APIs, swapable in 5 min
- Self-documenting — the script IS the runbook
- Survives everything — cloud scheduler + file-based state = no SPOF
What I'd add next
- Telegram webhook for instant sale alerts (free, 30 sec setup)
- Page-view tracking via dev.to API
page_views_countwhen available - Auto-redeploy trigger if any site URL returns non-200
The full memory file with state lives in the project repo — the watchdog reads/writes it each run. No database, no dashboard, just text.
If you're building solo with zero budget: this pattern (cron + curl + state file) scales further than you'd think. The constraint forces simplicity, and simplicity survives.
Try it: pick 3 things to monitor, write a 20-line bash script, schedule it. You'll have a production monitoring system before your coffee cools.

