September 2026 Summaries

Descript, an AI video and audio editing platform, reduced the time required to evaluate new AI models for its Underlord editing agent by replacing separate provider integrations with OpenRouter’s unified routing layer. Previously, adding models from providers such as OpenAI, Anthropic, and Google required engineering work and scheduling delays that could leave promising models untested for a week; now, employees can request evaluations through Slack, where Anthropic’s Claude Tag runs tests and opens pull requests for human review, often within one or two hours. This has enabled Descript to test models several times a week, select them based on performance against its own benchmarks, and move successful releases into production quickly, including Grok 4.5 without a direct xAI integration. For production workloads, Descript can retain control through dedicated deployments, such as a Baseten-hosted open-weight model using its own key, while OpenRouter provides fallback providers that preserve the selected model if an inference host fails.

OpenRouter compared 20 image-generation models using identical 1:1 prompts on 11 September 2026, finding billed costs from $0.006 to $0.134 per image despite differing pricing units such as tokens, megapixels, and per-image rates. OpenAI’s gpt-image-2 was the cheapest tested model and produced readable text and competent edits, while Sourceful Riverflow v2.5 Pro led cited Design Arena image and editing rankings, Google Gemini 3 Pro Image was the most reliable tested option for replies containing both images and written text, and Recraft v4.1 Vector offered editable SVG output. The comparison emphasizes that listed prices may not match actual charges, prompt length and quality settings can substantially alter token-based costs, and output resolution, format, reference-image limits, seed support, and images-per-call limits vary widely across models. Tests of product-label generation showed that most selected models rendered requested text correctly, while reference-image editing revealed that models generally preserved wording but altered object details to some extent. The report recommends selecting models according to practical requirements such as volume cost, text accuracy, edit consistency, number of references, vector output, or multimodal responses, and advises developers to inspect each API response’s usage.cost and media_type fields and retrieve current endpoint specifications because pricing and capabilities change frequently.

OpenRouter’s guide explains how to build a reliable TypeScript tool-calling agent loop in which a model selects tools, an application validates and executes the requested functions, returns one result for each tool call ID, and repeats the process until the model produces a text-only response or a safety condition stops execution. Using a local weather lookup example, it demonstrates defining tools, sending tool definitions with every request, parsing JSON arguments safely, preserving assistant and tool messages in conversation history, and executing independent calls concurrently when appropriate. The guide emphasizes hard operational controls, including a positive iteration cap, repeated-call detection using tool-and-argument fingerprints, error handling that returns tool failures to the model, and careful ordering of messages so subsequent turns retain context. It also covers ordered model fallback through the models parameter, provider routing through Auto Exacto, history-size management, safe logging practices, and concurrency decisions for stateful versus independent tools. MCP servers can replace local handlers for remote tool discovery and execution, but still require the same limits and result handling, while OpenRouter’s Agent SDK is recommended when applications need managed loops, streaming, approvals, persistent state, or built-in repeated-call detection.

DeepSeek V4 is a family of models with differing input capabilities rather than a single vision-enabled model: DeepSeek V4.1 Flash and the experimental V4 Flash Vision Exp accept both text and images, while V4 Pro 0813, V4 Flash 0731, older 0423 versions, and the Flash “latest” alias are text-only. OpenRouter recommends V4.1 Flash for new image tasks because it supports native image understanding, a 1,048,576-token context window, tool calling, structured outputs, and lower listed pricing than the experimental alternative as of September 2026. Image requests can use public URLs or base64 data URLs, but sending images to text-only V4 models fails. To use a text-only V4 model, including V4 Pro, for image reasoning, users must first have a separate vision-capable model such as Qwen3.8 27B or Kimi K3 describe the image and then supply that description to V4, adding cost and removing direct pixel access. No listed V4 model supports video input, and users should verify current modalities, pricing, and aliases through OpenRouter model pages or its Models API before deploying a model.

Descript’s Underlord video-editing agent uses a single OpenRouter integration to run 13 production AI models from Anthropic, Google, OpenAI, and xAI. According to the case study, adopting this approach reduced the time required to evaluate and introduce a new model from more than a week to one or two hours, allowing the team to test models several times per week without relying as heavily on engineering resources.

