Meter · token economics
Lower the token cost of every successful agent task.
Raw token totals reward inactivity and punish productive teams. Meter connects usage to outcomes: successful tasks, accepted pull requests, failed runs, and the repository work that consumed the context.
It identifies repeated discovery—agents rereading the same build files, tracing the same service boundary, or recovering the same command—and converts stable knowledge into maintained repository skills.
Finance sees attributable usage. Engineering sees where a better environment or reusable context will reduce cost without reducing completed work.
A day in Meter
From token volume to engineering unit cost.
Usage, successful outcomes, waste signals, and recommended repository skills share the same view.
| Group | Tasks | Success rate | Tokens / success | Cost / success | Trend |
|---|---|---|---|---|---|
| Core services | 684 | 82.4% | 76k | $1.84 | −12.1% |
| Data platform | 391 | 77.8% | 94k | $2.27 | −7.4% |
| Infrastructure | 328 | 71.3% | 113k | $2.91 | −3.2% |
| Embedded | 247 | 64.9% | 148k | $3.78 | +4.6% |
| Internal tools | 192 | 80.2% | 81k | $1.96 | −9.8% |
Measure the cost of completed agent work.
Connect a repository and establish its first cost-per-success baseline.