Usage & Metering

Every tool call, whether it comes through the Tools API or the MCP server, is metered against the key that made it. You can review usage per key in the app.

Where to find it

In the app, open the profile menu, choose MCP Keys, then expand a key’s Usage panel.

What’s tracked

string | null

The current billing period, formatted YYYYMM, for example 202607.

number

Units consumed by this key in the current period.

number

Lifetime number of tool calls made with this key.

number

Lifetime units consumed by this key.

array

Per-tool breakdown. Each entry is { tool, calls, units }: the tool name, how many times it was called, and the units it consumed.

Example

{
  "key_id": "b3f1c2a4",
  "current_period": "202607",
  "current_period_units": 128,
  "total_calls": 5140,
  "total_units": 6021,
  "by_tool": [
    { "tool": "get_wallet_portfolio_breakdown", "calls": 2100, "units": 2100 },
    { "tool": "analyze_transaction", "calls": 820, "units": 1640 }
  ]
}

Notes

Units versus calls: a call is one tool invocation; units are the metered cost of that call. Some tools cost more than one unit.
Per surface: the Tools API and the MCP server are metered on independent per-key windows.
Owner-scoped: you can only see usage for your own keys.

Use a separate key per workload, such as a bot, a notebook, and a backend, so the per-key and per-tool breakdown tells you exactly where your usage is going.

​Where to find it

​What’s tracked

​Example

​Notes

Where to find it

What’s tracked

Example

Notes