Attribution
OpenOrange attributes model usage by instance, actor, agent, route, request, token count, cache behavior, provider cost, and tariff context, with reporting-period and subject-limit controls.
// account.model_usage
Model usage accounting
OpenOrange makes model and service activity accountable by actor, agent, route, model, request, reporting period, provider cost, tariff, service, and operation.
Usage accounting in OpenOrange connects model calls and service activity to the operating context that produced them: instance, actor, agent, route, model, reporting period, provider price, tariff, and service.
01
Token and prompt-cache savings stay visible per operated surface.
02
Provider costs are tied to model routes and historical price versions.
03
Customer tariffs make usage explainable instead of hand-waved.
04
The staging Services ledger extends attribution to search, mail, connectors, and web activity.
Pricing history
Historical model prices and customer tariffs keep billing explainable even when provider pricing or internal commercial terms change over time.
Services ledger
Staging adds a provider-aware inventory and activity ledger for search, mail, connectors, and web access so operational consumption is visible beyond model tokens.
// questions
Is this a generic billing dashboard?
No. It is model and service usage accounting tied to people, agents, runtime context, request traces, limits, and price history inside a private instance.
Can cache savings be explained?
Yes. The accounting model can preserve prompt-cache behavior and savings so operators can explain both spend and efficiency.