COMPUT Cost and Usage

COMPUT records gateway requests and provider-reported token usage. Cost figures are estimates, not invoices, and are not automatically measured savings.

Read the dashboard

Select a reporting period on the overview to inspect requests, input and output tokens, success rate, average response time, and estimated spend. Request history helps distinguish failed requests from successful completions.

Missing token usage means not reported, not zero. A model without a pricing entry can contribute zero to a cost total. A zero total therefore does not prove that the provider is free or that no invoice will be issued.

Estimates versus savings

Estimated cost is derived from recorded usage and configured model rates. Provider free-tier allowances, subscriptions, negotiated rates, and invoice adjustments may differ from these estimates.

Savings require a documented comparable baseline: the same workload, acceptable quality, and the cost without the optimization. Deduct retries, fallback charges, and infrastructure costs where applicable. Do not label all traffic sent to a free or cheaper model as verified savings.

Pricing and reporting

The pricing implementation is in src/lib/pricingSync.ts and the cost calculation in src/lib/usage/costCalculator.ts. Review model rates before using estimates for budgets or customer reporting.

The dashboard uses GET /api/usage/analytics; request logs use GET /api/usage/call-logs. These are management endpoints on the dashboard host, not public inference endpoints under /v1. Use authenticated dashboard access.

Analytics can recompute estimates with current pricing, so historical estimates may change when rates are corrected. Treat provider invoices as the authority for actual provider charges.

Troubleshooting

• Zero estimated spend: check that usage and a matching model price exist.
• Missing usage: inspect the upstream response; not every provider reports tokens.
• Delayed updates: refresh the reporting period; some spend recording is buffered.
• Unexpected charges: inspect retries, routing policies, provider billing, and quotas.

Compatibility identifiers

COMPUT currently retains inherited runtime names such as OMNIROUTE_SPEND_FLUSH_INTERVAL_MS, OMNIROUTE_SPEND_MAX_BUFFER_SIZE, and the omniroute CLI. These are compatibility identifiers, not a recommendation to install an unrelated package named comput. Do not rename environment variables without corresponding runtime support and a migration plan.

Start with the COMPUT quick start. COMPUT is based on OmniRoute; required license notices and upstream attribution are preserved.