Microsoft's MAI Code 2 Halves Input Price to $0.50/M Tokens; DeepSeek Kills 18-Day-Old Web Search Fee — How to Reroute Your API Bills
Token pricing and per-call fees directly decide whether agentic workflows are cheap enough to run continuously. Western developers running automated retrieval or large refactors can save hundreds of dollars per month by re-routing to the newly discounted MAI Code 2 and by using DeepSeek's now-free built-in web search, as long as they respect the billing boundaries.
Microsoft shipped MAI Code 2 at Ignite 2026 with a 1.05 million-token context and a promotional price of $0.50 per million input tokens (output at $2.50), half the normal rate until May 17, 2027. The sparse MoE model with native vision encoding runs in GitHub Copilot and Microsoft Foundry, and its Flash variant gives near-instant completions. Blind tests on a 30,000-line backend showed roughly equivalent performance to GPT-6.2 Sol and Gemini 4 Neon for refactoring and unit-test work, at a fraction of the cost.
DeepSeek reversed course on its web search fee after only 18 days. The 5 yuan per 1,000 successful requests charge, introduced November 1, is now gone for any search automatically triggered by the model — including the official web search tool and the Anthropic/Responses API web_search. Standalone Search/Fetch API calls still cost money, and fetched content still counts as input tokens, so tool parameters should cap results at 3 to avoid ballooning context.
A practical routing strategy splits daily work: 80% to discounted MAI Code 2, real-time lookups to DeepSeek's built-in web search, and less than 10% of hard concurrency/architecture tasks to premium models. The author's monthly spend dropped from $200–350 to under $40, with a 12-line Python routing config that switches on scene: search vs. coding.
DeepSeek's 18-day fee reversal suggests that charging for built-in web search was a pricing experiment, and the backlash from automated users (whose bills ballooned despite low token costs) forced a quick rollback.
The half-price window for MAI Code 2 is effectively a long-term (18-month) price war, not a short-term promo, and it pressures other providers to match the $0.50 input rate.
With context windows now over a million tokens, the input token price has become the dominant cost lever for repository-scale refactors, making model choice more about input cost than raw output quality.
Capping web search results at 3 is a subtle but critical optimization: the real cost in retrieval workflows isn't the per-call fee anymore, but the token bloat from long pages.