Skip to main content
A monitor runs the same OpenRush tools on a schedule and saves each result, so you can see what improved, what slipped, and what to do next. After you set one up, OpenRush:
  • runs the check on its servers, so your laptop can be off,
  • saves the results, and
  • works out what changed since the last check.
Your agent reads the changes, explains them, and sends a summary where you want it.

​
Start a monitor

From the dashboard:
  1. Go to Monitoring and click Monitor.
  2. Pick your site and what to monitor.
  3. Copy the prompt into your agent.
Your agent suggests anything the monitor needs, like keywords or competitors, tells you the cost, and creates it once you agree. From your agent:
Use OpenRush to monitor example.com and my three main competitors every week.
Monitor my rankings for “crm software”, “sales pipeline tool”, and “crm for startups”.
Monitor example.com’s AI visibility against rival.com and other.com.
When you look at the same site more than once, your agent may offer to monitor it.

​
What you can monitor

See Credits for tool prices.
For your own site, Search Console is the best view of your rankings. It shows Google’s measured positions for your real search terms.Search Console and Website analytics are separate monitors, so you only set up the ones your site has connected. A site with both can have both. Asking for one whose product isn’t connected creates nothing and says where to connect it.

​
Fair comparisons

A monitor is one exact question, so each check compares fairly with the last.
  • Settings stay fixed. You can rename a monitor or change how often it runs, but not what it checks.
  • A new question is a new monitor. To track other keywords, create another monitor. Pause the old one to keep its history readable.
  • No duplicates. Asking for a monitor that already exists returns it, with no charge. If a new monitor overlaps with another, your agent is told, so it can check with you.
  • Complete days only. Search Console, Website analytics, and Ads leave out days Google is still reporting, so part of a week is never compared with a whole one.
  • Same targets. Site health audits the same pages, and AI visibility keeps the same competitors. A keyword that wasn’t checked shows as not checked, never as lost.

​
Read your history

Ask your agent:
What changed in my OpenRush monitors this week, and what should I do about it?
Show me how /pricing has moved over the last 3 months.
Every Monday, check my OpenRush monitors and send a short summary to Slack.
Reading history is free. It builds whether or not anyone reads it, so you can always ask what happened weeks ago. Asking the same question again in a normal tool call also shows what moved, when the settings match. If a monitor already covers it, your agent is pointed to its history.

​
Credits

A check costs the normal price of each tool it runs. There’s no extra fee for monitoring, and reading history is free.
  • No surprise charges. OpenRush never charges into a negative balance. If your balance can’t cover the next check, the monitor pauses.
  • Your history is safe. A pause never deletes anything. Monitors paused for low credits resume by themselves once you add credits.
  • Failed requests are refunded. After 3 failed checks in a row, a monitor pauses. Run it again to restart it.
To keep monitors running, turn on auto top-up in Billing. Only account admins see auto top-up prompts. The dashboard shows each monitor’s state and your weekly monitor spend.

​
Teams

  • Monitors belong to the account. Every member can see, create, edit, pause, and delete them.
  • Each monitor shows who created it: a member, or the API key’s name.
  • Check credits count toward the creator in per-member usage.
  • Each monitor’s page shows who created, changed, paused, or deleted it.

​
Google data and your privacy

The first time a monitor uses your own Google data (Search Console, Analytics, or Ads), a signed-in member accepts a one-time consent for the account. Storing a history of that data is a separate use, so we ask first. If your agent creates the monitor, it shows you a consent link. Other steps run right away. Google steps start at the next check after you accept. Google-derived history is used only for your account’s own features, never across accounts.

​
For developers

Monitors use four tools, over the API and MCP. See Monitor tools for fields and examples. Monitor checks show in your usage with the channel monitor. Changes reach your agent in the envelope’s deltas field as <domain>.delta facts. See Deltas.