Macroscopic invoicing

Rikaii bills pay-as-you-go usage on Rikaii-routed traffic using a macroscopic model aligned with common Stripe-style invoicing: many small metered events roll up to one wholesale subtotal, one platform fee line, and one total per billing period.

The math (Stripe-standard mental model)

For each monthly invoice window the platform:

1. Sums your pure wholesale API costs for the period (the underlying inference spend attributed to your workspace).
2. Applies one platform fee of 4% to that global wholesale total (not per micro-transaction).
3. Presents a single unified invoice with wholesale, fee, and total due.

This keeps the fee line easy to audit and matches how teams expect to read a platform invoice alongside card charges.

Deleted keys policy (critical)

Compute is immutable. If you delete an API key to cycle credentials, its historical usage will still appear on your monthly invoice labeled as (Deleted).

Deleting a key does not delete or rewrite past metered events.

Related

• Understanding Cost Avoidance
• BYOK integration