Skip to main content
Early pricing is live. Start free for up to 3 AI systems — no card, no time limit.Early pricing is live. Free for up to 3 AI systems.
All docs
Explanation

What leaves your machine

The data flow from a local session log to the Scorecard: what the collector sends and what never leaves.

4 minFor: Engineer, Finance reviewer

Data flow

The collector reads the logs Claude Code and Hermes already keep on a machine, adds them up per day, harness and model, and pushes the totals. The totals are the only thing that crosses the network.

YOUR MACHINEOABO, YOUR ORGANIZATION ONLYtoken counts, sessionsClaude Code session logs~/.claude/projectsHermes state~/.hermes/state.dboabo-collector scanper day, harness, modelstate.jsonwhat was already pushedNever leaves: prompts, completions,file contents, file namesPOST /api/v1/usage/gateway/collector/eventsAuthorization: Bearer <ingest key>Usage recordsby day and systemPriced twiceactual and equivalentCosts and Scorecard
the collector aggregates token counts by day, harness and model; conversation content never leaves the machine · source data-flow.mmd

What is sent

FieldWhat it is
fingerprintThe project directory’s basename, lowercased and sanitized, or the value you mapped it to. Never the full path.
dayThe day the usage is attributed to, UTC.
harnessclaude_code or hermes.
model, provider, billing_modeAs the harness names the model; provider and billing mode clamped to the allowed sets.
input_tokens, output_tokens, cache_read_tokens, cache_write_tokens, cache_write_1h_tokensToken counts, summed for the day.
sessions_countHow many sessions contributed that day.
reported_host, reported_userThe machine’s hostname and the OS user name, sanitized. Reported, not verified.
Authorization headerThe source ingest key. It travels in the pasted installer text and the config file, never in a URL.

A zero record is sent for a day-key that vanished from the window because a file's modification day moved, so a stale server row is retracted rather than double counted.

What is never sent

  • Prompts, completions, messages, tool calls or any conversation content.
  • File contents, file names or directory paths. Only the sanitized basename becomes the fingerprint, and a mapping can replace even that.
  • Anything from the Hermes database other than usage figures; it is opened read-only.
  • A cost figure. The collector sends counts; Oabo prices them, twice.

Note

The same rule holds for every door. The MCP evidence endpoint refuses a whole batch if any record carries prompt or completion text, and names the offending path. See Evidence records.

Where it lands

  • POST /api/v1/usage/gateway/collector/events, which accepts only a Developer machines key.
  • Usage records keyed on organization, system, day, harness, model and provider. A re-push replaces that day's rows; it never adds to them.
  • Each record is priced twice, actual and equivalent; subscription usage has an actual cost of zero and a real equivalent cost.
  • A fingerprint the workspace does not know lands in the unattributed pool, counted on the source until someone assigns it. Nothing is registered from a directory name.
  • On screen: Models in use on Home, the agent's spend section, Connections for the source's health, and the Scorecard's cost side when enabled.
  • The first real attributed cost retires the seeded illustrative figures for the organization, once.

Previous

How a request stays inside your organization

Last documented 2026-11-18 against master fb17e1c5. Live release 0.3.1.