AI Weekly Malaysia

Anthropic published a guide on reducing token costs and improving efficiency when using Claude Code. Key recommendations include running /clear between tasks to avoid sending irrelevant context, setting model and effort levels before starting to prevent prompt cache busts, and using @-mention for files instead of naming them to save Read calls. It also advises using /compact before taking a break since the prompt cache expires after an hour.

Why: If you use Claude Code, changing your model or effort level mid-conversation busts your prompt cache and increases token cost, so you should configure these upfront. You should also run /compact before stepping away, as summarizing while the cache is still active is significantly cheaper.

Nvidia announced NeMo Switchyard, a software proxy that routes inference requests to different models based on cost, latency, or quality, claiming a 74% cost reduction versus using Claude Opus 4.8 alone with roughly a six-point accuracy tradeoff. Alongside it, Nvidia released Nemotron 3.5-30B-A3B-Lightning, a 30B-parameter MoE open-weights model for low-latency general use, and Nemotron Parse, a 1B-parameter model specialized in extracting context from PDFs including charts and tables.

Why: If you're paying for frontier-model API calls on every request, model routing lets you send trivial subtasks (title generation, summarization, PDF parsing) to cheaper or self-hosted models and reserve expensive models for the prompts that actually need them. The key insight is optimizing for completion cost, not per-token price—a model at 1/10th the token price that needs 10x tokens isn't cheaper. Evaluate whether a routing layer fits your stack before committing to a single provider.

Developers report that Anthropic's Claude API returns empty or truncated thinking blocks for Opus 4.8 and Sonnet 5 even when summarized thinking is explicitly requested, yet the underlying reasoning tokens are still billed in full as output tokens. Anthropic's own documentation confirms users are charged for all thinking tokens generated regardless of whether the thinking text is returned, and the issue may stem from display-summary testing rather than a broad outage.

Why: If you enable thinking on Claude Opus 4.8 or Sonnet 5, you may be paying for reasoning tokens you never see — so audit your token usage and consider lowering the thinking budget or disabling thinking entirely until the blank-block behavior is confirmed fixed. This directly affects your API cost per call.

Nvidia has doubled the MSRP of the RTX PRO 6000 Blackwell to $16,000, up from sub-$8,000 pre-order pricing last year. The card features 96GB of VRAM, making it a key option for local LLM inference and fine-tuning workloads.

Why: If you were budgeting for local GPU hardware to run large models, your cost just doubled overnight — recalculate build-vs-cloud-rental math now. For Malaysian builders importing GPUs, the ringgit impact is even steeper given currency conversion on top of the doubled USD price.

Alibaba Cloud presented 'DualLane' at SIGKDD 2026, a dual-path AI agent system for tech support tickets that classifies incoming queries as high-frequency routine or low-frequency long-tail, then runs a fast path (a couple of tokens) and slow path (up to 3,000 tokens) concurrently. If the fast path detects a routine scenario, it kills the slow path, avoiding unnecessary LLM calls. Alibaba reports this is faster, cheaper, and more accurate than letting agents handle all tickets, because agents commonly fail at tool selection, parameter generation, dependency extraction, and output synthesis.

Why: If you build AI agent pipelines for support or operations, the dual-path pattern is a concrete cost-reduction architecture worth testing: classify queries cheaply, run a lightweight fast path and a heavier reasoning path in parallel, and cancel the expensive path when the simple one suffices. Alibaba's documented agent failure modes (wrong tool selection, bad parameters, dependency extraction errors, output synthesis omissions) are a useful checklist for evaluating your own agent reliability.

Hyperscalers (Amazon, Google, Meta, Microsoft) are betting heavily on natural gas to power AI data centers, with Meta planning a 7.5GW plant in Louisiana, Amazon 7.6GW in Texas, and Microsoft and Google each building gigawatt-scale gas plants in Texas. Energy research firm Noreva forecasts natural gas prices could triple above $10/MMBtu in certain U.S. hubs (from ~$2-4.50 today), as hyperscaler demand collides with declining supply growth and rising LNG exports.

Why: If fuel costs double or triple, cloud compute pricing for AI workloads could rise materially since fuel is roughly half the cost of electricity from large gas plants. Founders and developers running GPU-heavy workloads on AWS, Azure, or GCP should model scenarios where cloud inference and training costs increase, and consider cost-optimization strategies like spot instances, model distillation, or multi-cloud arbitrage before locking into long-term cloud commitments.

CoreWeave CEO Mike Intrator says the company has signed A100 GPU contracts extending into 2029, demonstrating that Nvidia's 2020-era GPUs remain profitable nine years post-deployment. Power constraints and legacy infrastructure costs make older GPUs economically viable even as newer chips arrive.

Why: If you're budgeting GPU compute for AI workloads, don't assume older GPUs like the A100 will become cheap or obsolete soon — CoreWeave is locking customers into multi-year A100 contracts through 2029, which signals sustained pricing power for legacy hardware. This affects cost planning for anyone renting cloud GPU capacity or deciding whether to wait for next-gen capacity versus contracting now.

OVH Cloud CEO Octave Klaba warned of server rental price hikes up to 87% (gaming servers) and 40-59% (other recent servers) starting September 2026, driven by RAM costs rising 6x (heading to 12x next year), NVMe drives up 7x, HDDs up 3.5x, and CPUs/motherboards up 15-20%. OVH is also decoupling storage (€0.000146/GB/h) and IP addresses (€0.0027/h) from Gen3 instances starting October 1st, and dropping 1-month, 6-month, and 24-month saving plans.

Why: If you run on OVH or any budget European cloud, lock in 12 or 36-month saving plans now before September, and recheck your October bill for newly separated storage and IP line items. More broadly, the AI-driven hardware cost inflation Klaba describes is not OVH-specific—expect similar upward pressure across all non-hyperscale providers, which matters for SaaS unit economics and infrastructure cost projections.

Writer launched Palmyra X6, a post-training variation of Z.ai's open source GLM-5.2, alongside upgrades to its agentic harness, claiming up to 50% cost cuts for basic tasks. Writer's own research found that harness efficiency changes reduced costs an average of 40% across multiple models, often more reliably than model choice itself.

Why: If you're shipping AI agents, the practical lever to pull may be your harness/orchestration layer, not just swapping models. Writer's finding that harness tweaks averaged 40% cost reductions across models suggests auditing your agent loop—prompt structure, tool-call patterns, token reuse—before paying for a pricier model.

AI infrastructure spending is pushing up prices for electricity, chips, software, and data-center capacity, creating near-term inflationary pressure while corporate adoption remains uneven and productivity gains have not materialized. Fed Chair Kevin Warsh faces the question of whether AI-driven cost increases are a type of inflation that warrants interest rate hikes, despite Silicon Valley leaders like Sam Altman, Elon Musk, and Masayoshi Son promising eventual deflationary effects.

Why: If you are budgeting for AI-dependent products or SaaS, the article signals that infrastructure costs (compute, power, data-center capacity) are rising now while the productivity payoff is delayed — meaning margins may stay compressed longer than investor narratives suggest. Founders shipping AI features should price for current cost reality, not promised cost collapse.

The article title indicates OpenAI and Anthropic are engaging in a price war while Chinese AI competitors gain market share, but the actual article body was not provided—only cookie consent boilerplate is present in the source text.

Why: No concrete details (specific price cuts, model names, competitor names, or percentages) are available from the provided text, so no actionable takeaway can be extracted. Builders should look for the original article to assess whether API pricing changes warrant switching providers or renegotiating usage.