Best forBest first test for classification, structured extraction, grounded answers, and narrow agent steps that need to run often.
Per 1M tokens · base list tier
GPT-6 Luna and GPT-6 Sol share a 1,050,000-token context window, a 128,000-token maximum output, and text-and-image input. They are not interchangeable defaults. OpenAI positions Luna for focused, high-volume work and Sol for complex coding and agentic workflows. On GPTProto, the current displayed rates are $0.08 input / $0.40 output for Luna and $1.60 input / $8.00 output for Sol per million tokens. Check the live pricing panels before budgeting.
The short answer: start with Luna for repeatable tasks with clear acceptance criteria. Trial Sol for multi-file coding, ambiguous reasoning, and agent runs where fewer failed attempts could justify the higher token rate. Choose with a test set and a cost-per-successful-task calculation, not a model-name ranking.
Best forBest first test for classification, structured extraction, grounded answers, and narrow agent steps that need to run often.
Per 1M tokens · base list tier
Best forBest first test for complex code changes, code review, debugging across files, and multi-step agent work.
Per 1M tokens · base list tier
GPTProto rates below are the catalog prices checked on October 13, 2026. They are the prices to use for a GPTProto comparison; review the current pages before budgeting production traffic. Release dates follow the OpenRouter canonical slugs gpt-6-luna-20260922 and gpt-6-sol-20260922.
curl https://gptproto.com/v1/chat/completions \
-H "Authorization: Bearer $GPTPROTO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-6-luna",
"messages": [{"role": "user", "content": "Hi"}]
}'curl https://gptproto.com/v1/chat/completions \
-H "Authorization: Bearer $GPTPROTO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-6-sol",
"messages": [{"role": "user", "content": "Hi"}]
}'Prices per 1M tokens. Official list rates from the GPTProto catalog (raw price / 740). GPTProto rates apply price_multiplication 0.8. The 272K long-context tier is the official price in extend_config, converted with the same multiplier. Latency and benchmarks are OpenRouter figures as of 2026-10-14.
GPTProto’s displayed rates put Luna at $0.08 input / $0.40 output and Sol at $1.60 input / $8.00 output per million tokens. Sol is 20 times Luna’s listed input and output rate. For an illustrative request with 10,000 uncached input tokens and 1,000 output tokens, those displayed rates imply $0.0012 for Luna or $0.024 for Sol. That calculation covers only those input and output tokens; cached input, cache writes, tools, retries, and other usage can change a complete bill.
A 20× rate gap is significant on repeated calls. But the cheaper call is not automatically the cheaper completed task. If Luna needs many retries or escalations on difficult work, compare the total tokens and accepted outcomes against a Sol run. OpenAI applies higher long-context rates above 272,000 input tokens. The catalog stores those official tiers ($0.20/$0.75 for Luna and $4/$15 for Sol per million) and converts them with the 0.8 multiplier. Confirm GPTProto billing for long prompts before extrapolating from the displayed base rates.
Check the current Luna rate and Sol rate before making a production estimate.
Calculate base token costs for both models using the same expected input and output volume. Then add real observations: prompt-caching behavior, retry rate, tool-call cost, and the percentage of tasks each model completes to your standard.
Excludes top-up bonus credits. Priced at the base tier, not the over-272K long-context tier. Confirm GPTProto billing before you extrapolate a long-prompt budget.
OpenAI describes Luna as its efficient option for focused, high-volume work, while Sol targets more complex coding and agents. That positioning is useful, but it is not a measured latency or uptime guarantee for GPTProto. Request length, output length, reasoning effort, tool usage, and live conditions all affect completion time.
OpenRouter figures as of 2026-10-14. Provider medians are not a GPTProto SLA. Chat Completions function calling is documented by OpenAI only when reasoning effort is none; confirm the live GPTProto route.
Use one GPTProto account and balance to test both models at their displayed rates. That makes it practical to start routine steps on Luna and selectively test Sol for work that needs more reasoning. Check the selected endpoint’s API Usage panel for available controls.
Get started. Great for testing the endpoint and trying new models.
The sweet spot for individual developers and small projects shipping to production.
Built for teams running production workloads. Bonus credits stack on already-discounted model pricing.
Luna fits tasks with a bounded answer: label a support message, extract fields, summarize a retrieved passage, or handle a small code change with a direct test. Sol is the more relevant candidate when an agent needs to plan across files, interpret several tool results, debug a difficult failure, or review a substantial patch. A published benchmark cannot decide your routing rule on its own.
Artificial Analysis and Vals AI figures as listed on OpenRouter, 2026-10-14. Neither model had a Design Arena rank on that check.
Route by the acceptance test, then escalate when that test fails.
Route routine requests to Luna and move a request to Sol after a failed validation, repeated retries, or a clear complexity signal. Compare this mixed workflow with an all-Luna and an all-Sol baseline. Count the cost and latency of the full task, including every escalated attempt.
Both models publish a 1,050,000-token context window, a 922,000-token maximum input, and a 128,000-token maximum output. They take text and images as input and return text. Matching limits do not mean equal performance on long documents or complex visual references. Retrieve relevant material, preserve room for the answer, and test quality at the prompt lengths you actually use. These are OpenAI model limits, not a guarantee that every GPTProto route accepts a request at the maximum size.
GPTProto also has model-specific Luna file-analysis and Sol file-analysis pages, plus Luna web-search and Sol web-search routes. Check each route’s live request schema before relying on a capability in production.
Create a small evaluation set that mirrors production: routine classification, a longer document task, a multi-file code change, and a task your current system often fails. Run both models with comparable prompts, tools, reasoning settings, and acceptance tests. Separate cheap successes from expensive failures. Report cost per accepted result, not just price per million tokens; then decide which tasks stay on Luna and which earn escalation to Sol.
Both model pages include current pricing, API examples, and a Playground. Copy the model ID and route from the relevant page, test the same real workload, and select the default or escalation rule that meets your quality, speed, and budget requirements. GPT-6 Sol is not GPT-6.1 Sol. Browse OpenAI models on GPTProto.
Yes. On October 13, 2026, GPTProto displays $0.08 input / $0.40 output per million tokens for Luna and $1.60 input / $8.00 output for Sol. Sol’s listed input and output rates are 20 times Luna’s. Review each live model page for current pricing and any other applicable charges.
Start Luna on narrow steps with direct tests. Trial Sol on cross-file changes, difficult debugging, and multi-step agent work. Use the same tools and acceptance criteria, and compare successful completions, retries, elapsed time, and total spend.
No. OpenAI lists a 1,050,000-token context window, a 922,000-token maximum input, and a 128,000-token maximum output for both. Those limits do not guarantee equal accuracy on long inputs, or that every GPTProto route accepts the maximum size.
Yes. OpenAI lists text and image inputs and text output for both models. For image creation, choose a dedicated image-generation model instead.
OpenAI’s model documentation supports tool calling through its Responses API. For Chat Completions, OpenAI documents function calling only when reasoning effort is set to none. Verify the route and supported controls in GPTProto’s API Usage panel before deploying a tool-using agent.
No. GPT-6 Sol and the newer GPT-6.1 Sol have separate model pages and IDs on GPTProto. This comparison is specifically about gpt-6-luna versus gpt-6-sol.
Yes. The catalog includes GPT-6 Luna and GPT-6 Sol pages with pricing, API examples, and a Playground. The OpenAI model catalog shows the current lineup.
Creators and developers share the models and workflows they built with.
For a team already juggling DeepSeek, Kimi, Qwen, or other providers, a shared routing layer can be reasonable if it removes duplicated work and the fallback behavior is tested. GPTProto is one implementation of this approach.

