Claims

May 2026 token telemetry was cache-dominant: 82.9% of 73,950,305 recorded tokens were cache reads, suggesting persistent workflows shift the economic unit from cost per token to cost per completed artifact

Claim · All claims
Evidence · 1 study (2 entries) · design r2 · q1
Currency · newest study 2026 · not yet checked against its sources · not reviewed by a person

Subclaims

Reading the evidence codes

q is the design tier, i the impact, n the sample, and the kind with its r the rigour judged within that kind: what each code means.

This claim: no standardized effect is recorded in observations/ for it yet, so no benchmark reading is possible.

q1 i? In the strict May 1–May 25 trajectory subset (627 model-completed events), cache-read tokens represented 61,278,669 of 73,950,305 recorded tokens, a cache-dominance ratio of 0.829. → Anas H. Alzahrani 2026 q1 i? The author interprets the cache-heavy profile as evidence that persisted context was central to the workflow and that per-token accounting alone is a poor proxy for value. → Anas H. Alzahrani 2026 (2)

Evidence

Anas H. Alzahrani 2026

Anas H. Alzahrani, MD, PhD, MPH. (2026). Persistent AI Agents in Academic Research: A Single-Investigator Implementation Case Study. arXiv preprint. https://arxiv.org/abs/2605.26870 doi:10.48550/arxiv.2605.26870

q1 · i? · design · r2

Token-telemetry analysis of the strict May 1–May 25 model-completed trajectory subset (627 events) in the single-investigator case study. The article states token telemetry is usage telemetry, not invoice cost, and covers only a partial month.

"Cache-read tokens represented 61,278,669 of the total, yielding a cache-dominance ratio of 0.829 (CDR = 82.9%), compared with 10,697,394 input tokens, 754,633 output tokens, and 1,219,609 cache-write tokens."

Anas H. Alzahrani 2026 (2)

Anas H. Alzahrani, MD, PhD, MPH. (2026). Persistent AI Agents in Academic Research: A Single-Investigator Implementation Case Study. arXiv preprint. https://arxiv.org/abs/2605.26870

q1 · i? · design · r2

Authors' interpretation (type e) of the cache-dominance finding in the Resource Profile section, attributed to reused context rather than isolated fresh inference. Provider routes included OpenAI Codex-route, OpenAI-route, and Anthropic-route usage.

"The cache-heavy profile is an empirical signal that persisted context was central to the workflow. It also shows why per-token accounting alone is a poor proxy for value."

Discussion

Page metadata
Field Value
type claim
id cache-dominant-82-9-percent-tokens
title May 2026 token telemetry was cache-dominant: 82.9% of 73,950,305 recorded tokens were cache reads, suggesting persistent workflows shift the economic unit from cost per token to cost per completed artifact
description May 2026 token telemetry was cache-dominant: 82.9% of 73,950,305 recorded tokens were cache reads, suggesting persistent workflows shift the economic unit from cost per token to cost per completed artifact
status review
evidence_strength weak
newest_evidence 2026
generated by process:wiki-ingest on 2026-10-11
trust unverified — no one has confirmed this page's content
sources 2 — anas-h-alzahrani-2026, anas-h-alzahrani-2026-2

Frontmatter is the page's machine-readable record — see the Schema & Guide.