Hermes

Observed through

Tokscale Model Report

Hermes model details and observed coding usage from Tokscale.

Reality Snapshot

Observed tokens

2B>+999%

over 30 days

Estimated tracked spend

$138

Invoices may differ

Active developers

1+0

this month

30-day momentum

>+999%

Compared with the prior 30-day window

Most-used client

Hermes Agent100%

of observed tokens

Observed Usage

Tokens observedDaily active developers
Observed coding tokens over 30 daysDaily observed usage from Jul 12 through Aug 10, with active developer activity for context.1B800M600M400M200M010.80.60.40.20Jul 12Jul 15Jul 18Jul 21Jul 24Jul 27Jul 29Aug 1Aug 4Aug 7Aug 10

How developers use it

Usage by coding client

Sharevs 30 days

Token composition

Share of observed tokens

43%cache read
Input1.1B56%
Cache read873M43%
Output3.5M<1%
Reasoning734.3K<1%
Mixed token profileObserved work is distributed across fresh input, cache, and output tokens.

Token Economics

Estimated spend profile

Hermes Agent$138100%

Observed cost signals

Estimated spend per 1M tracked tokens$0.07
Cache-read share43.4%
Estimated cache savingsNot available
Typical workloadmixed

Estimated tracked spend calculated from Tokscale model and provider pricing data. Actual invoices may differ.

Model Momentum

>+999%30-day growthRank: Observed model

Compared with the prior non-overlapping window

Fastest-growing client: Hermes Agent

800M533M267M0Jul 12Jul 27Aug 10

Official Model Details

Tokscale Insight

Hermes recorded 2B coding tokens across 1 developers during the latest 30-day Tokscale window.

Observed confidenceLimited sample