Examenos

Official vendor benches · independent evaluators · OpenRouter pricing

Guidesv 00be1f8

Read reported spending from a usage log

Import OpenRouter JSON or JSONL locally and understand charge coverage, duplicates and privacy.

Your goal: add up reported charges

  1. Open Calculator and select Check recorded spending.
  2. Select a UTF-8 .json or .jsonl file: one OpenRouter response, an array of responses, or one response per line. Generation-metadata responses are also supported.
  3. Read the covered total and warnings. Expand Inspect billing metadata for extracted request IDs and charges.
  4. Clear records when finished. Explicitly download sanitized billing metadata only if you want a local copy.

Which fields are read?

Responses use id and usage.cost; generation responses use data.id and data.total_cost. Missing charge fields are not zero. Duplicate IDs count once; conflicting IDs are excluded. Native counts, provider, model and tier are retained when supplied. Cumulative CLI counters, arbitrary CSV and subscription-equivalent estimates are not supported formats.

File protections

Files are parsed in a local worker with a five-second timeout, 10 MB limit and at most 10,000 records. Invalid UTF-8, excessive nesting/structure and duplicate JSON keys are rejected. Nothing is uploaded or executed. Prompt/content/account fields are discarded from derived data, and displayed text is escaped. These checks are not antivirus scanning or invoice authentication.

See response usage and generation metadata.

Sources and further reading

These explanations describe Examenos's data and display policy. Calculator examples are explicitly hypothetical. Inspect dated endpoint evidence and the formulas; projections do not authenticate a bill.