Skip to main content
Cost Center in the sidebar groups the organization’s spend and its controls: Overview and Cost quality share the reporting period chosen in Cost reporting period. Provider inference charges are separate from your Aixy subscription.

Overview

Overview shows organization-wide spend for the reporting period:
  • Recorded API cost: the total Aixy attributed to requests in the period, with its Cost attribution by project, team, user or key.
  • Month forecast: projected from month-to-date usage, available for the current month.
  • Budget health: the latest hard-budget balances and monitor thresholds. Each budget uses its own current period, and overlapping policies are not added together. Budgets needing attention lists those approaching or over their limit; choose Inspect or View policy.
When some requests have no amount or only partial pricing, Overview marks the total as possibly incomplete. Choose Review cost quality before reading the total as the full spend.

Cost quality

Cost quality shows how much of the period’s traffic has a recorded amount and why the rest is missing. Each request has one provenance: Under Requests without an amount, choose a reason to open the matching requests in Activity. Then use Investigate and correct:
  1. Inspect the request: check its usage, cost source and why the amount is missing.
  2. Check model pricing: add or revise a rate in the Price Book so future requests are covered.
  3. Assign a request price: in a supported request’s details in Activity, preview a Price Book assignment before saving it. This requires Activity access and permission to read and write pricing.
Recorded API cost can differ from provider invoices and from the amount a hard budget retained. Price changes and request assignments do not change hard-budget balances; reconcile those in Enforcement.

Enforcement

Use Enforcement when a member reports that a budget blocked their request. Find the member under Member budget balances to see every budget that applies to their active API keys:
  • Shared with all contributors: every covered key draws from one balance.
  • Allowance for a member: each covered member has a separate balance.
  • Hard limit blocks requests once reached; Monitor only records and alerts without blocking.
A request must satisfy every applicable hard budget, so raising one limit does not bypass another. Compare the counted amount, reservations and available balance, then open View member activity, Review unsupported cost or Review failed requests to inspect the requests. To correct counted consumption after fixing a request’s price, use Reconcile balance.