Tarif de lancement (jusqu’au 25 déc.), garanti tant que vous restez abonné : Go à $10/mois (au lieu de $20), Plus avec Opus 5.5 à seulement $30/mois (au lieu de $50)S’abonner →
Chat textecontexte de 1M

GPT-6.2 Sol

Use GPT-6.2 Sol at 30% of OpenAI's price: $0.60/1M input, $3.00/1M output. Compare with GPT-6.2 Astra, plus curl, Python, and Codex setup.

Prix / 1M de tokensÉconomisez 70 %
OfficielAIReiter
Entrée$2.00$0.60
Sortie$10.00$3.00
Lecture du cache$0.10$0.03
Création cache$2.50$0.75
Documentation
Entrée
Limite la longueur de la réponse. Les modèles de raisonnement comptent aussi leur réflexion.
gpt-6.2-sol
Sortie

A codebase you don't know is a risk, not a hurdle. The plan should burn down that risk in order: understand, run, trace, spike, then make the change small enough that "production-ready" is a property you can demonstrate, not a hope.

Here are the first five steps, with the evidence you collect at each.

Step 1 — Get it building and the baseline green (half day)
Read the README, the manifest(s), the CI config, and any architecture docs. Boot the app locally, run the full test suite, run the linter/typechecker.
Evidence: The exact commands that reproduce a clean build and a passing test suite from a fresh checkout (recorded output, not memory of it). A one-page map you wrote yourself: where the entry points are, the layers, the build/test toolchain, and the main risks to your feature (e.g. "this touches cron jobs and payments").

Step 2 — Trace the smallest end-to-end slice that resembles your feature (half day)
Don't start with your feature. Pick a neighboring one that already works and follow it from entry to persistence. Note the conventions along the way: how errors surface, how config is injected, how logging is done, how tests are written.
Evidence: An annotated trace — file → function → what it does — for that slice. A written list of "conventions I must follow" (not intuitions; things you observed in real code). A named shortlist of the 3–5 files you will actually touch. If you can't produce this trace, you're not ready to write code.

Step 3 — Spike the core path (day 2)
Build the ugly version: hardcoded values, no error handling, no tests. The purpose is to confirm the path you traced in step 2 is real and to surface what you didn't know you didn't know.
Evidence: A working spike demonstrating the feature's central data path, alongside a list of every assumption the spike broke and what you corrected. That correction list is the most valuable document in this whole plan.

Step 4 — Write the contract before the code (half of day 2 / day 3)
Once the spike proves the path, pin down what production needs: the inputs/outputs, the error cases, where it sits in the conventions from step 2. Then write the tests — they'll be red, but they're the specification.
Evidence: A one-to-two-page design doc, an agreed interface/API shape (with the team if there is one), and a red test suite that encodes intended behavior. If you can't write the contract without consulting the code, you haven't finished step 2.

Step 5 — Implement in small, verified increments (days 3–4)
Replace the spike with the real thing in small commits, each one keeping the suite green, leaning on the existing patterns. Run lint/tests/typecheck per commit — CI, not just locally — and exercise the actual path against a real instance (staging or a local environment that isn't stubbed).
Evidence: A branch with progressive commits, each green in CI; coverage on the new code; something that proves it works against reality (a test result, a log trace, a screenshot); and a review by at least one person who knows the codebase. The review counts as evidence — an unfamiliar codebase has tribal knowledge you cannot extract from the files alone.

Steps 6+ would be the things that actually make it "shipped": a migration plan and its rollback, feature flagging, observability, the release and post-release verification. But the first five get you to a reviewed, green, working slice in staging — which is the point at which you can say "this will work in production" with evidence behind it, instead of a guess.

Généré en42.7s
Token d’entrée134
Token de sortie2,354
Tokens / s55.13
TTFT-

Exécuter ouvre AI Chat avec ce prompt. Connexion et crédits requis.

Détails du modèle

Utilisez la même clé de modèle dans le Playground, les requêtes API et les workflows internes.

ID du modèle
gpt-6.2-sol
Fournisseur
Openai
Protocole
OpenAI Chat Completions
Fenêtre de contexte
1,050,000 tokens
Sortie maximale
128,000 tokens
Token d’entrée
60 crédits / 1 M de tokens
Token de sortie
300 crédits / 1 M de tokens
Lecture du cache
3 crédits / 1 M de tokens
Écriture du cache
75 crédits / 1 M de tokens

Qu’est-ce que GPT-6.2 Sol

GPT-6.2 Sol comparison

GPT-6.2 Sol code samples

01GPT-6.2 Sol cost examples

FAQ

01How much does GPT-6.2 Sol cost on AIReiter?

GPT-6.2 Sol costs $0.60 per 1M input tokens and $3.00 per 1M output tokens on AIReiter, which is 30% of OpenAI's official $2.00 and $10.00. Cached input reads are $0.030 per 1M against the official $0.10, and cache writes are $0.75 per 1M. AIReiter charges one flat price at any context length, with no long-context surcharge.

02What is GPT-6.2 Sol good at?

OpenAI positions GPT-6.2 Sol as its go-to model for everyday work, from coding to powering agents at scale. It accepts text and image input and returns text, so audio and video tasks need a different model.

03What is the context window?

GPT-6.2 Sol has a 1,050,000-token context window, with up to 922K input tokens and 128K output tokens. OpenAI surcharges input above 272K tokens, but AIReiter bills one flat price across the whole window.

04Which reasoning effort settings are supported?

OpenAI's model page says requests that set reasoning effort to none are rejected for GPT-6.2 Sol. Use low, medium, high, xhigh, or max instead. Higher settings produce more reasoning tokens, which are billed as output, so raise effort only for problems that need planning.

05Does GPT-6.2 Sol support tool calling?

Yes. Function calling, structured outputs, and streaming are supported. On AIReiter, tool calling works on both https://aireiter.com/api/v1/chat/completions and https://aireiter.com/api/v1/responses with model gpt-6.2-sol.

06How do I use GPT-6.2 Sol in Codex CLI?

Add an aireiter provider to ~/.codex/config.toml with base_url https://aireiter.com/api/v1, wire_api set to responses, and env_key set to AIREITER_API_KEY, then set model to gpt-6.2-sol. Export your AIReiter key in that environment variable and start Codex. The full config is in the code section above.