Skip to content

How to verify the model and usage of every request

· 5 min read · OpusVIP

Short answer

Type /model in Claude Code to confirm the active model, find the request in the console usage log, and check its model and its input, output and cache token counts. Multiply the tokens by the per-token list prices: the result should match the credits deducted in the log.

OpusVIP records the model, token usage and credits deducted for every request in the console. Here are a few quick checks that take only minutes.

Confirm the current model

Type /model in Claude Code to see the current selection, and switch with /model opus, /model fable, /model sonnet or /model haiku. The four aliases map to claude-opus-5-5, claude-fable-5-1, claude-sonnet-5-5 and claude-haiku-5-5.

Check the model in the log

Open the usage log in the console. Every request shows the time, model, input / output / cache read and write token counts, and the credits deducted. The model you pick is the model you see in the log. Claude Code occasionally sends light background requests on its own (for example, to generate a session title); these appear in the log as Haiku 5.5 and are billed at list price like everything else.

Recompute the price

Take any log entry, multiply each token count by the matching rate in the price table, and add them up to get the credits deducted. The method is in Billing and caching explained. OpusVIP bills in credits: 1 credit = $0.01 of usage at list price, so a USD list price times 100 gives the credit rate (for example, $4 is 400 credits per 1M tokens). The multiplier is 1x, and 100 credits cost $0.15, so that $4 of input costs you $0.60. Failed requests are free.

See whether caching is working

Run a few turns in the same session. From the second turn on, the log should show cache read tokens. Cache reads cost far less than regular input, which removes most of the context cost in long sessions. See Cache hit rate and billing explained.

Judge speed and quality on your own tasks

Pick a few tasks with a clear right answer (refactor a function, track down a known bug, read a large file and summarize it), run them, and note the quality and time taken. For more getting-started tips, see How to choose a Claude Code relay.


Questions? Email hello@opusvip.dev.