Descript, an AI-powered video and audio editing company, used OpenRouter to simplify how its Underlord editing agent evaluates, deploys, and routes among frontier language models. Previously, direct integrations with OpenAI, Anthropic, and Google required engineering support for each new model because of differing parameters and custom fallback logic, making evaluation take a week or more despite only requiring a few hours of technical work. Through a single OpenRouter connection, Descript reports expanding from essentially one production model to 13 models across four developers, reducing evaluation and deployment time for promising releases to one or two hours while retaining a separate direct Anthropic connection for early-access models. Its teams use automated Slack-triggered evaluations, internal testing, pull requests, feature flags, and human approval to assess new models several times a week, including open-weight options hosted through Baseten. OpenRouter’s per-model provider routing, policy-based provider selection, and same-model fallback capability are described as helping maintain service continuity during rate limits, outages, and deployment issues without changing the model users receive. Descript says this process lowered total model spending to less than half while maintaining performance on its internal tests, and enabled other teams to switch deprecated models or prototype new use cases through configuration rather than new integrations.

LLM-as-a-judge evaluation uses a separate language model to score an AI agent’s final responses against clear, written rubrics, addressing quality gaps that deterministic tests of tool calls or exact outputs may miss. It distinguishes candidate and judge models to reduce self-preference and other biases, and supports pointwise scoring for thresholds, pairwise comparisons for model or prompt selection, and reference-based checks for factual coverage. The guide recommends deterministic validators for exact, safety-critical requirements such as schemas, calculations, permissions, and tool side effects, while using judges for semantic qualities including grounding, completeness, instruction following, tone, and correct use of retrieved information. Using OpenRouter’s Ori Eval, developers can create TypeScript-based tests that combine observable assertions with rubric scoring, run evaluations in CI, compare candidate models, and control costs through sampling and focused criteria. Reliable judging requires observable rubrics, calibration against human-labeled examples, blinded evaluation inputs, version-controlled test data and configurations, awareness of output variance and known biases, and protection of sensitive production data.

OpenRouter provides text-to-speech through its OpenAI-compatible POST /api/v1/audio/speech endpoint, allowing developers to use one API key and a consistent request format across speech models from multiple providers. Requests require a model, text input, and generally a model-supported voice, with optional output format and speed settings; successful responses return raw audio bytes, while failures return JSON and should be validated before saving. The tutorial demonstrates generating MP3 files with cURL, Python requests, JavaScript, and the OpenAI Python SDK configured with OpenRouter’s base URL, emphasizing HTTP status checks, content-type validation, and generation-ID logging. Available voices, formats, pricing, and provider-specific controls vary by model, with examples including Mistral Voxtral Mini TTS, xAI Grok Voice TTS, and Microsoft MAI-Voice-2. For production use, it recommends splitting lengthy text into segments, recording generation metadata, retrying temporary errors with backoff, avoiding retries for invalid requests or credential issues, and checking the current Models API or model pages for supported capabilities.

Zero Data Retention (ZDR) is a provider-side policy under which eligible AI inference endpoints process prompts and return responses without persistently storing either afterward, though data still travels to and is processed by the provider. It differs from no-training policies, data residency, and self-hosting: a provider may avoid training on data while retaining it temporarily, regional routing controls processing location rather than storage, and self-hosting is needed when third-party processing itself is prohibited. On OpenRouter, ZDR can be enforced through account privacy settings, guardrails, or the per-request `provider.zdr` control, while `data_collection: "deny"` can additionally exclude endpoints that non-transiently store data or may train on it. ZDR does not cover request metadata retained by OpenRouter, application logs, external tools and plugins, legal or abuse-review retention, or response caching, which must be assessed separately; in-memory provider prompt caching is considered compatible because it is not persistent storage. Organizations should verify claims at the endpoint level, examine coverage for files, tools, identifiers, caches, and metadata, use enforceable routing controls rather than manual selection, and monitor current endpoint policies as they change.

OpenRouter Fusion is a compound inference system that lets a calling model escalate difficult prompts to a panel of one to eight models, whose parallel responses are compared by a judge before the original model produces a final answer. Unlike auto-routing, which selects one suitable model, Fusion combines multiple reasoning paths, source choices, and interpretations, with the judge identifying consensus, contradictions, unique insights, and blind spots rather than merely voting. The approach is intended for complex research, expert review, due diligence, and other high-stakes decisions where improved accuracy may outweigh additional expense, while it is less suitable for real-time chat, simple extraction or rewriting tasks, and reproducibility-sensitive evaluations because it typically costs four to five times more than a comparable single completion, takes two to three times longer, and produces variable results across runs. Benchmark results cited for the DRACO deep-research test indicate that synthesis and model diversity can improve performance, though gains vary by task and do not necessarily apply to coding or general chat. Fusion is available through a web lab, the openrouter/fusion API model alias, or a server tool, with configurable presets for high-quality, budget, or faster panels and options to choose the judge model or require deliberation.

