Ecommerce uptime monitoring for agencies

A generic uptime monitor pings the homepage and sees HTTP 200. That tells you the server answered, not that a customer can buy. Across a portfolio, the failures that actually cost your clients money are the ones that leave the site "up": an app update that covers the buy button on mobile, a theme change that breaks Add to Cart, a script error on the cart page. Real-checkout monitoring runs an actual purchase to the payment step and proves it, store by store. See what checkout monitoring is for the detail.

The developer tools make a portfolio manageable from one place:

rs add https://newclient.com --slack https://hooks.slack.com/services/XXX   # onboard + alerts
rs list                        # every store you monitor
rs status clientstore.com      # one client's tests, latest run and schedule
rs --json runs clientstore.com | jq '.runs[] | select(.status != "passed")'   # failures only

Onboarding a new client becomes a single rs add with the store URL. Pulling the proof for a monthly client report becomes an rs evidence call per run. An AI assistant with the MCP tools can roll a weekly summary across every store for you.

Today these tools authenticate with a single administrative key, so they are run by us or by a single operator on your behalf: a managed setup, not a self-serve product you log into with your own scoped key. Per-agency scoped keys, so an agency can hold the monitoring tier itself and only see its own stores, are a planned next step, not something shipped. If you are an agency and want this wired into your stack, that is exactly the demand that pulls it forward, and the CLI and MCP server are already the foundation it is built on.