Skip to content
ModelCap

Qwen3.5 Plus 2026-02-15

All-versions archive #221API only

Qwen·qwen/qwen3.5-plus-02-15

Qwen3.5 Plus 2026-02-15 is ModelCap archive rank #221 (Modeled · succession), from the ModelCap Index as of 22 Sept 2026, 02:49 UTC.

Qwen3.5 Plus 2026-02-15 listed OpenRouter input price is $0.26 per 1M tokens and listed output price is $1.56 per 1M tokens, from OpenRouter listed prices as of 22 Sept 2026, 02:49 UTC.

Qwen3.5 Plus 2026-02-15 has a published context limit of 1M tokens in the ModelCap catalogue as of 22 Sept 2026, 02:49 UTC.

Qwen3.5 Plus 2026-02-15 has 1 published OpenRouter serving endpoint, from OpenRouter as of 22 Sept 2026, 02:49 UTC.

Qwen3.5 Plus 2026-02-15 weight access is api only, from ModelCap classification of published repository metadata as of 22 Sept 2026, 02:49 UTC.

Snapshot facts · download the public dataset · methodology

ModelCap Index · All-versions archive
38.0#221
Estimated · 26% support · score interval 24.4–51.6
No admitted evaluation publication timestamp yet
Market Gravity
39.5Increased by 0.1
Secondary market signal

Superseded by Qwen3.7 Plus. It no longer holds a current-board position; its all-versions archive rank is #221.

Input
$0.26
per 1M tokens
Output
$1.56
per 1M tokens
Context
1M
tokens
Providers
1
endpoint
Gateway spend
latest · Vercel share

Providers

Uptime measured over the last 30 minutes
ProviderInputOutputContextQuantUptime
Alibaba$0.26$1.561M100.0%

Other versions (5)

ModelCap Index · All-versions archive

Methodology
38.0
Modeled · succession · calibrated architecture-and-release-era fallback from static public metadata
All-versions archive
#221
Public rank basis
Modeled · succession (architecture)
Index support
26.4% · limited
Index interval
24.4–51.6
Rank posterior
Not available
Top 5 / Top 10 probability
Not available / Not available
Posterior as of
Snapshot timestamp unavailable
Evidence as of
No admitted evaluation publication timestamp
Identity binding
Exact catalogue product · qwen/qwen/qwen3.5-plus-02-15 · aggregates disclosed benchmark configurations · endpoint configuration not claimed
Index observations used
0
Qualified Index evidence point
38.0
How this position was produced · fused launch placement

No general-family board lists this model yet. Its point estimate is the precision-weighted mean of every channel that spoke for it; each channel’s share is the weight it carried. Independent measurements replace this placement as boards list the model.

Fused estimate
38.0 ± 10.6
Independent share
0%
Shrink toward corpus
+4.3
Optimism haircut
None applied
Method
precision-weighted-v1
Channels fused into this model’s launch placement
ChannelEstimateShare
Publisher corpus prior · not independent
publisher-corpus-prior over 203 held-out anchors
53.5 ± 22.722%
Family succession · not independent
opens from measured predecessor qwen/qwen-plus
33.7 ± 12.078%
Bayesian Evidence Score · measured evidence input only

BES normalizes admitted public benchmark evidence for measured Index rows. Its legacy score and observables prior do not define the public language rank.

Observed capability
Evidence status
No admitted measured evidence
General preference
Coding
Agents & tools
Reasoning
Evidence breadth
0%
Evidence coverage
0%
Market and catalogue signals · secondary, never the language Index rank
Usage (OpenRouter popularity)
10.0
Liquidity (providers × uptime)
97.4
Open reach (HF downloads)
Surface (context / tools / modalities)
100.0
Freshness
43.6
  • · OpenRouter popularity #181
  • · 1 live provider
  • · Catalogue: context 1000000, reasoning, tools, modalities Text/Image/Video
  • · First seen 2026-02-16

These adoption and deployment observations remain context only. They do not change this model's ModelCap Index score or rank.

The bounded 0–100 capability score blends each source’s competitive placement with its published achievement, then combines capability families. Evidence breadth adds a modest uncertainty adjustment; price and popularity are not part of benchmark-led rank.