I've been testing GPTProto recently, and it's honestly made my creative workflow much simpler. Instead of paying for multiple subscriptions, I can access several leading AI models from one place.

I turned this single prompt into a cinematic fantasy video using GPTProto. "Continuous 15-second cinematic shot, 4K resolution, hyper-realistic dark fantasy photorealism…"

I challenged myself to create a cinematic AI cooking short in just 15 seconds. I used GPTProto to bring the entire workflow together, from image generation to video, all in one place.

Made with Seedance 2.0 + GPT Image 2 on GPTProto. A Pixar-style commercial with the perfect glow.
What worked for me was pointing the cloud connections at GPTProto so the frontend only sees one endpoint and I just change the model name to swap. I am not rebuilding a connection from scratch every time.
I route the calls through GPTProto so a fallback is a config switch instead of a weekend rewrite when a model disappears. It turns "my default model just got export controlled" from an incident into a config change.

I used to switch between different AI tools just to compare results. Now I just use GPTProto. GPT-5, Claude, Gemini, Kimi, and more — all in one workspace.
I route the calls through GPTProto so the model id and latency land in one place regardless of which provider is behind it. The win is having the log schema consistent across providers.

I created this 15-second cinematic product video with GPTProto using Seedance 2.0, and I was really impressed by how smooth the workflow was.

GPTProto routes the character prompt and shot list to a top model on one API key: 20 minutes … voices it and burns in captions from the same key: 20 minutes.
Text, images, and voice are configured separately. You can keep OpenRouter for text and use GPTProto for visuals.
The call layer underneath the router is GPTProto, so swapping a model does not require provisioning a new provider integration. Changing models becomes cheap enough that the question stops being "should we change."
Compare models, learn API setup, and explore image and video workflows for real projects.
Create images and videos online, or bring text, image, and video models into your app with one API key. Explore discounted rates on selected models.