Usage and Activity

The Usage page combines your credit balance with an attributed activity ledger. It answers both how many credits remain and where each charged action originated.

One pool of credits

Everything metered spends from one monthly pool: a scan costs 50 credits, an AI code review 50 (Pro only), a capability run 10, a posture upload 5 and a capability read 1. The page shows the allowance, what is used, what remains (including any top-up balance, which never expires), the exact rolling reset time, and the cost of each action, so you can see what the month went on. Searching capabilities is free and appears nowhere. See Concepts → Credits and Aevrin MCP limits.

Below the balance, activity counts per surface (CLI scans, dashboard scans, capability runs, code reviews) show where the credits went. They are history, not separate limits: the pool is the only cap.

Activity ledger

The latest 50 charged scans show source, target, target type, request time, final status, score, and a link to the same full report used by History. Use source filters to isolate automation or developer activity. The ledger covers scans only: capability reads and runs move the credit balance but have no ledger entry.

History retention

Scan history is not pruned automatically on any plan. History supports individual deletion and Clear history. Deleting a scan removes its stages and findings from the dashboard; credits already spent are not refunded.