Models

gpt-6-sol — API, Pricing & Context Window | Vivgrid

Run OpenAI's gpt-6-sol on Vivgrid: the balanced gpt-6 model with a 1.05M-token context window, 128K max output, geo-distributed acceleration, and a unified API.

gpt-6-sol is the balanced model in OpenAI's gpt-6 family, sitting below the flagship gpt-6-astra. It keeps the generation's 1.05M-token context window and 128K-token max output at a fifth of astra's per-token price, making it a practical default for production coding agents.

On Vivgrid, gpt-6-sol is served through a single OpenAI-compatible endpoint with geo-distributed acceleration across AMER, EMEA, and APAC, so requests are routed to the nearest compute region for lower latency. You can switch your agent to gpt-6-sol from the Console without changing a line of application code.

It is available on both OpenAI surfaces — Chat Completions (/chat/completions) and the Responses API (/responses) — so coding CLIs that expect the Responses wire format, such as Codex and Pi, work against the same key.

Specifications

ProviderOpenAI
Model IDgpt-6-sol
Best forCoding
Context window1,050,000 tokens
Max output128,000 tokens
ModalitiesText, Image
Tool / function callingYes
Knowledge cutoff2026-04
Acceleration⚡ Geo-Distributed — AMER, EMEA, APAC

Pricing

Pricing in USD per 1M tokens, matching the provider's rates.

InputCached inputOutput
$2.00$0.20$10.00

Quick start

Call gpt-6-sol through Vivgrid's unified, OpenAI-compatible endpoint. Get an API key from the Vivgrid Console.

curl https://api.vivgrid.com/v1/chat/completions \
  -H "Authorization: Bearer $VIVGRID_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-6-sol",
    "messages": [
      { "role": "user", "content": "Say hello in English, Chinese and Spanish." }
    ],
    "stream": true
  }'

Prompt caching is billed at $2.50 per 1M cache-write tokens, with cached reads at $0.20.

Requests beyond 272K input tokens are billed at the long-context rate: $4.00 input / $0.40 cached input / $5.00 cache write / $15.00 output per 1M tokens.

Ideal use cases

  • Production coding agents balancing quality, speed, and cost
  • Coding CLIs on the Responses API (Codex, Pi, OpenCode)
  • Whole-repository analysis within a 1.05M-token context
  • High-volume tool-calling workflows that outgrow a small model

On this page