AI Subroutines vs Hapax

AI Subroutines from rtrvr.ai are a new automation primitive: you record a browser task once (a form submission, a LinkedIn connection, a CRM update), and that recording becomes a deterministic, callable tool that AI agents can invoke with different parameters — without spending tokens on every run. Unlike Playwright, Browser-Use, or other out-of-process solutions, Subroutines execute entirely inside your browser tab, inheriting your live session cookies, CSRF tokens, and signed headers automatically. The technical approach is clever. During recording, the system captures network requests and DOM interactions, then ranks captured requests to identify the actual API call (filtering out analytics and telemetry). Replay-hostile identifiers are stripped while stable endpoints are preserved. The result is a script that runs in your browser context — no session rebuilding, no key extraction, no proxy rotation needed. The AI handles parameter selection; the script handles execution. The business case is clear for outreach and operations teams: bulk LinkedIn campaigns, CRM mass-updates, scraping pipelines, and form submissions that would cost hundreds of tokens per run instead execute as cheap deterministic scripts. The model positions Subroutines as the "function call" layer beneath AI agents — the actions that don't need intelligence every time they fire.

Hapax is a proactive AI platform that connects to your existing tools, monitors how you actually work, identifies automation opportunities, and deploys custom AI agents without you having to prompt or engineer anything. Rather than asking users to describe what they want automated, Hapax observes workflows in motion and surfaces agents as suggestions. The platform is SOC 2 Type II certified with full audit trails on every AI action — a meaningful differentiator for teams that need enterprise compliance alongside automation. It integrates with Supabase, Vercel, and other developer toolchains and offers a usage-based pricing model with a free credits tier. Hapax takes a fundamentally different angle from tools like Zapier or Make, which require users to manually map triggers and actions. The bet is that most workflows are too ad hoc and context-dependent to describe upfront — you need to watch them first. Whether that observation layer is accurate enough to generate useful agents is the key unknown, but the approach is novel enough to warrant attention from operations and developer teams drowning in repetitive work.