Skip to main content
Pricing & Billing

Notifications & Billing Email

What Relay tells you, when, and through which channel — balance, rate changes, and monthly statements.

In-app vs. email

Relay reuses Vibgrate's existing notification pipeline: events land in your Vibgrate Cloud notification feed in real time, and the ones that matter financially are also emailed, since billing email is often the only Vibgrate surface a finance team ever sees.

What triggers a notification

TriggerWhat it tells you
Top-up succeededReceipt: credit, processing fee, tax, total, and the exact expiry date
Auto top-up chargedSame as above, plus what triggered it and how to change or disable it
Auto top-up failedWhat failed, that auto top-up is now off, and how to fix it
Balance lowCurrent balance, recent burn rate, and a direct top-up link
Credit expiringAt 30 and 7 days before an expiry: amount, exact date, that it's use-it-or-lose-it
Rate increase approvedWhich model, old vs. new price, effective date — sent to every workspace that used that model in the trailing 30 days
Rate decrease appliedSame, announced automatically — nobody needs to approve giving you a lower price, but you still deserve to know
Monthly statementSpend by repository and branch, per model, credits consumed vs. expired
Platform fee due (BYOK)The threshold, your measured spend, and the marginal fee calculation shown in full

Reproducible arithmetic, always

Every billing email is generated from the same ledger and usage rows the dashboard itself reads — a statement or receipt can always be reconciled line-by-line against your account, and no email ever carries a secret, a token, or a provider key.

Rate-change notice example

A rate change is never applied silently. When an increase is approved (decreases apply immediately and are simply announced), every affected workspace sees:

Model: anthropic/claude-sonnet-5
Old price: $3.00 / 1M input tokens
New price: $3.30 / 1M input tokens
Effective: 2026-09-01

Because every rate card is versioned rather than mutated in place, any request you already ran is unaffected — it's always billed at the rate that was active the moment it ran, never re-priced retroactively.

Related Documentation