WeSearch

Cost-per-success, not cost-per-call: the LLM routing number nobody measures

Nitish Agarwal· ·1 min read · 0 reactions · 0 comments · 2 views
Cost-per-success, not cost-per-call: the LLM routing number nobody measures
TL;DR · WeSearch summary

Member-only storyAIAi OpsAi FinopsSoftware DevelopmentSoftware EngineeringThe Cheap Model That Tripled Your BillNitish Agarwal10 min read·Just now--ListenSharePress enter or click to view image in full sizePhoto by Giorgio Trovato on UnsplashSomebody on your team did the responsible thing. They looked at the invoice, saw that the flagship model was eating the budget, and re-pointed the agent at the cheap tier. Then two weeks later the bill went up, the p95 latency got worse, and a ticket landed in the queue titled “model getting stuck in loop.” Nobody had lied.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 4,565 of its stories.

Original article
Medium · Nitish Agarwal
Read full at Medium →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherMedium
Canonical URLhttps://nitishagar.medium.com/the-cheap-model-that-tripled-your-bill-06c5c796fa25
Publication timeWed, 12 Aug 2026 09:57:48 +0000
Retrieval time2026-08-12T10:21:32.007Z
Last seen2026-08-12T10:21:32.007Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster6E8ZCU6mrvJ5 · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Member-only storyAIAi OpsAi FinopsSoftware DevelopmentSoftware EngineeringThe Cheap Model That Tripled Your BillNitish Agarwal10 min read·Just now--ListenSharePress enter or click to view image in full sizePhoto by Giorgio Trovato on UnsplashSomebody on your team did the responsible thing. They looked at the invoice, saw that the flagship model was eating the budget, and re-pointed the agent at the cheap tier. Ship it. Save money. Then two weeks later the bill went up, the p95 latency got worse, and a ticket landed in the queue titled “model getting stuck in loop.” Nobody had lied. The per-call price really had dropped. The system just started failing more often, and every failure cost you twice.This is the trap, and it’s not a model problem. It’s a measurement problem.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Medium.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Medium