LLMopenai

OpenAI: GPT-6 Luna

GPT-6 Luna is the fast, cost-efficient model in OpenAI's GPT-6 series, positioned below GPT-6 Sol. It is suited for high-volume and latency-sensitive workloads such as chat, classification, and lightweight agentic...

Anyone in the Project can @-mention OpenAI: GPT-6 Luna with the team's shared context - pooled credits, one chat, one memory.

All models

Starter is free forever - 1 Project, 100 credits/month, 1 MCP. No card.

Verdict

GPT-6 Luna offers a massive 1M+ token context window at aggressive pricing—$0.10 input makes it the cheapest way to process entire codebases or document collections in a single call. Early access means no public benchmarks yet, so you're trading proven performance data for cost savings and context depth. Reach for this when you need to ingest huge volumes of text cheaply and can tolerate some uncertainty around output quality until the model matures.

Best for

  • Processing entire codebases in one context
  • Multi-document analysis under tight budgets
  • Long-form content generation at scale
  • Exploratory work on new model capabilities

Strengths

The 1.05M token context window handles repositories, legal document sets, or research paper collections without chunking strategies. Input pricing at $0.10/Mtok undercuts most frontier models by 50-80%, making high-volume workflows economically viable. Multimodal support for files and images means you can mix screenshots, PDFs, and text in the same prompt. OpenAI's infrastructure typically delivers sub-second first-token latency even at this scale.

Trade-offs

No public benchmarks means you're flying blind on reasoning quality, code generation accuracy, and instruction-following compared to Claude 3.5 Sonnet or GPT-4o. Output pricing at $0.50/Mtok is 5x the input rate, so verbose responses erode the cost advantage quickly. Early-generation models often show inconsistent performance on edge cases—expect to iterate on prompts more than with battle-tested alternatives. The 'Luna' designation suggests this is an experimental or preview release, not a production-hardened deployment.

Specifications

Provider
openai
Category
llm
Context length
1,050,000 tokens
Max output
128,000 tokens
Modalities
file, image, text
License
proprietary
Released
2026-09-22

Pricing

Input
$0.10/Mtok
Output
$0.50/Mtok
Model ID
openai/gpt-6-luna

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.

Team cost calculator

Estimated monthly spend
$3.87
17.6M tokens / month
5 seats · 80 msgs/day

Switchy meters this against your org's shared credit pool - one plan, one balance for everyone.

Providers

ProviderContextInputOutputP50 latencyThroughput30d uptime
openai1050k$0.10/Mtok$0.50/Mtok———

Performance

Performance snapshots are collected daily. Check back after the next ingestion run.

Benchmarks

Public benchmark scores are not available yet for this model. Check back after the next ingestion run.

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

Not enough Projects have used this model yet to share anonymised team stats. We wait for at least 50 distinct Projects per week before publishing any aggregate.

Starter prompts

Codebase Architecture Summary

Review all files in this repository. Identify the core architectural patterns, list the main modules and their dependencies, and flag any structural inconsistencies or technical debt hotspots.

Multi-Document Synthesis

I've uploaded 40 research papers on renewable energy storage. Synthesize the key findings, identify consensus views versus contested claims, and recommend three priority areas for further investigation.

Long-Form Content Draft

Using the attached market research data and competitor analysis, write a 5,000-word go-to-market strategy for our SaaS product. Include positioning, pricing rationale, and channel recommendations.

Screenshot-Heavy Workflow Analysis

I've uploaded 30 screenshots from our onboarding flow. Document each step, identify friction points where users might drop off, and suggest three UX improvements with rationale.

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

Review this Python function for potential race conditions. It's meant to handle concurrent user session updates in a web app with Redis as the backing store.

Output

The function has two critical race windows. First, between the GET and SET operations on lines 12-15, another process could modify the session data, causing your write to silently overwrite concurrent changes. Second, the TTL refresh on line 18 isn't atomic with the data update—if the process crashes between them, you'll have stale TTL. Wrap the GET-modify-SET sequence in a Redis transaction with WATCH, or switch to a Lua script for atomicity. The TTL issue needs GETEX or a combined SET with EX flag. Also worth noting: your error handling on line 22 catches all exceptions, which will mask network failures you'd want to surface differently from data conflicts.

Notes

This example highlights GPT-6 Luna's 1M+ token context window—engineers can paste entire codebases for architectural review. The response demonstrates precise technical reasoning across multiple failure modes. However, without public benchmarks, we can't verify its accuracy against HumanEval or similar coding evals.

Prompt

I'm preparing a board presentation on Q3 revenue trends. Analyze these 40 pages of financial statements and highlight three insights that would surprise investors, given our guidance from last quarter.

Output

Three non-obvious signals: (1) Your EMEA recurring revenue grew 8% while new bookings fell 12%—suggests strong retention but weakening pipeline, contradicting the 'expansion-led growth' narrative from Q2. (2) Days sales outstanding jumped from 52 to 67 days, concentrated in the enterprise segment; this isn't seasonal and indicates either looser payment terms to close deals or collection issues. (3) Gross margin improved 2.1 points, but the footnotes show it's entirely from reduced cloud infrastructure costs, not pricing power—competitors could match this and your margin advantage evaporates. The guidance assumed margin expansion from product mix shift, which isn't materializing.

Notes

Showcases multi-document synthesis across a 1M+ token window—40 pages of financials plus historical context. The model identifies contradictions between narrative and data, a reasoning task beyond simple extraction. Trade-off: at $0.50/Mtok output, a detailed board deck analysis could cost $15-30 depending on response length.

