Credits & billing

Running an indexer means running a dedicated worker pod that holds a validator stream open and writes to your database. Credits are how that compute is paid for.

Getting credits#

Every new account receives a free starting grant, so you can build and deploy your first indexer without entering payment details. Top up from the Credits page in your workspace when you need more.

How they are spent#

A running worker consumes credits continuously while it is up. An indexer that has never been deployed, or one that is stopped, costs nothing — you pay for workers that are running, not for indexers that exist.

Your balance is kept live rather than being reconciled at the end of a billing period, so the number on the credits page reflects what has actually been consumed a moment ago, not last night.

Running low#

You are warned when your balance falls to roughly a tenth of what you started with. That is the point to top up: it is well before anything stops, and it leaves room to act.

Keeping an eye on it#

• The Credits page shows your balance, your history, and consumption broken down per indexer — useful for spotting the one that costs more than you expected.
• Every deploy checks the balance before it starts, so a 402 at deploy time is the earliest and cheapest place to find out.
• If an indexer no longer earns its keep, delete it. There is no stop action in the current release, so deletion is how you stop paying for a worker.