Metering correction and credit policy

Last updated: 2026-07-26
Scope: Weirgate platform charges and the app-user entitlement ledger. Provider inference charges remain between the developer or end user and their provider.

Promise

Weirgate does not silently rewrite money history. Confirmed metering errors are classified, recorded, disclosed to affected developers, and corrected with append-only adjustments. usage_events remain the original observation; a correction never edits or deletes them.

We investigate and make customers whole for confirmed direct overcharges even when the amount is small.

Error classes

Class	Examples	Money at risk	Default response
Over-metering	Duplicate event, excessive units, wrong key-source classification	Developer platform charge; app-user allowance	Restore the full excess and correct any platform invoice
Under-metering	Missing event, too few units, omitted billable request	Weirgate revenue; developer downstream evidence	Record and disclose; do not silently claw back a closed app-user period
Missing or orphaned event	Provider-billed request with no usage event, or the reverse	Provider-cost evidence and disputeability	Quarantine the window from a parity claim and investigate request correlation
Price-table drift	Stale model price, wrong token class, provider fee omitted	Displayed provider cost or pricing advice	Preserve the event, correct derived totals prospectively, and annotate closed reports
Attribution error	Wrong tenant, app, user, feature, or key source	Another party's money or privacy boundary	Severity-1 incident; freeze affected billing output until scoped
Non-billable traffic leak	Doctor, health, fixture, retry, or failed call enters billing	Developer platform charge	Exclude it and credit any posted charge

Detection and evidence

Reconcile every closed week as a half-open UTC window, using matching timestamps and provider/API-key filters.
Retain aggregate provider and Weirgate subtotals, request counts, signed delta, absolute error rate, and an explanation for every nonzero exception.
Run the call-class rollup on the same window. Review modality, key source, calls, tokens, app-owner cost, user-borne cost, and non-billable rows.
Investigate any request-count mismatch, cross-tenant attribution, or nonzero dollar delta outside the evidence source's displayed precision.
Do not call a window reconciled while an exception is unexplained.

Correction mechanics

App-user entitlements

Excess debit: append an idempotent correction grant for the exact units lost.
Erroneous grant: reverse that specific grant through the existing reversal primitive.
Missing debit or under-metering: do not manufacture or edit a usage event and do not silently debit a closed app-user period. Record the exception and correct future behavior.
Failed or refunded inference: preserve the reservation/refund trail.

Developer platform billing

Before invoice finalization, replace the draft quantity with the corrected aggregate and retain both versions in the reconciliation case.
After invoice finalization, issue a credit note for the exact overbilled call or token line quantity. Do not hide it in a later allowance or unrelated discount.
Weirgate-caused underbilling in a closed period is waived; this correction surface cannot create a supplemental charge.
Provider charges are not resold by Weirgate. Correcting a displayed provider cost changes Weirgate's analysis, not the provider's invoice.

Notification and make-whole commitment

Acknowledge a reported money discrepancy within one business day.
Notify affected developers within two business days after confirmation and include the window, meter, signed delta, known cause, correction, and possible downstream impact.
Apply an entitlement restoration or platform credit within five business days after confirmation. Security or cross-tenant cases are immediate.
If app users lost units, restore all units. If the developer charged those users separately, provide the per-user evidence needed for the developer to refund them.

Report a discrepancy to [email protected]. Report a suspected cross-tenant or security incident to [email protected].