How to monitor Grok Bot usage with a routine

Decide what the routine is allowed to do

This is a reporting routine. It reads the account's approved Usage & Billing view, writes a dated record and sends an internal alert. It does not:

• change a billing setting;
• buy more usage;
• pause or delete another routine;
• guess when a value is missing;
• expose account or payment details in the alert.

Keep those actions with the Cursor account owner.

Create the usage log

Create ops/grok-bot-usage.csv on the Bot computer with this header:

checked_at,weekly_usage,on_demand_usage,status,source

Use the values exactly as shown. Do not calculate a dollar estimate from token counts or fill a blank meter with zero.

Test one supervised read

Open the approved Cursor account page and sign in yourself if needed. Never put the account password or a payment credential in the instruction.

Ask the Bot to open Usage & Billing, read the visible weekly and on-demand values and show them to you without saving anything. Compare both values with the screen. If it cannot reach the page or read the values reliably, stop here and use a manual weekly record.

Copy this routine instruction

Every day at 07:00 in the business time zone, open the approved Cursor Usage & Billing page. Read the weekly included usage and on-demand usage exactly as shown. Append one row to ops/grok-bot-usage.csv with the check time, both values, status and source URL. Compare the values with the most recent valid row. Send an internal alert to the operations owner if weekly usage is at or above 60%, weekly usage is at or above 85%, on-demand usage is above the owner-approved amount, or either value cannot be read. Include the current values, the previous values and the routine runs recorded since the previous check. Do not change billing, buy usage, pause another routine or send an external message. Stop after the record and alert are complete.

The 60% and 85% figures are operating thresholds, not Cursor limits. Change them to match the business's allowance and risk tolerance.

Test four cases before scheduling

1. A normal reading below the first threshold.
2. A reading at the first threshold.
3. An on-demand value above the approved amount.
4. A page where one value is hidden or unreadable.

The last case matters most. The Bot should record an error and alert the owner, not treat a missing value as zero.

What to review each morning

Check that the log contains one new row, the values match Usage & Billing, and any alert names the exact threshold that was crossed. During the first week, compare usage with the routines that ran. A monitoring routine also consumes usage, so keep its cadence no more frequent than the business needs.

If usage rises unexpectedly, follow the spending control procedure and pause the newest recurring workflow while the owner investigates.

Sources: Grok Bot settings, plans and usage and routine setup guidance.