DeepSeek Cuts Prices 75%, But the 100x Problem Remains

DeepSeek's recent decision to drastically cut pricing on its V4-Pro model by 75% should have been unequivocally good news for enterprise AI vendors and developers. Instead, many are discovering that cheaper models don’t automatically translate into healthier margins. The reason is simple: While inference costs plummet, agent systems are voraciously consuming tokens faster than prices are declining.

For the last 2 decades, software economics was dictated by the same rule. Infra became cheaper every year whereas applications became more capable. AI was initially hypothesized to follow the same pattern.

As frontier models improved and token prices dropped, many assumed inference would become a negligible operating expense. That assumption has begun crumbling exponentially. A chatbot usually turns one user question into one model call.

An agent turns it into a chain of planning, retrieval, tool use, verification, summarization, and follow-up decisions. The user sees one answer. The vendor pays for the loop.

That is the 100x problem: The same user-visible request can cost a lot more to serve as an agentic workflow than as a chatbot or retrieval-augmented generation (RAG) response. In longer-running workflows, the multiplier is higher. Falling model prices help, but they do not fix a product architecture that turns one prompt into dozens of billable operations.

The scale of what is now at stake is clear in how model providers themselves are pricing developer relationships. OpenAI's proposed program to give every Y Combinator startup $2 million in API credits — a number that would have funded an entire seed round in any prior tech cycle, and when the same cohort got by on a few thousand dollars of AWS credits — is less a recruiting perk than an admission of what it now costs to run an AI-native company through its first year of product. For established enterprises retrofitting agents into existing product lines, the absolute numbers are larger still.

What token amplification is In a single-turn chatbot, one user message produces roughly one model call. Input-to-billed ratio is about 1:5. In a multi-step agent rolled out across customer support, sales operations, finance, legal review, and engineering, that ratio routinely lands at 1:700 or higher .

Every loop iteration carries forward the cumulative conversation, tool outputs, and reasoning traces. Each step appends; nothing is dropped. A "simple" agent query like " What did our top customer ask about last week?" typically touches seven priced operations before returning an answer: User prompt (~50 tokens) System prompt and tool definitions (~3,000 tokens, repeated on every call) Retrieval (~5,000 tokens of context) Model call #1 — tool selection (8,000 in / 200 out) Tool execution (~4,000 tokens returned) Model call #2 — summarization (12,000 in / 400 out) Model call #3 — follow-up decision (12,400 in / 100 out) One sentence in, roughly 35,000 input tokens billed.