Showing 1–15 of 15 dossiers

OpenAI lets one API project choose regional processing per request

OpenAI’s August 21 control moves processing-region choice into request routing: a single Global project can send eligible calls to regional base URLs. That simplifies multi-region SaaS architecture, but builders still need to enforce residency policy in code and account for support, retention and pricing constraints.

Qwen3.8-27B brings stronger agentic coding into a locally deployable 27B model

Qwen3.8-27B is now available as open weights on Hugging Face and ModelScope. For builders, the important change is not another benchmark bump: a comparatively compact 27B model now combines native vision, long context, controllable reasoning and OpenAI-compatible serving paths for local or self-hosted coding and agent workloads.

Azure Document Intelligence v2.0 API retires August 31 — old integrations need a version migration

Azure Document Intelligence v2.0 reaches retirement on August 31, 2026. Microsoft recommends moving workloads to the current v4.0 API; the post-v2 REST surface was redesigned, so teams should verify the actual api-version their SDK or HTTP client sends rather than assuming a package upgrade is enough.

Inference is where an AI product meets its latency target, reliability budget and monthly bill. Model quality matters, but so do rate limits, caching, batching, regional availability, data terms, observability and the provider behaviour that only appears under production traffic.

BTN tracks important API launches, price changes and serving techniques across hosted and self-managed systems. Coverage connects provider documentation with benchmarks and operating experience so builders can compare more than headline token prices. The useful outcome is knowing when an infrastructure change makes a product newly viable, when migration is worth the work and where apparent savings hide another constraint.

The beat includes routing layers, gateways and compatibility standards when they reduce switching cost or improve control. It also watches changes to retention, abuse monitoring and service terms, because the fastest endpoint is not a safe default if its data handling conflicts with the product being built.