Choosing this model
Selection advice by Y-API. The checks below are suggested evaluations, not published test results.
Where to start
Use it as the second opinion on work where 5.4 produced something plausible but you cannot confirm it: a subtle concurrency bug, a security-relevant code path, an ambiguous specification.
What to watch for
Token efficiency is a publisher claim about output length, not something this page measured. If you compare cost per task, count the tokens actually billed rather than the tokens in the answer.
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
API pricing & cost estimate
- Estimated credit consumed
- $20.00
- Estimated cash equivalent
- $2.00
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.
| Model | Estimated credit consumed | Estimated cash equivalent |
|---|---|---|
| GPT-5.5 | $20.00 | $2.00 |
| GPT-5.5 Pro | $120.00 | $12.00 |
| GPT-5.4 | $10.00 | $1.00 |
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
Two services disagree about who owns this record. Given both handlers, identify the ordering that produces the disagreement and propose a fix that does not depend on which one runs first.
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 --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-5.5",
"messages": [
{
"role": "user",
"content": "Two services disagree about who owns this record. Given both handlers, identify the ordering that produces the disagreement and propose a fix that does not depend on which one runs first."
}
],
"max_tokens": 4096
}
JSONHow to evaluate the result
The fix should be correct under both orderings. Ask for the interleaving that breaks the original code, then check that the proposed change survives it.
Before you choose
Is 5.5 worth it over 5.4 for everyday work?
Usually not for routine tasks — the two are close in price per token, so the decision should come from your own failure rate. Keep 5.5 for the cases where 5.4’s answer needed a second attempt.
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.