billing

What the ledger came to, with comped work split out

Estate-wide ledger totals for a window (the current UTC month by default), with operator-comped usage taken OUT of the revenue line and reported as complimentary_cents instead of netted into it. One D1 read; no vendor is called, and no query, report or customer name appears in it.

get/v1/admin/billing/summary

Request

  • Base URL: https://api.hyperresearch.ai
  • URL: https://api.hyperresearch.ai/v1/admin/billing/summary
  • Auth: API key in cookie hr_session

Query parameters

fromstring
Example:2026-09-01T00:00:00Z
tostring
Example:2026-10-01T00:00:00Z

Response

Ledger totals for the window

fromstring required
tostring required
charged_centsinteger required

Money customers owe for this window: every positive ledger row that is neither comped nor trial-covered. This is the revenue line, and a comped run is never in it.

complimentary_centsinteger required

What the comped runs of this window would have cost, at their real list price (0041). Reported rather than netted away: the work was real and it cost us real money.

refunded_centsinteger required

The negative rows, as negative cents.

gross_centsinteger required

Every row in the window. Reconciliation only.

eventsinteger required
complimentary_eventsinteger required
complimentary_accountsinteger required

Accounts carrying a complimentary grant that is in force right now.

Changes

No recorded changes to this operation across all 1 revision of this API.