Model pricing and cost calibration

OcHub cost is a local estimate calculated from request tokens, model prices, and a multiplier. It is not the provider’s invoice. OcHub does not maintain its own built-in price list. A request can succeed while showing 0 when model IDs or pricing sources do not match.

What determines cost

One request can have three model names:

With gateway rewriting, all three can differ. For example, the client may request claude-sonnet-current, routing may send anthropic/claude-sonnet-4-6, and the pricing model should follow whichever real ID matches billing.

The price table stores four USD rates per million tokens:

• Input
• Output
• Cache read
• Cache write, also called cache creation internally

OcHub adds these base costs and then applies the multiplier. It also handles app-specific cache semantics: Claude-style input is usually fresh input, whereas Codex / Responses input can include cache reads that must be subtracted before applying the ordinary input rate.

Price sources and synchronization

The app bundle includes an offline catalog that CI filters, validates, and pins to a specific revision of LiteLLM’s official data. First launch therefore does not require the network, and the prices are not a separately maintained OcHub list. OcHub makes at most one conditional background check per day. Use Sync now under Usage → Model pricing to check immediately. If an update fails, the last valid catalog remains active.

Price resolution follows these rules:

1. User-saved manual overrides always win and catalog sync never changes them.
2. The catalog first matches a complete provider or regional model key, then a direct model key.
3. An alias is used only when every matching catalog entry has the same four rates. OcHub does not guess when providers or regions disagree.
4. When a request used cache tokens but the catalog omits the corresponding cache rate, the missing value is not treated as 0.

Models with tokens but no reliable price are grouped into one missing-price notice instead of repeated dialogs. After catalog sync or a manual override, OcHub attempts to backfill zero-cost historical requests with tokens. Existing nonzero costs are not rewritten in bulk.

Find the correct model ID

Do not guess from a marketing page:

1. Make a real request.
2. Open it under Usage → Request logs.
3. Record Request model, Model, and Pricing model.
4. Compare them with the provider’s price list.
5. Add the ID that represents the model actually billed.

If Pricing model is a custom alias, choose among response-model pricing, adding an equivalent alias price, or changing the route mapping. The most reliable setup makes Pricing model equal the provider’s priced model ID.

Add a manual price override

After a manual override is saved, OcHub attempts to backfill historical requests for that model whose token count is nonzero but total cost is still 0. Existing nonzero historical costs are not all recalculated, so a price change can create a before-and-after reporting boundary.

Request model versus response model

Claude and Codex have a default pricing-model source:

Compare both names on a direct request and a routed request, choose the source that consistently finds the real price, save defaults, then verify the Pricing model on a new request.

Claude Desktop inherits the Claude default multiplier and pricing source.

Cost multiplier

The default multiplier 1 leaves base prices unchanged.

The multiplier applies after input, output, and cache base costs are added. It does not change token counts.

If a provider marks up models differently, enter settled per-model rates and keep the multiplier at 1.

Check one calculation by hand

The base total is $0.08475. At a 1.2 multiplier:

$0.08475 × 1.2 = $0.10170

Use token values from one request detail, not the page-wide Actual tokens summary. OcHub already normalizes Codex / Responses cache semantics.

Reconcile with provider billing

When local estimates differ:

1. Use the same date range and timezone.
2. Filter to one provider.
3. Compare request counts, including upstream treatment of failures and retries.
4. Verify the pricing model.
5. Check whether system prompts, tools, or reasoning tokens are billed separately.
6. Verify input and cache semantics.
7. Check multiplier, discount, or currency conversion.
8. Reconcile one request before comparing daily totals.

Account plans, tiered prices, batch discounts, regions, or minimum charges may not fit one model price and multiplier. Treat OcHub as a request-level estimate and the provider invoice as the settlement record.

Data-source limits

OcHub cannot infer reliable cost when model or token data is absent.

Common problems

After setup, verify one new request with a known model. See View sessions and usage for daily filtering and drill-down.