Billing
How ByteKit prices bandwidth and credits, and how balances, top-ups, and spending controls behave.
ByteKit meters two separate things: bandwidth, which pays for the capture endpoints, and credits, which pay for search and schema extraction. The relevant balance is checked before any billable work is admitted, so a request either runs against a balance or is rejected — it never continues as unpriced usage.
Balance and exhausted quota
What happens when a ByteKit bandwidth or credit balance reaches zero.
Bandwidth billing
How ByteKit measures billed bandwidth for capture and sitemap endpoints.
Credit billing
How search and schema extraction consume credits.
Top-ups and rollover
How purchased bandwidth and credits expire, carry across periods, and are consumed.
Spending controls
How spending caps and automatic bandwidth top-ups behave.