Auto Router (Beta)
The experimental version of our Auto Router where we test new improvements. Use it to get the latest and greatest version of our general purpose auto router, but expect beta...
Anyone in the Project can @-mention Auto Router (Beta) with the team's shared context - pooled credits, one chat, one memory.
Starter is free forever - 1 Project, 100 credits/month, 1 MCP. No card.
Verdict
Best for
- Prototyping with minimal model research
- Cost-sensitive batch processing tasks
- Exploratory data analysis workflows
- Low-stakes content generation at scale
Strengths
Auto Router eliminates model selection paralysis by routing requests to whichever backend offers the best speed-cost-availability mix at query time. The 2M token context window suggests it can handle long documents when routed to appropriate models. Multi-modal support (text, image, audio, video, file) means you can throw varied input types at it without pre-filtering. For teams running thousands of requests where individual output variance is acceptable, this reduces both decision fatigue and average spend.
Trade-offs
You lose reproducibility — the same prompt may hit different models on successive runs, making A/B testing or debugging nearly impossible. Pricing is opaque (listed as unknown), so cost forecasting requires post-hoc analysis. Without public benchmarks, you're flying blind on capability floors; a critical prompt might land on a weaker model during peak load. Teams needing consistent voice, format adherence, or audit trails will find this router frustrating. The beta label signals expect breaking changes and limited support.
Specifications
- Provider
- openrouter
- Category
- image
- Context length
- 2,000,000 tokens
- Max output
- —
- Modalities
- text, image, audio, file, video
- License
- proprietary
- Released
- 2026-07-17
Pricing
- Input
- —
- Output
- —
- Model ID
openrouter/auto-beta
Per-token prices show what the model costs upstream. On Switchy your team draws from one shared org credit pool - one plan, one balance for everyone.
Providers
| Provider | Context | Input | Output | P50 latency | Throughput | 30d uptime |
|---|---|---|---|---|---|---|
| openrouter | 2000k | $0.00/Mtok | $0.00/Mtok | — | — | — |
Performance
Benchmarks
Works well with
Top MCPs
Compatibility data comes from first-party telemetry; once we have enough co-usage signal, top MCPs for this model will appear here.
How Switchy teams use it
Starter prompts
Summarize Research PDFs
Read this PDF and provide a 200-word summary covering the research question, methodology, and main findings. Focus on actionable insights.
Classify Support Tickets
Classify this support ticket into one of these categories: billing, technical, feature request, or other. Provide the category name and a one-sentence justification.
Generate Product Descriptions
Write a 50-word product description for this item emphasizing benefits over features. Use an enthusiastic but professional tone.
Extract Data from Screenshots
Extract all visible text, numbers, and labels from this screenshot into a JSON object. Use descriptive keys for each field you identify.
Brainstorm Campaign Ideas
Suggest five marketing campaign ideas for this product targeting small business owners. For each idea, include a headline and two-sentence pitch.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
Generate a product photo of a minimalist ceramic coffee mug on a wooden surface with soft morning light. Clean background, professional e-commerce style.
The router selects an image generation model optimized for photorealistic product rendering. The output shows a cream-colored ceramic mug positioned at a slight angle on light oak wood. Soft directional lighting from the left creates subtle shadows and highlights the mug's smooth glaze. The background fades to a clean off-white gradient. The composition follows rule-of-thirds framing with sharp focus on the mug's rim and handle, while the wood grain provides natural texture without competing for attention.
Auto Router's strength here is model selection intelligence — it routes product photography requests to models trained on commercial imagery rather than artistic generation. The 2M token context window allows detailed style references to be included. Trade-off: pricing uncertainty ($? per Mtok) makes cost optimization difficult to predict across different routed models.
Create an editorial illustration for a tech article about AI ethics. Abstract geometric shapes, muted color palette, conveys complexity and human oversight. 16:9 aspect ratio.
The router directs this to a model specializing in conceptual illustration. The output features overlapping translucent geometric forms — hexagons and circles in slate blue, warm gray, and muted coral — arranged to suggest both structure and ambiguity. A subtle human silhouette outline appears integrated within the largest shape, implying human agency. The composition uses negative space effectively, with forms concentrated in the left two-thirds. The style reads as modern editorial: clean enough for publication, abstract enough to avoid literal interpretation.
The router distinguishes between photorealistic and illustrative requests, routing to appropriate specialized models. This example shows its ability to handle conceptual briefs that require artistic interpretation rather than literal rendering. Trade-off: with no public benchmarks available, output quality consistency across different prompt types remains unverified.
Design a fantasy character concept: a forest guardian with bioluminescent markings, wearing organic armor made from bark and moss. Full body, three-quarter view, painterly style.
The router selects a model trained on character design and fantasy art. The output depicts a tall, lithe humanoid figure with skin in deep forest green tones. Glowing cyan markings trace patterns along the arms and face, suggesting veins of light beneath the surface. The armor appears grown rather than crafted — shoulder pieces of gnarled bark, chest plate woven from living vines, moss accents at joints. The three-quarter pose shows both front detail and the flowing cape of leaves. Painterly brushwork is visible in the texture rendering, giving it concept-art quality rather than photorealistic finish.
Auto Router handles creative character design by routing to models with strong performance on stylized, imaginative content. The multi-modal input support (text, image, audio, file, video) means reference images could supplement the text prompt for style consistency. Trade-off: beta status suggests routing logic is still being refined — edge cases in prompt interpretation may route to suboptimal model choices.
Use-case deep-dives
When Auto Router handles mixed-media moderation at scale
A 12-person social platform team needs to moderate user uploads—screenshots with text overlays, short videos with audio, PDFs with embedded images—without maintaining separate pipelines for each format. Auto Router's multi-modal support (text, image, audio, video, file) means one API call handles any upload type, and the 2M token context window lets you batch hundreds of items per request to cut latency. The trade-off: pricing is unlisted, so you're flying blind on cost until you test in production. If your moderation volume is under 10K items/day and you can afford to prototype without a rate card, Auto Router eliminates the format-switching tax. For higher volumes or strict budget control, wait until OpenRouter publishes the per-Mtok rates or build separate pipelines with known-cost models.
Why Auto Router works for 500-page reports with charts
A 4-person consulting firm turns client RFPs—dense PDFs mixing tables, diagrams, and 200+ pages of text—into structured summaries for proposal teams. Auto Router's 2M token context means you can ingest an entire document in one pass without chunking, and file + image modalities let it parse both the layout and the visuals. The router logic theoretically picks the cheapest capable model for each request, but with no published pricing you can't validate the savings claim or forecast monthly spend. If you're processing under 50 documents/month and need the convenience of single-call ingestion more than cost predictability, Auto Router is the simplest path. Beyond that threshold, test against a known-cost alternative like Claude 3.5 Sonnet to confirm the routing actually saves money.
When Auto Router's audio+video support beats separate tools
A 20-person customer success team records Zoom calls (video + audio + screen shares) and needs same-day transcripts with speaker labels and slide context. Auto Router handles video and audio natively, so you skip the export-to-audio step and preserve visual cues (who's presenting, what's on screen) in the transcript. The 2M token window fits a 90-minute call with room for prompt instructions. The catch: beta status and missing pricing mean you're adopting before the SLA or cost structure is stable. If your call volume is under 30/week and you're comfortable with beta risk, Auto Router collapses three tools (video processor, transcriber, slide OCR) into one. For production-critical workflows or higher volume, wait for GA and published rates or use a dedicated transcription service with known uptime guarantees.
Frequently asked
Is Auto Router good for image generation?
Auto Router doesn't generate images itself — it's a routing layer that picks the best available model for your prompt. For image generation, it'll route to models like FLUX or Stable Diffusion based on your requirements. If you need consistent results from a specific model, use that model directly instead of relying on the router's selection logic.
How much does Auto Router cost compared to using models directly?
OpenRouter hasn't published fixed pricing for Auto Router because costs depend on which underlying model it selects for each request. You'll pay whatever that chosen model costs, potentially plus a small routing fee. For predictable budgets, pick a specific model rather than letting the router decide — you'll know exactly what you're paying per token.
Can Auto Router handle large context windows for multi-image tasks?
The 2M token context window is theoretical capacity, not practical image-processing ability. Auto Router routes to models with varying context limits, so your actual window depends on which model it picks. For reliable multi-image workflows with known context needs, specify a model like GPT-4o or Claude that documents its image-handling limits rather than gambling on router selection.
Should I use Auto Router instead of GPT-4o for vision tasks?
Only if you want OpenRouter to experiment with model selection for you. GPT-4o gives you consistent vision performance and documented capabilities. Auto Router might route to GPT-4o, or it might pick something cheaper or newer based on heuristics you can't control. Use Auto Router for exploration; use GPT-4o when you need reliability and can't afford surprise model swaps mid-project.
Is Auto Router stable enough for production image workflows?
No. It's marked Beta, has no published benchmarks, and its routing logic is opaque. You can't guarantee which model handles your request, making debugging impossible when results vary. For production, pin to a specific model with known performance characteristics. Use Auto Router only for prototyping or when you're actively testing multiple models and want OpenRouter to handle the switching.
Compare with
More image models
- Google: Nano Banana 2.1google
- Google: Nano Banana 2 (Gemini 3.1 Flash Image)google
- Google: Nano Banana 2 (Gemini 3.1 Flash Image Preview)google
- Google: Nano Banana 2 Lite (Gemini 3.1 Flash Lite Image)google
- Google: Nano Banana (Gemini 2.5 Flash Image)google
- Google: Nano Banana Pro (Gemini 3 Pro Image)google
- Google: Nano Banana Pro (Gemini 3 Pro Image Preview)google
- OpenAI: GPT-5.4 Image 2openai
- OpenAI: GPT-5 Imageopenai
- OpenAI: GPT-5 Image Miniopenai
- Auto Routeropenrouter