Qwen-Image 2.1 (Model Studio)

# Fix list: Qwen-Image 2.1 (Model Studio)

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/qwen-image-2-1, the October 2026 research run, assessed 10 October 2026. Grade B, 64.7 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on Qwen-Image 2.1 (Model Studio): work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Payments & pricing, 20 out of 100, up to 10 more on the total

Why it scored 20: No x402, MPP or L402 (0). Per-image prices for every region are published without a login, $0.04 in Singapore and $0.035333 elsewhere (20). New Singapore users get a 90-day free quota after completing account information, but the quota page does not list this model, and the international sign-up asks for payment details first, as read for alibaba-wan (0). A person signs up in a browser and creates the key (0). Total 20.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 2. Reliability, 70 out of 100, up to 6 more on the total

Why it scored 70: Alibaba Cloud runs a status page at status.alibabacloud.com with per-product components, read the same way as the alibaba-wan listing (20). The page renders in the browser only and its incident history was not read, so 5 for no readable history. The model page lists 20 requests a minute in all six regions (15). The rate-limit guide documents 429 for throttling and 403 for an exhausted free quota, and suggests switching to a backup model. No Retry-After header or idempotency guidance was found (10). The Model Studio inference SLA, last updated 8 September 2026, promises 99.9 per cent monthly uptime with service credits on paid inference (10). The model carries no preview label (10). Total 70.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 3. Schema & documentation, 66 out of 100, up to 5.5 more on the total

Why it scored 66: No OpenAPI or other machine-readable contract for the Qwen image endpoints. The OpenAI-compatible mode follows part of the OpenAI Images protocol but publishes no schema of its own (0). llms.txt at docs.modelstudio.console.alibabacloud.com with Markdown copies of every page (10). The API reference says when to use each of the three access methods and which parameters each model accepts, though little on when not to use the model (15 of 20). Typed parameters with ranges for n, size, seed and input images, an enum for prompt_extend_mode, and stated defaults. Some limits differ by model in prose rather than in types, such as negative_prompt for the 3.0 series only (13 of 15). curl, Python and Java examples for each access method, an error format with type, param and code, and a linked error-code page (15). A dated model release page and v1 paths. No dated snapshot of qwen-image-2.1-pro exists yet (13 of 15). Total 66.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 4. Agent ergonomics, 73 out of 100, up to 4.4 more on the total

Why it scored 73: API reading of the checklist. A sync call returns one or more PNG URLs with a small usage object. Base64 output is not available on the OpenAI-compatible mode (20 of 25). `n` (1 to 6) and `size` control output, and the async mode returns a task id to poll. No task list was found (15 of 20). Errors carry a code, a message and the parameter at fault, and the error-code page gives a fix for each code (18 of 20). No idempotency key, and nothing found on whether failed calls are billed for this model (5 of 20). Only `model` and `prompt` are required, everything else has a default, and the DashScope SDK for Python and Java and the OpenAI SDKs all work (15). Total 73.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 5. Security & auth, 75 out of 100, up to 4.4 more on the total

Why it scored 75: Model reading of the checklist (credential, training, retention, operator visibility, programme). API keys belong to a workspace, can be limited to chosen models and an IP allow-list of up to 20 entries, can be reset, and temporary keys are documented (30). The Model Studio privacy notice says Alibaba Cloud will never use customer data for model training (20). Result URLs and images are purged after 24 hours (5). No retention period for prompts or input images was found (0). The audit log records model calls and monitoring filters by API key (15). SOC 2 with an unqualified opinion is stated in the privacy notice (5). No security.txt on alibabacloud.com and no Model Studio bug bounty was found (0). Total 75.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 6. Transparency & trust, 66 out of 100, up to 3 more on the total

Made of editorial 60, provenance 72.

Why it scored 66: The API model is closed under Alibaba Cloud's product terms. Qwen-Image-2.1 weights are on Hugging Face under the Qwen Research License, which allows non-commercial use only and is not an OSI licence (15). The privacy notice says customer data is never used for training, and the API reference states 24-hour result retention. Input retention is not stated and no DPA was read (15 of 30). A decommissioning policy with notice periods by model type and a list of dated retirements (20). Six regional hosts are documented with separate keys and prices. No subprocessor list was found (10). Total 60.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Domain age: alibabacloud.com, no registry record we could read (0 of 15)
- Terms of service: published, but our reader couldn't read it (7 of 10)
- security.txt: not found (0 of 10)

## 7. Maintenance & community, 77 out of 100, up to 2 more on the total

Why it scored 77: Model reading. qwen-image-2.1-pro was released on 2 October 2026, and the `dashscope` SDK shipped 1.27.7 on 24 September with six releases since 27 August (30). A decommissioning policy gives 3 months' notice for mainline models and 30 days for dated snapshots, by email, internal message and announcement. The snapshot window is short, so 15 of 20. A dated model release page with qwen-image entries on 20 July, 4 August and 2 October, and Alibaba Cloud ticket support (12 of 15). Current official SDK on PyPI (15). PyPI links no source repository or CI (5). Total 77.

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- unchecked: the incident history on status.alibabacloud.com, which renders in the browser only.
- unchecked: whether the new-user free quota covers qwen-image-2.1-pro. The quota page does not list image models.
- unchecked: Alibaba Cloud's product terms and legal entity, which follow the alibaba-wan listing and were not re-read today.
- qwen-image-2.1-turbo has a page on help.aliyun.com with a price of 0.1 CNY an image and 120 requests a minute, but it is not in the API reference's model list or the international docs index. The founder's lead named Qwen-Image-2.1-Turbo. Whether Turbo is callable through Model Studio's API was not established, so the listing grades qwen-image-2.1-pro.
- Model Studio also serves qwen-image-3.0 and qwen-image-3.0-pro on the same endpoints, released in July and August 2026, which have no listing.
- No authenticated call was made, so speed, transparency output and error behaviour are as documented.

## Weaknesses

- 20 requests a minute in every region
- No OpenAPI or other machine-readable contract for the image endpoints
- Result URLs expire after 24 hours, and the OpenAI-compatible mode ignores `b64_json`
- `negative_prompt` works only on the qwen-image-3.0 series, not on qwen-image-2.1-pro
- Qwen-Image-2.1 weights are under a non-commercial research licence, so self-hosting is not an option for commercial work

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- Use the same region for the key, the model and the endpoint. Cross-region calls fail
- Download each result within 24 hours. The URL expires and the image is purged
- With the OpenAI SDK, pass `image`, `seed`, `prompt_extend` and `watermark` through `extra_body`, and write size as `1024x1024`, not `1024*1024`
- Set a client timeout of up to 600 seconds for several outputs, or use the async DashScope call and poll the task id
- Do not send `prompt_extend_mode: agent` with input images. It returns 400

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.