Fairness & Observability

The principles that keep RPT honest, the invariants that keep it reliable, and the APIs that let you see exactly where your credits went.

Last updated: 2026-04-24

RPT is designed so that you can always explain your bill — not just to yourself, but to your procurement team, your auditor, and your finance partner. Three layers make that possible: principles (what we promise), invariants (what the system guarantees), and observability (what you can actually see).

Fairness Principles

Four principles hold across every plan and every integration.

Principle	What it means for you
Cost-based	Credits are derived from the actual cost of the AI call. If the underlying model gets cheaper, your credits go further. The conversion includes a transparent platform overhead.
Append-only ledger	Every credit grant and every flush to the ledger creates a new, immutable record. Nothing is rewritten after the fact.
Audit-complete	Every AI call is recorded with the model used, token counts, and the cost that drove the charge. You can always trace a credit back to the work that consumed it.
Predictable caps	Each plan has a monthly allocation. If you approach or exceed it, you will know — through the UI, the API, and (depending on configuration) event notifications.

Reliability Invariants

RPT is built around a small number of hard invariants. These are not aspirational — they are verified at multiple layers of the platform.

Invariant	What it means for you
Monotonic counters	Your consumption total never decreases. You can’t be surprised by a retroactive jump.
Idempotent allocation on signup	If an account creation event is retried, you don’t get double-allocated credits.
Integer external reporting	When bizSupply reports usage to an external billing system, the figure is always a non-negative integer. Fractional accumulation stays internal.
Separation of metering and enforcement	Metering never blocks your request path. The enforcement layer (quota checks) is designed to fail safely, not to drop billing data.
Durable audit of every AI call	Even if any in-memory cache fails, the raw per-call record persists and can be reconciled.

Observability Surfaces

The Credits section of the bizSupply UI, and the public Credits API, expose everything a customer needs.

Customer-visible data

Current balance — allocated, consumed, and remaining (plus an unlimited flag for Enterprise).
Consumption history — paginated snapshots of how credits were used over time.
Allocation history — every credit grant, its source (signup / renewal / plan change), and its amount.
Plan definitions — the catalog of available tiers, features, and allocations.
Token usage summary — aggregated token counts per job, useful for attributing cost to a specific workload.

ℹ️Note

All of these are read-only from the customer’s perspective. Ledger mutations happen only through trusted internal flows (your subscription events, top-ups, and plan changes).

Credits API — shape of the balance response

The Credits API lives under the standard bizSupply API base and is authenticated with your tenant API key. A balance query returns allocated, consumed, and remaining totals plus a flag for unlimited accounts.

bash

curl -X GET "https://api.bizsupply.com/v1/credits/balance" \
  -H "Authorization: Bearer YOUR_API_KEY"

json

{
  "plan": "professional",
  "billing_period": {
    "start": "2026-04-01",
    "end": "2026-04-30"
  },
  "credits": {
    "allocated": 25000,
    "consumed": 8432,
    "remaining": 16568,
    "unlimited": false
  },
  "tokens": {
    "total": 5127890,
    "by_model": {
      "gpt-4o-mini": 3240110,
      "gemini-1.5-flash": 1887780
    }
  }
}

💡Tip

Balance queries always reflect the most recent flushed ledger state plus a real-time adjustment at critical decision points (for example, before starting a long job). You will never see a balance that the platform would then refuse to honor.

Consumption and allocation history

Both histories are paginated and return immutable records, ordered by time. Every consumption entry links back to the job that produced it; every allocation entry names its source.

bash

="color:#5c6370;font-style:italic"># Last 30 days of consumption, page 1
curl -X GET "https://api.bizsupply.com/v1/credits/consumption?days=30&page=1" \
  -H "Authorization: Bearer YOUR_API_KEY"

="color:#5c6370;font-style:italic"># Every allocation event for the current billing period
curl -X GET "https://api.bizsupply.com/v1/credits/allocations?period=current" \
  -H "Authorization: Bearer YOUR_API_KEY"

Alerts and Notifications

You can configure usage alerts at any threshold. Notifications are delivered by email or webhook, depending on your plan.

50% / 75% / 90% of allocation consumed — the default milestone set.
Custom thresholds — any percentage or absolute credit count.
Anomaly hints — unusual spikes against your rolling 7-day baseline (available on Professional and above).

See the subscription guide for setting up alerts via the API.

RPT overview — how tokens become credits in the first place.
Compliance & audit — marketplace reporting, data handling, and audit trails.
FAQ — quick answers to the most common questions.

BILLING & CREDITSPlans & Billing Models BILLING & CREDITSCompliance & Audit