GPT-6.1 Sol

openai/gpt-6.1-sol

GPT-6.1 Sol is the revised Sol entry in the GPT-6 generation, listed with a 1,050,000-token window and file, image and text input. The reference positions it below Astra for agentic coding, computer use and document-heavy work.

Input · Account credit
$2.00

per 1M tokens

Cash equivalent $0.20

Output · Account credit
$10.00

per 1M tokens

Cash equivalent $1.00

Context window
1,050,000

tokens · OpenRouter

Input → Output
File · Image · Text→ Text
Model specifications
Sources reviewed: Y-API catalog snapshot:

Choosing this model

Selection advice by Y-API. The checks below are suggested evaluations, not published test results.

Where to start

Try it on agent workflows that touch tools repeatedly — reading files, editing code, checking the result — where the earlier Sol entry needed more retries than you wanted.

What to watch for

A point release is not a guarantee of better behaviour on your workload, and “computer use” in the reference describes the model’s training, not a screen-control feature of this gateway. Keep your own tool harness and its permissions.

Model specifications

These are OpenRouter model-level specifications, not a Y-API compatibility test. A particular route may accept fewer input formats, parameters or tokens. Verify the features you need with a small request; a successful text response does not validate vision or tool calling.

Context window
1,050,000 tokens
Input
File · Image · Text
Output
Text
Listed on OpenRouter
Parameters listed by OpenRouter
include_reasoningmax_completion_tokensmax_tokensreasoningreasoning_effortresponse_formatseedstructured_outputstool_choicetoolsverbosity
OpenRouter model page & specifications

API pricing & cost estimate

Estimated credit consumed
$7.00
Estimated cash equivalent
$0.70

Illustrative token budget, not measured usage or a quote. Includes input and output; excludes separate media charges, cache discounts and retries. Include billed reasoning tokens in your output budget where applicable. Actual billing follows usage returned by the service.

$1 paid adds $10 of credit. Cash equivalent = credit consumed ÷ 10; this is not the model publisher’s list price.

Same token budget, different models
ModelEstimated credit consumedEstimated cash equivalent
GPT-6.1 Sol$7.00$0.70
GPT-6 Sol$7.00$0.70
GPT-6 Astra$35.00$3.50
View LLM API pricing & billing

API integration examples

These minimal, text-only requests use the exact Y-API model ID. They do not demonstrate image, audio, video, file or tool support. The output limit also needs room for reasoning; an empty answer with finish_reason=length can mean the budget was exhausted.

A task to try

Walk through fixing this failing build step by step. After each step, state the evidence you would look for before deciding the next one.

Set the TOKEN environment variable to a key from your console. Run this on your server or locally; never expose a key in browser code or a public repository.

cURL · GPT-6.1 Sol
curl --fail-with-body --silent --show-error --max-time 120 \
  'https://api.y-api.bestvirtualgoods.com/v1/chat/completions' \
  -H "Authorization: Bearer ${TOKEN:?Set TOKEN first}" \
  -H 'Content-Type: application/json' \
  --data-binary @- <<'JSON'
{
  "model": "openai/gpt-6.1-sol",
  "messages": [
    {
      "role": "user",
      "content": "Walk through fixing this failing build step by step. After each step, state the evidence you would look for before deciding the next one."
    }
  ],
  "max_tokens": 4096
}
JSON

How to evaluate the result

Each step should be conditional on evidence from the previous one. A fixed checklist that ignores what the build actually printed is the pattern this task is meant to expose.

Before you choose

Should I switch from GPT-6 Sol to 6.1 Sol?

Run the same agent tasks through both and compare retries and total billed tokens. A point release often helps most on long tool loops, which is exactly where a single sample will mislead you.

Sources & scope

Technical facts come from the cited model page and, where available, its linked publisher card. A card describes that checkpoint; it is not proof of the weights a gateway serves. Prices come only from the Y-API catalog. We do not claim measured latency, uptime or benchmark scores for this endpoint.