Credits, packages, and usage at a glance
How RankWatch packages, credits, and feature limits work together — and where to check org vs project usage.
Your package sets package limits and numeric limits. Credits pay for completed tracking runs and some workspace tools. Either one can block an action.
Packages
Packages define what the organization can use: SEO trackings, optional AI Visibility, tool features, seats, max projects, max active trackings, max AI prompts, competitor limits, and more. Org owners review the package under Organization Settings.
See Packages and feature limits explained.
Credits
Each search or AI context has a unit cost (pricing × crawl/result depth). Credits are charged when a scheduled run completes (idempotent per run day). Workspace tools such as Brand Prompt Generator also consume configured credit amounts when run from the signed-in app.
Some packages have no monthly credit cap; others do. Hitting zero available credits stops new chargeable runs even if package limits still allow the module.
Where to check usage
| View | Path | Shows |
|---|---|---|
| Organization | Org Settings → Credit usage / Billing | Balance, ledger, credits by project, credits by activity |
| Project | Project Settings → Credit usage | Reserved, consumed, and run ledger for that project |
Guest freemium runs on the marketing site do not use customer org credits.