Skip to main content
See what your model calls cost and who made them, then open any single call to see how it was served. Every view reads the same usage records the gateway writes for each call.

Before you begin

  • You can sign in to Model Gateway studio.
  • What you see depends on your role. An organization admin sees the whole account. Everyone else sees their own calls and those made with their own API keys; each report says which at the top.

Studio views

1

Read the account at a glance on Usage

Open Usage. Pick a Range: Today, 7 days, 30 days, or Custom…. The tiles show Spend, Requests, Tokens, Refused, Error rate, and Avg latency, each against the previous period. In the chart, choose a Measure and Break down by Model, Provider, Person, Workspace, or Operation. Select a series to narrow the whole page to it. Export CSV downloads what the page shows.
2

Open a focused report

From Usage, open Models leaderboard to rank models by requests, tokens, spend, effective cost per million tokens, and latency. Open Providers to compare providers that serve the same model, from your own traffic. Open Health for errors and refusals.
3

See spend by person

Open People for everyone in the directory with their spend, requests, and tokens over the range you pick. Keys and agents acting for a person count under that person.
4

See spend by agent

Open Agents. Your agents and System agents are separate tabs, and Workspace filters by an agent’s workspace. Each row shows the agent’s model, requests, tokens, spend, and the people it acted for. Select an agent to see its spend per day by person.
5

Find a single call on Calls

Open Calls. Pick a Range (1 h, 24 h, 7 d, or 30 d) and an Outcome (All, OK, Errors, or Refused). Filter by Provider, Model, Made by, Agent, Streamed, or Error class, or paste a Trace id (exact). Sort by time, duration, tokens, or cost. Select a row to open the call.
6

Try a model in the Playground

Open Playground and pick a mode: Chat, Image, Speech, Transcribe, Realtime, Rerank, or Moderate. Choose a Model; a model you can’t call says why. In Chat, select + Compare with another model to send the same prompt to two models side by side. Exact call shows the request with curl, Python, and TypeScript to repeat it.

What a call shows

The drawer that opens from Calls shows the call’s outcome, whether it streamed, and how many attempts it took. Its sections are:
  • Tokens and cost: Input, Cached input, Cache write, Output, Reasoning, what was Billed, and where the price came from.
  • Timing: First token, Total, and Output rate.
  • Route: Served by (the provider and its wire), Upstream model, and Workspace.
  • Who and where: Made by, and the Agent when an agent made the call for a person.
  • Trace: the request, session, and trace ids, with Copy trace id.
Prompts and replies are never stored, so Open in playground opens the same model and you type the message again.

Verify

  1. In Playground, send a chat message to any model. Each reply is a real, metered call made as you.
  2. Open Calls and turn on Live, which refreshes every 5 seconds. The call appears within a few seconds, with status OK.
  3. Open Usage. The call counts in Requests once usage folds in, which takes a few minutes.
A call made with an agent’s own API key belongs to the agent, not to you. It doesn’t appear in your Calls. An organization admin sees it on Agents, in the Own credentials column, and in the account report on Usage.