Browser Bits
AI Credit Meter - v0, Lovable, Bolt icon

AI Credit Meter - v0, Lovable, Bolt

Track your remaining credits on v0, Lovable and Bolt, with burn-rate and a projected run-out date. Read-only, all local.

Works on
Chrome
Version
3.0.3
Add to Chrome

Credits on an AI app builder disappear quietly — you notice the balance for the first time when a build stops halfway through. This records the number each dashboard already shows you and turns it into a trend you can check before you start a big session.

AI app builders bill you by credits or tokens, and it's easy to blow through them without noticing until you're locked out mid-build. This keeps an eye on the number for you.

Leave it installed and use v0, Lovable and Bolt as usual. The extension reads the credit balance already shown on each dashboard, remembers it over time, and shows you a simple picture in one popup: how many credits you have left on each, how fast you're spending (per day), and roughly when you'll run out. The toolbar badge shows your lowest balance so a squeeze never sneaks up on you.

It's read-only. It never spends, buys, or changes anything — it just watches the number you can already see, and keeps the history on your device.

Independent extension, not affiliated with v0, Vercel, Lovable or Bolt.

Screenshots

What it does

  • Remaining credits for v0, Lovable and Bolt in one popup.

  • Burn-rate (credits per day) and a projected run-out date.

  • Toolbar badge showing your lowest balance across builders.

  • Read-only and local

    no spending, no account access, nothing uploaded.

When you'd reach for it

  • Checking the balance without opening three dashboards

    Each builder keeps its credit count in a different corner of a different page. The popup lists them together, one card per platform, with the current balance on each. The toolbar badge carries the lowest of those numbers, so the tightest budget is visible without clicking anything, and it turns red once that number drops below 50.

  • Working out how long the month's credits will last

    Once there are a few samples for a platform, the card shows a per-day burn rate fitted across the stored history along with an estimated number of days left. Before committing to a long build session you can see whether the current pace lands you at the end of the cycle or halfway through it.

  • Noticing when a build starts eating credits

    A run of failed generations burns through a balance much faster than normal work. Because a new sample is stored whenever the number on the dashboard changes, an unusually steep drop shows up as a rising per-day rate and a shortened run-out estimate the next time you open the popup.

How to use it

  1. 01Install, then open v0, Lovable or Bolt while logged in.
  2. 02Keep building — the extension records your balance as you go.
  3. 03Click the toolbar icon to see balances, burn-rate and projected run-out.

Permissions & privacy

Single purpose

Single purpose: Show the user their remaining credit/token balances on supported AI app builders, with burn-rate and a projected run-out date. Permission — storage: Stores the timestamped balance history locally (chrome.storage) to compute burn-rate. No personal data. Host permissions — https://v0.dev/*, https://v0.app/*, https://lovable.dev/*, https://bolt.new/*: the content script reads the credit balance shown on each builder's dashboard. Scope limited to these builders; no <all_urls>. Remote code: None. All code is bundled; nothing is fetched or eval'd at runtime. Data collection / transmission: None. Balances are read and stored locally only; nothing is transmitted. The extension performs no purchases or account actions (read-only).

storageSaves your settings and data in the browser's own storage, on this device.
https://v0.dev/*Runs only on https://v0.dev/*.
https://v0.app/*Runs only on https://v0.app/*.
https://lovable.dev/*Runs only on https://lovable.dev/*.
https://bolt.new/*Runs only on https://bolt.new/*.

Reads only the credit number shown on each builder's page and stores the history locally on your device. No account access, no purchases, no data sent anywhere. It runs only the code shipped inside the package — no remote code is fetched.

Questions people ask

how to check how many v0 credits i have left

Open v0, Lovable or Bolt while signed in, keep working as usual, and the extension records the balance those pages display. Click the toolbar icon and each tracked builder appears with its latest balance. The badge on the icon always shows the lowest balance across whichever platforms have been seen, abbreviated with a k above a thousand.

Why does it say it's still collecting?

A burn rate needs more than one reading. The first visit stores a single balance, and until there are at least two samples showing a decline there's nothing to draw a line through, so the card says it's collecting instead of guessing. Use the builder for a while and reopen the popup and the per-day figure and days-left estimate appear.

How is the run-out date worked out?

It fits a straight line through the stored balance samples for that platform and takes the downward slope as credits per day, then divides the current balance by that rate. It is an extrapolation of your recent pace, not a statement from the platform, so a quiet week or a heavy weekend will move it. Only the last 60 samples per builder are kept.

Does it need access to my account or my billing?

No. The manifest declares one permission, storage, plus host access to v0.dev, v0.app, lovable.dev and bolt.new — the four dashboards whose credit figure it reads. The balance history it builds is kept in the browser's local storage. Independent extension, not affiliated with v0, Vercel, Lovable or Bolt.

Why is a platform missing from the popup?

A builder only appears after the extension has actually seen a balance on its pages, which requires being signed in on a page where the credit figure is displayed. Balances often load a moment after the page does, so it re-checks for a short while after each load. Only the four supported domains are covered — other AI tools aren't read, because no permission for them is declared.

Related extensions

More in: Developer tools