GPT-6.1 Terra halves costs; Decisions API hits GA

A developer review reports that GPT-6.1 Terra cuts vision-reasoning input costs to $1 per million tokens, half the price of GPT-5.6 Terra, with a reported 15-point gain on agent benchmarks and a drop-in model-ID swap requiring no prompt changes. The Decisions API reached general availability as a bounded-answer classification endpoint on GPT-6 Luna, handling up to 400 questions per request at $0.10 per million input tokens with roughly 10x lower latency, alongside native GPT-Live voice integration and US/EU regional residency. Google's Flash TTS was also covered for prompt-based custom voice design and 30-second voice replication with SynthID watermarking and consent verification.

This week delivered two of the more practically meaningful cost reductions in recent memory—GPT-6.1 Terra cuts vision-reasoning spend in half with no migration pain, and the Decisions API finally makes structured classification a first-class API primitive. Layered on top: voice generation that actually scales, multimodal search without caption hacks, and a Rust TypeScript compiler that's either a curiosity or a lifeline depending on how bad your type-check latency is. GPT-6.1 Terra ships at $1/M input tokens—50% cheaper than GPT-5.6 Terra—with a reported 15-point benchmark improvement on agent tasks. The migration story is as frictionless as it gets: swap gpt-5.6-terra for gpt-6.1-terra in your model ID, no prompt changes required. The practical unlock here is high-volume document automation. Invoice processing, form extraction, technical drawing interpretation—these workloads have historically been expensive enough to force architectural compromises batching, aggressive caching, selective routing . At half the cost with better accuracy, you can straighten those pipelines out and run them more aggressively. The routing heuristic is simple: GPT-6.1 Terra for everything that was running on GPT-5.6 Terra, GPT-6 Astra only when you genuinely need maximum-difficulty reasoning and can justify the cost delta. Verdict: Ship. Zero-friction replacement with meaningful cost and accuracy gains. Deploy today for any cost-sensitive vision or agentic workload. The Decisions API is a bounded-answer classification endpoint built on GPT-6 Luna. It trades generative flexibility for speed and cost on discrete decisions—routing logic, classification gates, scoring—and now handles 400 questions per request at $0.10/M input tokens $0.01/M cached . The problem it solves is concrete: agentic workflows are full of sequential completion calls that exist solely to make structured yes/no or categorical decisions. Each call carries the full overhead of a generative endpoint even when you only need a label. The Decisions API collapses those chains into a single request with a defined schema predicate, choice, or score types and returns results at 10x lower latency. Native GPT-Live integration is the other notable addition—real-time voice and multimodal decision loops without the context marshaling overhead that makes current implementations painful to maintain. Regional residency US/EU and prompt caching are included at GA. The upfront cost is schema definition. You need to think through your decision types before you can use this, which means it rewards teams who've already mapped their classification logic. If your app makes the same routing or gating decision hundreds of times per day, the pricing model heavily favors you. Verdict: Ship for any recurring classification or routing decision. Start with one high-frequency decision, validate schema design, then expand. Google's Flash TTS lets you generate custom character voices from natural language prompts, replicate voices from 30-second audio samples, and control performance at the line level—tone, pacing, dialect, speaker isolation. SynthID watermarking and consent verification are built into the replication flow. The meaningful shift is moving from preset voice libraries to programmatic voice design. If you're building audio agents, multilingual content pipelines, or interactive media, you've been either picking from a fixed palette or routing around TTS limitations with external tooling. This replaces both approaches with an API-driven model that scales without per-voice licensing overhead. Consent verification for voice replication 30-second sample plus verbal consent recording is a real workflow requirement, not optional. Plan for it in your data collection pipeline if replication is part of your use case. Flash-Lite TTS targets high-volume dubbing at lower cost for scenarios where dynamic voice design per request isn't required. Verdict: Evaluate. Available now in Google AI Studio. Worth running through the playground against your current voice solution before committing to integration work. Cloudflare AI Search now embeds images directly using Qwen3-VL-Embedding alongside text, handles 10 MiB PDFs with built-in OCR, and bills per query rather than by capacity. Free tier covers 5M ingestion tokens and 1,000 semantic queries per month; billing starts November 1, 2026. The caption-generation workaround for image search has always been lossy—you embed a description of an image rather than the image itself, and visual detail that doesn't survive captioning disappears from your index. Native multimodal embeddings fix the retrieval quality problem at the source. OCR on ingest removes the preprocessing step that makes PDF indexing tedious to operationalize. Setup requires Workers AI configuration and a choice between text-only and multimodal embedding models. If your index is text-only, the multimodal model adds overhead you don't need. If you're indexing product catalogs, screenshots, or scanned documents, it's the right default. Verdict: Evaluate if you're running caption-based image search or preprocessing PDFs manually. The free tier makes it low-risk to index a representative sample and compare retrieval quality directly. Ollama v0.40.0-rc3 automatically routes supported model architectures Qwen, Gemma, and others to the MLX runtime on Apple Silicon, eliminating the manual backend selection that previously required explicit configuration. For macOS developers running local LLMs, this removes the gap between "installed" and "actually fast." CPU fallback was the silent performance killer for anyone who hadn't manually configured MLX—now native acceleration is the default and opt-out is the override. Architecture support is the constraint. Check your model against the supported list before assuming MLX acceleration applies. Verdict: Ship if you're on Apple Silicon and v0.40.0-rc3+. Upgrade, verify your models are in the supported set, and move on. tsrs is a Rust implementation of TypeScript that runs 8x faster than tsc with 70% lower memory usage and compiles to WebAssembly. It's installable today via npm as an experimental package. The WebAssembly target is the more interesting technical story. TypeScript checking in browser and edge environments—without Node.js overhead—opens deployment topologies for build systems and developer tooling that weren't practical before. The raw speed improvement matters for large monorepos where type-check latency is a genuine iteration bottleneck. Diagnostic output ordering differences from tsc mean you should test against your existing codebase before relying on it in CI. Stable release is still pending. Verdict: Evaluate if type-check latency is actively slowing your team or you're targeting Wasm deployments. Too early to swap into production CI without validation work. If this kind of weekly signal-to-noise filtering is useful for your work, Signal goes out every week at repowrapped.com/signal https://repowrapped.com/signal . Senior engineers who don't have time to chase every announcement tend to find it worth the inbox slot.