Dashboard|

Billing & Usage

Understand plan tiers, credit-based usage charging, and spend controls.

Cencori billing combines plan limits with usage-based credits.

Two-Layer Billing
  1. Plan Tier: controls platform entitlements.
  2. Credits Wallet: prepaid balance used for AI request charges.

Requests are not capped by count on any plan. Even with credits available, a request can still be blocked by:

  • spend caps,
  • or security/rate-limit controls.

Plan Tiers

Tiers differ by features and seats, not by a request allowance — no plan caps how many requests you can make. What you pay scales with what you actually use, via the credits wallet described below.

Usage Pricing

For each successful managed-key request, Cencori computes:

  • provider cost from usage (tokens, image generations, audio duration/characters),
  • adds no Cencori gateway markup or per-request platform fee,
  • records final charge as cencori_charge_usd,
  • deducts that amount from org credits.

Formula:

managed: provider_cost = cencori_charge_usd
BYOK: cencori_charge_usd = 0

The provider cost uses the configured model rate and reported usage. If you enable Monetization, your own end-user rate-plan markup is separate from this Cencori usage charge.

See Credits System for top-up and wallet details.

Spend Management

Use these controls to prevent runaway spend:

  • Monthly Budget (soft): warning thresholds before overrun.
  • Hard Spend Cap: blocks requests once cap is reached.
  • Rate Limits: per-minute protection at project/API-key level.

Managed vs BYOK Billing
ModeProvider invoiceCencori wallet usage
Managed keysPaid by CencoriDeducted from credits
BYOKPaid by your provider accountNo Cencori usage deduction; provider cost remains visible in logs

See Bring Your Own Key (BYOK).

Where to Track Costs
  • Billing page (org-level balance and transactions)
  • Project logs and observability views
  • Request-level cost fields (provider_cost_usd, cencori_charge_usd, markup_percentage)
Did you like the content?