Token Controller Docs
Docs / Reference / Token entry schema

Token entry schema

The fields of a token entry, as the token entries endpoint and CSV import take them.

Browse the docs

Fields

FieldMeaning
agent_harnessThe product the agent ran on. Required.
agent_nameA label for the agent, such as "review bot". Optional.
modelThe model that did the work. Required.
started_at, ended_atThe time range. Required.
tokensCounts by kind: input, output, cache_write, cache_read. Required.
reported_costThe agent's own cost figure. Optional; without it the list value is computed.
summaryOne line on what the session did. The only text.
ticket, projectWhere it belongs. Optional; rules place it otherwise.
signalsBranch, working directory, repository, pull request number, subagent type, and ticket keys found in prompts, the session title and the pull request title. Optional.
session_idJoins the token entry to telemetry. Optional.

Set by Token Controller: agent manager, list value, billed value, postings, status.

Last updated 8 October 2026 · Edit this page © 2026 Jan Beck · Privacy · Imprint