2026-05-05 — Usage-Based Credits Replace Search Counts
Counting searches was always a blunt instrument. A quick definition lookup and a deep multi-step research question are not the same amount of work, but a request counter charged them as if they were. So we stopped counting requests and started accounting for what a search actually costs. Usage now runs on a credit wallet — the full picture lives on the pricing page.
Highlights
- Usage measured in credits tied to the real cost of each search
- A visible balance instead of an opaque request count
- Plan credits and top-up credits in one wallet
- Manual top-up available from Settings
A wallet, not a counter
Your account has a balance of credits. A search draws down credits based on what it genuinely took to answer — not a flat tick on a counter that treated every query the same. Cheap questions cost little; heavy ones cost more, which is how it should have worked all along.
Two kinds of credit, one balance
Plan credits come with a subscription and refresh each cycle; top-up credits are the ones you add yourself and don't expire on a monthly clock. Plan credits are spent first, then top-ups, automatically — you don't manage the order.
Top up when you need to
Settings now has a manual top-up flow, so if you're running low you can add credits directly instead of waiting for a cycle to reset.
Why This Matters
Tying usage to actual cost is simply more honest. You're not penalized for asking small questions, and you can see exactly where your balance stands instead of guessing how many "requests" you have left in a hidden bucket.
What this means for you: a balance you can see, charges that reflect the real weight of what you asked, and a top-up button for the moments you need more.