Token Ledger
A logging system that records the estimated token count, routing choice, latency, and prompt hash of each LLM call, typically persisted in JSONL format. It is used to identify duplicate calls, set thresholds for free paths, and provide an auditable data basis for routing decisions.
Timeline (last 90 days)
The ledger stores a truncated SHA256 hash of the prompt, which allows duplicate calls to be identified without retaining the original prompt.
The wall_s field in the ledger records measured wall-clock time, not an estimate.
The original author runs a summary script once each night, outputting distributions grouped by route: median tokens, p95 tokens, median latency, and the number of duplicate prompts derived from the hash statistics.
All Facts (3)
The ledger stores a truncated SHA256 hash of the prompt, which allows duplicate calls to be identified without retaining the original prompt.
50%UnverifiedThe wall_s field in the ledger records measured wall-clock time, not an estimate.
50%UnverifiedThe original author runs a summary script once each night, outputting distributions grouped by route: median tokens, p95 tokens, median latency, and the number of duplicate prompts derived from the hash statistics.
50%