One credit, one checked page
A credit pays for one page checked in an update that passes its checks.
Pricing
You pay for updates that pass. A held update costs nothing.
Accounts start with a credit grant. Prices publish when billing turns on. Until then, the first dataset is on us.
Starter plan card. Publishes when billing turns on: included credits, the per-credit price, and what a dataset with N pages costs a month.
Team plan card. Publishes when billing turns on: included credits, the per-credit price, and what a dataset with N pages costs a month.
Scale plan card. Publishes when billing turns on: included credits, the per-credit price, and what a dataset with N pages costs a month.
How credits work
Held updates are free
A failed check writes no rows and charges nothing. So does a page a site refuses to serve.
The balance is always visible
Every API response carries a credits-remaining header. No surprises at the end of the month.
Rules are versioned
Every charge keeps the pricing rule that applied when the update passed, so old invoices never change under you.
Questions
The questions
people ask first.
Short answers. If yours is not here, email hello@grava.dev and it will be tomorrow.