Billing and Units
CleanedWeb uses prepaid Units for API usage. One Unit pays for one saved record, and $1 of credit adds 1,000 Units. A run that saves no records, because it found nothing or failed first, uses no Units; a run that stops partway uses Units only for the records it already saved, and duplicate records are never charged. Signup includes a one-time allowance of 5,000 free records (5,000 Units), with no card required. The current prepaid offer has no subscription, and purchased credit does not expire. Optional auto-reload can make additional credit purchases when your balance runs low.
On this page
Use the pricing page for the public offer and the purchase summary in your workspace for the selected amount, discount, and payment total. Existing purchases or separately agreed terms may differ.
Read your balance and usage#
Open Billing in the selected workspace to inspect Available Units, Units used this month (UTC calendar month), purchase history, and saved auto-reload settings. Available Units are displayed as whole spendable Units; recorded usage can retain fractional precision where applicable.
A dash or Unavailable means the value could not be confirmed. It is not a zero balance or a zero charge. If Billing identifies a test or sample environment, follow that environment's restrictions rather than treating its values as a live account balance.
For a specific execution, open the run and inspect Charged Units and its charge receipt when available. A record count or an HTTP response alone is not proof of the amount charged. Keep the run identifier for any usage review.
Add credit#
Where credit payments are enabled, the workspace Owner can select Add credits, choose an amount, and review the server-confirmed purchase summary before continuing to Stripe checkout.
A purchase can add $10 to $10,000 of credit. Larger amounts receive a volume discount, and auto-reload adds 5 percentage points:
| Credit amount | Volume discount |
|---|---|
| Under $100 | None |
| $100 or more | 10% |
| $200 or more | 20% |
| $1,000 or more | 30% |
With auto-reload the discount is 5 percentage points higher, up to 35% at $1,000 or more.
The summary distinguishes Units added from the amount paid. For example, a purchase can add $100 of face-value credit while its discount reduces the payment total. Use the displayed quote rather than calculating the credited balance from the card charge alone.
After checkout, return to Billing and check purchase history. Payment submitted means settlement still needs to be confirmed. Credit appears after confirmed payment; the checkout redirect itself does not prove that your balance changed.
If the payment outcome is uncertain, refresh its state and contact support with the purchase reference before submitting another payment. If checkout is unavailable, check the workspace message and ask the Owner to review access and availability.
Configure optional auto-reload#
Auto-reload is offered during credit purchase where available. Review these values before enabling it:
| Setting | Meaning |
|---|---|
| Credit amount | The amount of credit to add on each refill. |
| Balance threshold | The level below which a refill can be triggered. Default $5.00. |
| Monthly spend limit | The authorized ceiling for automatic refill spending. Default $1,000.00. |
| Refill payment total | The amount charged for a refill after the applicable discount. |
Auto-reload settings activate after successful payment. Billing shows the saved status and settings. You can turn auto-reload off there; a payment already initiated may still complete. A paused refill may require a reviewed payment or a newly authorized saved card before it can resume.
Monthly usage budget#
Under Monthly usage budget in Billing, the Owner can select Limit monthly usage and set Monthly cap (Units) and Alert at (%) (default 80). The budget covers the UTC calendar month; adding credit does not reset usage, and existing reservations count toward the cap. A run saves no records beyond the cap; records already saved stay readable.
Review a charge#
For failed, partial, or repeated runs, compare execution details with the billing record before drawing a conclusion. Do not repeatedly rerun an uncertain request to investigate a charge.
Follow the billing review policy and include your workspace, purchase or invoice reference, charge date, amount, currency, and relevant run identifier. Never send payment-card details or API credentials. The support guide explains how to prepare a concise report.