Provider-reported usage only
Every token count is read from the model provider’s own usage field on the raw API response (never a tokenizer estimate applied after the fact).
Agent Tokenomics measures token usage across development frameworks with the rigor a benchmark deserves: fixed tasks, pinned model versions, multiple trials, and raw, independently reproducible transcripts behind every number. No self-reported estimates, no cherry-picked runs.
AI coding agents now write a meaningful share of application code, and every token they spend has a real cost — in latency, in dollars, and in context budget. Claims about which framework is more “agent-friendly” circulate constantly, almost always backed by a single anecdote rather than a controlled run. Agent Tokenomics holds the model, the task, and the tooling constant, varies only the framework, and publishes the raw evidence alongside the number.
Every token count is read from the model provider’s own usage field on the raw API response (never a tokenizer estimate applied after the fact).
Minimum five independent runs per task. Every nondeterministic input (tool output, timestamps, network calls) is disclosed, not papered over.
Every raw request/response log ships with a SHA-256 manifest, so a results table can never silently drift from the evidence behind it.
Model, prompt, tool access, and trial count are held constant across frameworks. Only the framework under test changes.
The same iOS app — same spec, same UI, two deep native features — built by isolated AI agents in both frameworks, with every token metered and the finished products performance-profiled.
One iOS app with two deep native features — HealthKit and Speech — built from a byte-identical spec by isolated AI agents in NativeScript and in Expo (React Native), under a spec that forbids third-party wrappers for the platform capability under test.
Every comparison here ships with a fully measured, fully published run. Replicate one on a different model, a new framework version, or bring your own framework pair — and submit the results.
Read the submission format