OpenRouter presets provide a config-as-code approach for LLM requests by storing versioned model selections, fallback chains, system prompts, provider-routing rules, sampling settings, and tools under a reusable name. Applications can reference a preset through the model field using a format such as “@preset/name,” allowing configuration changes made in the OpenRouter dashboard to take effect across API integrations, scripts, notebooks, and compatible third-party clients without code changes or redeployments. Request-level settings can override most preset values, while tool definitions are merged, and presets may also be created through the API. The guide demonstrates presets for consistently enhancing image prompts with a text model and image-generation tool, and for preserving a Fusion panel configuration across applications. Saving changes creates a new active version, while earlier versions can be restored if necessary, enabling teams to centrally manage and share model behavior, prompts, routing, and evaluation configurations.

OpenRouter has launched US In-Region Routing to complement its existing EU option, allowing Business and Enterprise customers to ensure AI requests are decrypted, processed, and served entirely within the selected US or EU region. Users can switch to region-specific API endpoints without changing API keys, request formats, model IDs, or existing provider settings, while regional Guardrails can enforce that designated workspaces, teams, or keys use only the approved endpoint. Regional catalogs include only models with an available in-region provider, and unavailable requests return a 404 rather than falling back to another jurisdiction. The service is intended to address data-residency and compliance requirements that global endpoints may not satisfy even for models developed by US or EU labs. It also enables regional access to certain Chinese open-weight models hosted by US or EU providers, separating model hosting from the originating lab. OpenRouter distinguishes its approach from inference-only regional routing by keeping requests, processing, provider inference, and supported server tools within the selected region, disabling tools that could transmit data outside it.

Seedance 2.5 is ByteDance’s OpenRouter video-generation model, released in August 2026, designed primarily for 4-to-30-second continuous scenes, editing or extending existing footage, and reference-guided work using images, video, or audio. It supports 480p and 720p output across six aspect ratios, first- and last-frame control, and synchronized audio at no additional charge, although seeds do not ensure fully reproducible results. Pricing is based on video tokens that scale with resolution and duration, averaging about $0.103 per second at 480p and $0.231 at 720p, while projects using video references receive a roughly 40% lower token rate. The review positions the model as especially useful for long takes and footage continuity, but less suitable for projects requiring 1080p or 4K, the lowest available cost, or frame-exact outputs. Seedance 2.0 is recommended for higher-resolution work, Wan 3.0 for cheaper 30-second text-to-video generation, and Veo 3.1 for short fixed-length 4K clips. Requests are submitted through OpenRouter’s asynchronous video API, then monitored until completion before downloading the result.

The guide explains how to edit existing images through OpenRouter’s API using Google’s Gemini “Nano Banana” image models, particularly the default google/gemini-3.1-flash-image model, by submitting a source image in input_references alongside a text editing instruction in prompt. It provides Python, TypeScript, and SDK-based examples for encoding local images as base64 data URLs, using public image URLs, decoding the base64-edited result returned in data[0].b64_json, and saving it to disk. It distinguishes image editing from text-to-image generation, recommends prompts that explicitly state both the desired change and elements to preserve, and advises performing complex work through small sequential edits by reusing each result as the next source image. The guide also compares available Nano Banana variants by speed, cost, and quality, notes that compatible alternatives such as OpenAI image models can be selected by changing the model field, and outlines practical concerns including supported formats, URL accessibility, oversized files, response errors, rate limits, retries, cost logging, and protecting API keys through environment variables.

OpenRouter has introduced beta Shell and Bash server tools, a Files API, and hosted Linux containers that let any tool-calling model execute commands, process uploaded files, and retain outputs across related requests. The OpenAI-compatible `openrouter:shell` and Anthropic-compatible `openrouter:bash` tools can run commands in OpenRouter’s sandbox when configured with the `openrouter` engine, returning command output, errors, exit codes, and changed-file identifiers so models can iteratively diagnose and correct work. Containers are isolated per workspace, can be reused through session or container IDs, sleep after five minutes of inactivity, restrict network access by default, and preserve files created under the designated home directory. The Files API supports uploading inputs, attaching up to 20 files to containers as writable copies, downloading generated container files, and promoting retained outputs into workspace storage, while web search and shell can be combined to research information externally and create files without granting containers internet access. Sandbox execution costs $0.0001 per active second with a 30-second minimum for cold containers, Files API usage is included with a 10 GiB storage limit, and workspace administrators can disable individual server tools for all API, chatroom, and preset requests.