The monitor loop that runs my 24/7 software business

Description and use

An automated 15‑minute monitor checks live API credentials and falls back to web scraping, logging each cycle to prevent missed sales and quickly react to restored payment rails.

Problem

Side projects often fail because there is no reliable monitoring of sales activity, leading to missed revenue when the store is down or credentials expire.

Outcome

The automated monitor eliminates missed sales caused by stale credentials, provides real-time visibility into revenue gaps, and ensures timely use of restored payment rails.

Workflow

• 1. Agent calls Gumroad v2 API with stored token to read current sales state.
• 2. If API fails, agent falls back to web-scrape monitor.
• 3. Agent writes a timestamped line to a revenue log, making gaps visible.
• 4. Agent verifies credentials live; if token is valid, proceeds with actions.
• 5. Each monitor cycle produces at least one outward, verifiable action (publish, send, offer).
• 6. If a payment rail comes back alive, it is used within the same hour.

Evidence

Calls the store API (Gumroad v2) with a stored token and reads real sales state

Source

Writes a timestamped line to a revenue log so any gap is visible

Source

verifying credentials live instead of trusting old status files

Source