Skip to main contentGuppy is designed for tasks that are conditional, stateful, and failure-prone. If a task involves a high cost of getting it wrong (money, scarcity, reputation), it’s a perfect fit for Guppy.
Canonical Categories
1. E-commerce Purchases
Automate retail purchases, especially for limited inventory or price-sensitive items.
- Includes: BestBuy, Target, Shopify stores, and limited drops.
- Why Guppy: Handles inventory flickers, price changes, queues, and shipping constraints.
2. Reservations
Manage bookings for restaurants, spas, or co-working spaces.
- Includes: OpenTable, Resy, and niche booking platforms.
- Why Guppy: Watches for cancellations and manages time-window availability.
3. Travel Bookings
Complex pricing and availability rules for flights, hotels, and car rentals.
- Why Guppy: Handles seat/fare class availability and 24-hour cancellation policies.
4. Ticketing & Events
Extreme time pressure and adversarial commerce environments.
- Includes: Concerts, sports, and conferences.
- Why Guppy: Navigates queues, captchas, and per-user limits.
5. SMB Procurement & Replenishment
Automated office supplies or raw material reordering.
- Why Guppy: Supports Net-terms, invoice workflows, and prevents double orders.
6. Administrative & Appointments
Booking DMV slots, passport appointments, or campground reservations.
- Why Guppy: Navigates ancient UIs, lotteries, and timed releases.
What Guppy Does NOT Handle
To maintain focus and reliability, Guppy is not currently designed for:
- Negotiated Transactions: Enterprise sales or dynamic bargaining where there is no clear terminal condition.
- Subjective Content: Writing, design, or decisions without a binary success state.
- Autonomous Financial Trading: Stocks or derivatives (due to regulatory and market complexity).
Guppy executes any real-world action that can be expressed as:
“When X becomes true, do Y safely.”
It reduces complex workflows into:
- Watch
- Wait
- Execute
- Recover
- Prove