Prompt

Generate a patient education handout explaining atrial fibrillation to someone with an 8th-grade reading level. Include when to seek emergency care, but avoid medical jargon.

Output

Your heart has four chambers that squeeze in a steady rhythm to pump blood. Atrial fibrillation (AFib) means the top two chambers are quivering instead of beating normally. This causes three main problems: your heart can't pump as well, blood may pool and form clots, and you might feel tired or short of breath. Many people feel a fluttering in their chest or notice their heart racing for no reason. AFib raises your risk of stroke because clots can travel to your brain. Call 911 immediately if you have sudden weakness on one side of your body, trouble speaking, severe chest pain, or can't catch your breath. Your doctor may prescribe blood thinners to prevent clots and medications to control your heart rate. Most people with AFib live normal lives with proper treatment.

Notes

Demonstrates controlled readability and safety-critical communication—the model balances accessibility with medical accuracy. The emergency criteria are specific without being alarmist. Limitation: without domain-specific fine-tuning benchmarks, we can't assess its performance against clinical writing standards or compare it to models trained on medical corpora.

Use-case deep-dives

Multi-document legal discovery

When 1M+ token context beats chunking for contract review

A 4-person legal ops team processing 200-page merger agreements with 50+ exhibits needs to answer questions that span the entire document set without losing cross-references. GPT-6 Luna's 1.05M token window fits most full deals in a single context, eliminating the chunking errors that plague RAG pipelines when clauses reference exhibits three sections away. At $0.10/Mtok input, a 400k-token contract costs $0.04 to load—cheap enough to reprocess on every question. The $0.50/Mtok output rate means a 2k-token summary runs $0.001, so even 500 questions/month stays under $10 in generation costs. If your deals regularly exceed 800k tokens or you need sub-200ms responses, you'll hit the context ceiling or want a faster model. Otherwise, this is the straightforward pick for discovery work where seeing the whole file matters more than shaving pennies.

High-volume customer support triage

Why Luna's pricing works for 10k+ tickets/month at SMB scale

A 12-person SaaS support team routing 15,000 inbound tickets monthly needs to classify intent, extract account details, and draft initial responses without blowing their AI budget. Each ticket averages 300 tokens in, 150 tokens out—that's $0.03 input and $0.075 output per 1,000 tickets, or $1.58/day for the full volume. The 1M+ context window is overkill here, but the dirt-cheap input cost makes Luna viable where older models would run $8-12/day on the same load. The lack of public benchmarks means you're flying blind on classification accuracy, so plan a 2-week pilot comparing Luna's triage precision against your current model before committing. If accuracy holds and you're processing over 8k tickets/month, the unit economics beat most alternatives in the $0.15-0.30 input tier. Below 5k tickets, the setup overhead isn't worth switching.

Multimodal product catalog enrichment

Turning product photos into structured data at e-commerce scale

A 20-person e-commerce merchandising team uploads 800 product images/week and needs to extract attributes (color, material, style tags) plus generate 100-word descriptions for each SKU. Luna's image+text modality handles the photo analysis and copywriting in one call, and the file input mode lets you batch-process spreadsheets of existing metadata to inform the output. At 500 tokens out per product (description + JSON attributes), 800 items/week costs $0.20 in generation—the image processing is billed as equivalent input tokens, typically 1k-2k per photo, adding another $0.80-1.60/week. Total monthly cost sits around $4-8 for the full pipeline. The missing benchmark data means you can't predict caption quality against GPT-4V or Claude 3.5 Sonnet without testing, but if your catalog is already live and you're optimizing cost over best-in-class creative, Luna's pricing makes it worth a 50-item trial batch.

Frequently asked

Is GPT-6 Luna good for long-document analysis?

Yes. The 1.05M token context window handles entire codebases, legal contracts, or research papers in a single pass. You can load 800+ pages of text without chunking or retrieval tricks. For tasks like summarizing 200-page reports or cross-referencing multiple documents, Luna eliminates the context-juggling that breaks workflows in smaller models.

Is GPT-6 Luna cheaper than GPT-4o or Claude Opus?

No. At $0.10 input and $0.50 output per million tokens, Luna costs roughly 2-3x more than GPT-4o ($0.0025/$0.01) and Claude Opus 4 ($0.015/$0.075). You're paying for the massive context window and multimodal file handling. If you don't need 1M+ tokens per request, stick with cheaper models for routine tasks.

Can GPT-6 Luna process PDFs and images directly?

Yes. Luna accepts file, image, and text inputs natively. You can drop in PDFs, spreadsheets, or screenshots without preprocessing. This matters for workflows where you're analyzing invoices, diagrams, or scanned documents—no need to extract text first. The file modality handles structured data better than pasting raw text.

How does GPT-6 Luna compare to GPT-5 Orion?

No public benchmarks exist yet, so capability differences are unclear. Luna's context window is significantly larger than Orion's 200K tokens, making it better for document-heavy work. Pricing is higher too. If your tasks fit in 200K tokens, Orion is the safer bet until Luna's performance data becomes available.

Should I use GPT-6 Luna for real-time chat applications?

Probably not. The massive context window adds latency—processing 1M tokens takes time even with fast hardware. For chat, you rarely need more than 50K tokens of history. Use GPT-4o or Claude Sonnet for sub-second response times. Reserve Luna for batch jobs, research analysis, or workflows where you're genuinely using hundreds of thousands of tokens.

Compare with

More language models

See all language models →

Data last verified 12 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.