GPT-6 Sol vs GPT-6.1 Sol: API price and setup

This page compares the exact API IDs `gpt-6-sol` and `gpt-6.1-sol`. Both are Codex models, so the client setup is shared; only the model value and token rates change. OpenAI GPT-6 Sol: the official column uses the verified Standard rate for requests below 272,000 input tokens. The monthly example assumes each request stays below that limit.

Short answer

Input and output rates match at $0.20/$1.00; GPT-6.1 Sol has the lower cache-read rate ($0.01 vs $0.02 per 1M tokens). For cached input, that is the only price difference shown.

These are price estimates, not measured benchmarks. The monthly example excludes cache, tools and differences in actual usage.

Token prices on the same basis

All values are USD per 1M tokens. Code By AI rates come from the live billing catalog and include the published multiplier. Only the Claude rows have comparable 5-minute and 1-hour cache writes.

ModelMetricCode By AIOfficial listOpenRouter
GPT-6 Solgpt-6-solInput$0.20$2.00$2.00
Cache read$0.02$0.20$0.20
Cache write (5 min)Not applicableNot applicableNot applicable
Cache write (1 hour)Not applicableNot applicableNot applicable
Output$1.00$10.00$10.00
GPT-6.1 Solgpt-6.1-solInput$0.20$2.00$2.00
Cache read$0.01$0.10$0.10
Cache write (5 min)Not applicableNot applicableNot applicable
Cache write (1 hour)Not applicableNot applicableNot applicable
Output$1.00$10.00$10.00

Official list: gpt-6-sol ·

OpenRouter standard endpoint (verified): openai/gpt-6-sol · openai · openai/gpt-6-sol-20260922 ·

OpenRouter standard endpoint (verified): openai/gpt-6.1-sol · openai · openai/gpt-6.1-sol-20260929 ·

OpenRouter cells show a number only when the exact provider model ID and rate basis were checked against this catalog row. Cells marked Not verified have no such evidence. Credit-purchase fees and other OpenRouter plans are separate and are never added to the per-token prices here. OpenRouter pricing and FAQ · FAQ

OpenRouter: OpenAI provider, 1,050,000-token context. Verified base rates apply below 272,000 input tokens per request and matched the catalog vendor fields; they are recorded here. Above that threshold OpenRouter lists higher rates. Batch, Priority and regional endpoints are excluded. /pricing

Monthly arithmetic example

At 20M input and 2M output tokens per month, using the rates above:

ModelOfficial list / monthCode By AI / month
GPT-6 Solgpt-6-sol$60.00$6.00
GPT-6.1 Solgpt-6.1-sol$60.00$6.00

Which choice fits which work?

Rows restate catalog arithmetic and official guidance. They are not Code By AI benchmarks or measured speed and quality results.

Kind of workStarting pointBasis
Work already configured for CodexEither model; change only `model`The base URL, auth and protocol are shared.
Input-heavy requests: long prompts, large context, repeated instructionsEitherBoth list $0.20 per 1M tokens for this metric.
Output-heavy requests: long code or document generationEitherBoth list $1.00 per 1M tokens for this metric.
Cache-read-heavy requests: repeated prefixes and reused contextGPT-6.1 SolCache read rate: GPT-6 Sol $0.02 vs GPT-6.1 Sol $0.01 per 1M tokens.

How the integration differs

These are wire-level settings readers must configure, not capability claims.

Model IDsgpt-6-sol / gpt-6.1-sol
Codex setupCodex setup guide · model: gpt-6-sol · https://www.codebyai.net/api/agent
ProtocolCodex: OpenAI Responses / Chat Completions
Key and balanceBoth use the same base URL, auth variable and prepaid balance.
What changesOnly the `model` value; the client configuration is unchanged.
BillingBoth debit the same prepaid wallet at the per-1M-token rates above. Code By AI does not charge the official list price.

FAQ

Which model is cheaper on Code By AI?
Input and output rates match at $0.20/$1.00; GPT-6.1 Sol has the lower cache-read rate ($0.01 vs $0.02 per 1M tokens). For cached input, that is the only price difference shown.
Are these the exact API model IDs?
Yes. Use `gpt-6-sol` and `gpt-6.1-sol` exactly. The page does not derive IDs by splitting the slug.
Do both models use the same key and endpoint?
Yes. Both are Codex models on the same endpoint; only the model value changes.
How are the OpenRouter prices obtained?
The OpenRouter cells show recorded base rates that matched the catalog vendor fields when checked. The dates are listed with the sources below the table. OpenRouter cells show a number only when the exact provider model ID and rate basis were checked against this catalog row. Cells marked Not verified have no such evidence. Credit-purchase fees and other OpenRouter plans are separate and are never added to the per-token prices here.
Does this page measure quality or speed?
No. The scenarios describe client protocols and token mix, not measured quality, speed or SLA results.

Next step

Create a Code By AI account, top up the prepaid wallet and create an API key. Then call the model with the ID and endpoint above.

Code By AI is a third-party prepaid API gateway. It is not an official vendor product.