Reading Usage & logs

Every request leaves a trace here: which model, how many tokens, what it cost and, if it failed, whose side it was on.

6 minLesson 4 of 80 of 4 steps

Usage & logs is where you find out what happened. When a key spends strangely or a tool doesn't work, the answer is here.

At the top: the big picture

Choose a time range and you see a few figures: requests, spend, input and output tokens, success rate and time to first token. The chart switches between Spend, Requests and Tokens.

Further down, usage is split by model and by key. Press any row and the whole page filters to it.

For any question about spending, look at the by-key view first. That's why we made one key per tool.

The requests table

ColumnSays
ModelThe model that answered
Input, Cached, OutputToken counts. Cached is input billed at a much lower rate
CostThat request's charge, in rials
First token, Total timeHow long to start and to finish
ChainAbove one means earlier models were tried and didn't answer

Use Columns to show or hide what you need. Export and the filters sit at the top.

Open a failed request

Press a row and the full detail opens. Three things stand out:

  1. Why it failed, in plain words, and whether it was on your side or ours.
  2. The chain of models and which one really answered. Only the model that answered costs anything.
  3. The request id, which you need for a ticket.

The Sessions and Members tabs

Sessions groups the requests of one conversation or agent run, so you see how many requests a whole job made and what it cost. If you have an organization, Members shows how much each person used.

Read your own log0 of 4 steps

  1. Set the range to today or the last 7 days.
  2. Open a request and see its model, cost and time.
  3. If you have another key, use the Key filter to see only that one.
Open the logs

What you learned

  • The summary says how much; the table says exactly where.
  • A chain above one means earlier models didn't answer and only the last one cost anything.
  • The Key and Model filters find any odd spending.
Connecting Claude Code, Cursor, Codex and the restThe tools you code with every day reach every model with one address and one key.Done, next lesson