Context.dev Credit Burn Audit and Monitor Pruning (Retention)

Context.dev Credit Burn Audit and Monitor Pruning (Retention)

1. 01

   Pull the current billing period usage from the Context.dev dashboard and record credits consumed against the plan allowance.

   Compare the figure to the plan ceiling: Free Tier caps at 1,000 credits per month with no overage, Pro at 125,000, Growth at 500,000. A client on Pro who has burned 118,000 credits by day 20 is on pace to breach the allowance before renewal.

2. 02

   Break the consumption down by endpoint: scrape, crawl, batch, Answers, and brand profiles.

   Answers is the usual culprit. Pro includes 12,500 Answers in Fast mode, and a research tool that fires an Answers call per user question will drain that allocation long before the scrape volume looks unusual.

3. 03

   List every active monitor and match each one to a client deliverable that someone actually reads.

   The Free Tier allows 10 monitors, Pro allows 1,000, Growth more still. Monitors that push to a webhook nobody consumes still consume credits on every detected change, so an agency running 400 monitors for a client who reads a weekly digest is paying for 390 of them.

4. 04

   Check the concurrency setting against the plan ceiling and the client's real traffic pattern.

   Free Tier permits 1 concurrent request, Pro 100, Growth 250. An agency that left a batch job running at Growth-level concurrency on a Pro plan will see requests queue or fail, and the retry logic built into Context.dev will re-spend credits on the same pages.

5. 05

   Confirm spend controls are switched on for every client workspace before the next billing cycle opens.

   Spend controls ship with the Pro plan. Without them, an agency absorbing overage on a fixed retainer has no automatic stop, and the margin on a $2,500 Starter Scrape Build disappears in a single runaway crawl.

6. 06

   Prune the monitor list and re-point surviving monitors at the pages that drive the client's weekly report.

   Delete monitors on pages that have not changed in 90 days, and consolidate duplicate monitors watching the same competitor pricing page from two different client workspaces.

7. 07

   Send the client a one-page credit summary with the pruned monitor count and the projected next-cycle spend.

   State the plan, the allowance, the credits used, and the number of monitors retained. This turns a cost conversation into a delivery conversation and gives the agency a documented reason to move the client from Pro to Growth when volume genuinely justifies it.