Skip to content

Analytics and data

Bill the query, not the estimate

Data products are consumed unevenly. Record what was actually served, let the period add it up, and send a bill that shows the figure behind the amount.

Meters
As many as your product has
Arithmetic
Integer units, end to end
Billing
In arrears, when the period closes
app.reclack.com/usage/meter_queries

Queries · October

412,908

0.00 USDCbeyond the allowance

Included1,000,000 queries
Rate after that0.000135 USDC each
ExportsMetered separately

INV-00219

14.14 USDC

Opened when the period closes, with the query figure on the document.

The loop

Recorded, totalled, billed

The meter is yours. The adding up, the invoice and the collection are ours.

The difference

What a metered bill has to prove

A figure a customer cannot check is a figure they will argue with.

Without it

A number in an email

  • An amount with no breakdown behind it
  • Usage counted in a spreadsheet after the fact
  • Double counting when a job is retried
  • Disputes settled by looking at logs together

With Reclack

A bill with its own evidence

  • The usage figure on the invoice that produced it
  • Running totals visible before the period closes
  • Idempotent writes, so a retry counts once
  • A transaction hash on the payment that settled it

At the close

The invoice, and the payment behind it

app.reclack.com/invoices/in_0219

INV-00219

October period · metered

Open
Queries1,104,773
Included1,000,000
Billable104,773
Total due14.14 USDC

Opened automatically when the period closed.

app.reclack.com/payments/pay_9Kd2

0x2e2d…f306

Base · USDC

Pending

0 of 12 confirmations

Amount29.00 USDC
InvoiceAwaiting
ReceiptEmailed on confirmation

Questions

Before you meter

Can we meter more than one thing?
Yes. Define the meters your product actually has, queries, rows, exports, seats, and record against each. They appear as their own lines when the period closes.
How precise is the arithmetic?
Amounts live in integer atomic units from the meter to the chain. No floating point touches a figure that will be charged, and rounding is decided once, when the invoice is written.
What stops a retry from double billing?
Usage writes take an idempotency key. Posting the same record twice counts it once, so recovering from an outage on your side is safe.

Charge for what was served

Meter in your product, bill in arrears, settle in stablecoins to your own address.

Start building
The products behind itUsage billingInvoicesSubscriptions