Start with the rule, then decide where AI helps
A product crossing below your budget, an availability label becoming available, or a page containing a phrase can be explained by ordinary rules. Those checks do not need AI Credits. Use AI where a short explanation or a second relevance decision adds useful context.
For a public policy page, you might keep an ordinary text-change rule, request a summary when a change looks substantial, then test a relevance criterion before choosing automatic filtering. Review the retained capture alongside any AI interpretation.
Budget for matching changes, not every scheduled check
Automatic summaries and relevance run after eligible changes match, not on every unchanged page check. A frequently checked page can use little AI if it rarely changes. A noisy page can use more even at a slower interval.
| Activity | Quantity | Credits |
|---|---|---|
| Completed change summaries | 40 × 1 | 40 |
| Completed relevance evaluations | 60 × 2 | 120 |
| Flux AI answers | 30 × 2 | 60 |
| Usable AI setup suggestions | 6 × 5 | 30 |
| Total | A mixture of AI help | 250 |
This example uses 250 credits. It is a planning example, not a forecast or a guarantee that a site will change at a particular rate. A change that receives both relevance and a summary can use 3 credits. Inspect a week of real activity before scaling up.
Set a practical budget and review it
Open the right workspace
AI Credits are shared within one workspace. Personal and team balances are separate.
Check the cost and remaining balance
Use the AI Credits page to compare included credits, purchased reserve and work in progress.
Choose an optional monthly budget
Owners can set workspace and per-member daily/monthly limits. Blank adds no owner-set cap; zero pauses new requests in that category.
Review successful and attempted work
Completed work consumes credits. Failures release credits, while user and service protections still count attempts.
Make the capture more useful before buying more
Select the paragraph or listing region you care about, test your ordinary rules, and review the first results. Relevance is not a substitute for a focused capture. A whole-page watch that includes changing navigation can generate unnecessary evaluations.
When you reach a budget, normal alerts continue. You can turn off automatic summaries while still requesting them on demand, revise criteria, raise your own budget, add a fixed credit pack or upgrade for a larger monthly allowance. A refill cannot override a workspace cap or service protection.
Choose included capacity or a one-time reserve
An upgrade fits a sustained need for more monitoring and AI capacity. A one-time credit pack fits an occasional burst of AI usage when your existing monitoring plan already works. Packs are available in 1,000-credit and 5,000-credit amounts, with quantities from 1 to 10; the purchase screen shows the exact amount and subtotal before checkout.
If checkout is interrupted, use Resume checkout in Credit purchases. Cancel the unfinished checkout before choosing a different pack; a payment already processing cannot be cancelled there.
Purchased credits are used after included credits and carry forward. They stay with the workspace after a downgrade, but do not unlock features reserved for another plan. Read the full credit guide before enabling automatic AI across a larger watch list.
Common questions
Do unchanged checks use AI Credits?
No. Ordinary checks have their own monitoring allowances. Automatic AI is considered only for eligible matching changes with consent.
Will I miss alerts if AI credits run out?
Normal alerts continue within their usual delivery and plan limits. A relevance evaluation that cannot run allows normal delivery rather than suppressing the alert.
Can I buy more AI without changing plans?
Yes. When paid billing is open, the workspace owner can buy a fixed number of additional credits as a one-time purchase. Feature access remains tied to the workspace plan.