GPT-6 Sol API
Call GPT-6 Sol through Wokey and review published catalog pricing, upstream-native API forms, context, and model capabilities.
GPT-6 Sol has been superseded by GPT-6.1 Sol
GPT-6.1 Sol launched on 2026-09-29 at the same input and output price as GPT-6 Sol ($2 / $10), with cache reads down from $0.20 to $0.10. OpenAI reports DeepSWE v1.1 up from 68.8% to 75.2%, and Artificial Analysis’ Intelligence Index rose from 48 to 52. Use GPT-6.1 Sol for new work; when migrating, note that it does not accept none or minimal effort.
- Model ID
gpt-6-sol- Vendors
- openai
- Supply status
- Currently callable
Catalog pricing snapshot
Prices are per 1M tokens; request-time pricing controls settlement.
| Meter | Wokey | Official reference | Savings |
|---|---|---|---|
| Input | $0.18 | $2 | 91% |
| Output | $0.9 | $10 | 91% |
| Cache read | $0.018 | $0.2 | 91% |
| Cache write | $0.225 | $2.5 | 91% |
Official price source: https://developers.openai.com/api/docs/models/gpt-6-sol
Measured on Wokey
Last 28 days (2026-10-13 to 2026-11-09), updated every Monday · Real requests from 100+ accounts
- Time to first token, short prompts
- 5.1 s (Median · prompts under 8K tokens · p90 16 s)
- Time to first token, agent-size prompts
- 9.7 s (Median · prompts of 32K–128K tokens)
- Prompt cache hit rate
- 84% (Share of input tokens read from cache)
Most-used clients: Codex 75%, OpenCode 10%, DeepSeek Harness 8%. Share of requests from identified clients; 24% of requests had an identified client.
How this is measured
Time to first token runs from the Wokey gateway receiving the request to the first streamed content (text, reasoning summary or refusal). It includes queueing, retries on another account and the model's thinking time, so it is longer than the upstream's own first-token latency. Only successful streamed requests count, banded by prompt size (input plus cache reads and writes).
Cache hit rate = cache-read tokens ÷ input tokens over successful requests. It depends on the client and how it is used; the cache hit-rate pages break it down by client.
Enterprise accounts and Wokey's own test accounts are excluded. A model is shown once at least 20 users used it in the last 28 days and no single user sent more than 50% of its requests, counting accounts registered through one referral chain as one user; each first-token figure needs at least 500 requests.
Model capabilities
- Context
- 1,050,000 tokens
- Max output
- 128,000 tokens
- Streaming
- Supported
- Tools
- Supported
- Vision
- Supported
- Supported API forms
/v1/chat/completions·/v1/responses
Send a request
/v1/chat/completions
curl https://api.wokey.ai/v1/chat/completions \
-H "Authorization: Bearer $WOKEY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"gpt-6-sol","messages":[{"role":"user","content":"Hello"}]}'/v1/responses
curl https://api.wokey.ai/v1/responses \
-H "Authorization: Bearer $WOKEY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"gpt-6-sol","input":"Hello"}'Use GPT-6 Sol in your tools
The gateway is https://api.wokey.ai (OpenAI-compatible clients usually take https://api.wokey.ai/v1), and the model ID is gpt-6-sol. Open the guide for the client you use.
- Use GPT-6 Sol in Codex: OpenAI Responses · base URL and API key setup
- Use GPT-6 Sol in opencode: OpenAI Chat Completions · base URL and API key setup
- Use GPT-6 Sol in DeepSeek Harness: OpenAI Chat Completions · base URL and API key setup
- Use GPT-6 Sol in Cherry Studio: OpenAI Chat Completions · base URL and API key setup
- Use GPT-6 Sol in WorkBuddy: OpenAI Chat Completions · base URL and API key setup
- Use GPT-6 Sol in OpenClaw: OpenAI Chat Completions · base URL and API key setup
- Use GPT-6 Sol in Hermes Agent: OpenAI Chat Completions · base URL and API key setup
- Use GPT-6 Sol in Magpie: OpenAI Chat Completions · base URL and API key setup
- GPT API cost calculator: what GPT-6 Sol costs per month: Compare monthly cost on the OpenAI API and Wokey for your usage and cache hit rate.
- OpenRouter alternative: Wokey vs OpenRouter: Compare token prices, payment fees, API forms, and upstream sources.
- Verifiable AI API: check a GPT-6 Sol response came from the official upstream: Which responses carry a tee.proof, and what a proof does and does not show.
- Verify a GPT-6 Sol response online: AI API relay verifier: Paste a response with its tee.proof and check it locally in your browser; nothing is uploaded.
Frequently asked questions
Should I use GPT-6 Sol or GPT-6.1 Sol?
Use GPT-6.1 Sol. Both cost $2 input / $10 output per million tokens, but GPT-6.1 Sol reads cache at $0.10 versus $0.20 on GPT-6 Sol, and its Artificial Analysis Intelligence Index score rose from 48 to 52. When migrating, note that GPT-6.1 Sol does not accept none or minimal effort, and Chat Completions cannot call tools, so use Responses.
How much does the GPT-6 Sol API cost, and how much does it save versus the official API?
Wokey lists input at $0.18 per 1M tokens and output at $0.9 per 1M tokens; the official references are $2 and $10. That is 91% lower for input and 91% lower for output. Request-time pricing controls settlement, and the vendor pricing source is linked on this page.
What is the GPT-6 Sol API model ID?
The model ID for GPT-6 Sol on Wokey is gpt-6-sol. Use it exactly as written in the request body's model field or in your client's model setting (for example ANTHROPIC_MODEL in Claude Code, or model in the Codex CLI config.toml); GET https://api.wokey.ai/v1/models also lists it.
Which API forms does GPT-6 Sol support, and how do I call it through Wokey?
GPT-6 Sol supports /v1/chat/completions (Chat Completions requests) and /v1/responses (Responses requests). Set the API base URL to https://api.wokey.ai, authenticate with a Wokey API key, and use the canonical model ID gpt-6-sol; you can start with /v1/responses. The Send a request section includes a curl example for every supported API form.
How do I use GPT-6 Sol in Codex CLI?
Codex CLI calls GPT-6 Sol over the Responses protocol. Add a model_provider to ~/.codex/config.toml with base_url = "https://api.wokey.ai", wire_api = "responses", and env_key = "OPENAI_API_KEY"; set model to gpt-6-sol and put your Wokey API key in OPENAI_API_KEY. The Codex CLI guide has the full config.
What are the context window and maximum output for GPT-6 Sol?
The catalog context window is 1,050,000 tokens and the maximum output is 128,000 tokens. These are separate limits, and a request must also satisfy the upstream constraints in effect when it is processed.
How are cache reads and cache writes priced for GPT-6 Sol?
Cache read: Wokey lists $0.018 per 1M tokens and the official reference is $0.2 per 1M tokens. Cache write: Wokey lists $0.225 per 1M tokens and the official reference is $2.5 per 1M tokens.
How does calling GPT-6 Sol through Wokey differ from OpenRouter?
Wokey lists GPT-6 Sol at $0.18 input / $0.9 output per 1M tokens, against an official reference of $2 / $10. OpenRouter states it adds no markup on inference and charges its fee when you buy credits (5.5% by card). Wokey carries a curated set of models and has no per-provider routing parameters, so OpenRouter fits better if you need a wider catalog. The OpenRouter alternative page has the full comparison.
How do GPT-6 Sol and GPT-6 Astra differ in price and context?
In the published price comparison, GPT-6 Sol lists input/output at $0.18 / $0.9 with a 1,050,000-token context window; GPT-6 Astra lists $0.55 / $2.75 with a 1,050,000-token context window. This is a factual price-and-capacity comparison, not a quality ranking; also compare their supported API forms and capabilities.
How fast is GPT-6 Sol on Wokey?
Measured on real Wokey gateway requests from 2026-10-13 to 2026-11-09: the median time to first token was 5.1 s for prompts under 8K tokens (p90 16 s) and 9.7 s for 32K–128K-token agent prompts. 84% of input tokens were read from the prompt cache. The most-used clients were Codex, OpenCode and DeepSeek Harness. Times run from the gateway receiving the request and include queueing, retries and thinking.
Related models and documentation
Get API key · gpt-6-sol