API key & token efficiency

Where the money actually goes, and the eight levers that move it — ordered by impact.

Hermes · internal reference · verified against fleet telemetry

The mechanic

cost = price × accumulated context, per call

Every turn resends the entire conversation. A 1,000-message session isn't 1,000× one message — it's roughly quadratic.

Nothing else in this list matters until that is understood: you are not paying for answers, you are paying for the transcript that precedes each answer.

Measured: 1,047 messages in one Telegram session → 3.4M input tokens.

Levers, in order — highest impact first

Measure it

Rule of thumb: if a session's context is over ~40% of the window and the task is done, /new.

On API keys specifically

Multiple keys per provider (credential pools) help with rate limits and rotation, not cost — same price per token.

Cost control is entirely about context size and model choice.