Experimental capability estimate

Estimate policy
Estimator abstained

insufficient-artifact-metadata

Feature coverage
86%
Training support
206 models · 119 lineages

insufficient-artifact-metadata. This layer predicts from admitted evidence and safe metadata only. It never enters ModelCap Score or rank.

Deployment readiness

Metadata index
30.1
limited · 38% metadata coverage
Not capability
Artifact reproducibility
0.0
Access & legal clarity
30.3
Deployability
80.0
Evaluation provenance
0.0

Missing: artifactReproducibility.revision-sha, artifactReproducibility.architecture-and-model-type, artifactReproducibility.parameter-count, artifactReproducibility.serialized-weight-format, artifactReproducibility.base-lineage, accessLegalClarity.declared-license, accessLegalClarity.resolvable-license-terms, evaluationProvenance.admitted-evaluation-observations, evaluationProvenance.capability-family-breadth, evaluationProvenance.evaluation-source-diversity, evaluationProvenance.identity-and-source-confidence, evaluationProvenance.evaluation-dataset-revisions.

A metadata completeness and deployability index—not a safety certification, quality grade, or production-readiness claim.

Market activity

Venue coverage
Market Gravity
39.5
OpenRouter weekly popularity
#181 of 322

Market Gravity uses OpenRouter’s full-catalogue popularity order. Sparse Vercel top-ten observations appear only when published and do not affect the score.

Arena preference

No matched Arena rating

This model is visible because it is available in the live catalogue, but it has no trustworthy community result yet. ModelCap does not infer a quality score from price, features, or market activity.

Market Gravity breakdown

Usage55%
10.0

OpenRouter weekly popularity across the full model catalogue.

Liquidity25%
97.4

Independent providers versus the model's open or closed cohort, weighted by uptime.

Open reach15%
50.0

Hugging Face 30-day downloads for open models; neutral for closed models.

Freshness5%
43.6

Time since first public availability, on a six-month half-life.

Specification

Context window
1M tokens
Max output
66K tokens
Inputs
Text, Image, Video
Outputs
Text
Tokenizer
Qwen3
Cached input tokens
Not offered
First seen on OpenRouter
16 Feb 2026

Capabilities

  • Supported: Reasoning
  • Supported: Tool use
  • Supported: Structured output
  • Supported: Response format
  • Not supported: Moderated

Qwen3.5 Plus 2026-02-15: common questions

How does Qwen3.5 Plus 2026-02-15 rank among AI models?

Qwen3.5 Plus 2026-02-15 is a superseded version and is not on the current board as of 22 September 2026. Its archive position, where one exists, is shown on the page; the newer version carries the current rank.

How much does Qwen3.5 Plus 2026-02-15 cost per 1M tokens?

Qwen3.5 Plus 2026-02-15 is listed at $0.26 per 1M input tokens and $1.56 per 1M output tokens as of 22 September 2026. Prices come from the OpenRouter catalogue and re-observe on every refresh. For 1,000 requests using 2,000 input and 500 output tokens each, the listed rates imply $1.30 total (2M input + 0.5M output). This excludes caching, batch discounts, prompt-length tiers, tool charges and retries; verify the chosen endpoint's rate and limits before budgeting.

What is the context window of Qwen3.5 Plus 2026-02-15?

Qwen3.5 Plus 2026-02-15 has a published context window of 1M tokens (1,000,000) and a maximum output of 66K tokens. Individual providers can serve less than the published maximum; the providers table lists each endpoint's own limit.

Is Qwen3.5 Plus 2026-02-15 open-weight?

API only. No downloadable model weights are linked in the current source data; access is through a hosted API or product.

Which API providers serve Qwen3.5 Plus 2026-02-15?

One provider serves Qwen3.5 Plus 2026-02-15 through OpenRouter as of 22 September 2026: Alibaba. Each provider's price, context limit, quantization and measured uptime are in the providers table above.

When was Qwen3.5 Plus 2026-02-15 released?

Qwen3.5 Plus 2026-02-15 first appeared in the catalogue on 16 Feb 2026. It has since been superseded by Qwen3.7 Plus. Rank and price movements since then are recorded on the site's changes feed.