BlockRun
Get started
Back to Pricing

Qwen3.7 Plus

qwen/qwen3.7-plus

openrouter

Alibaba's balanced Qwen tier — 1M context with reasoning, coding, and agentic tool use at a fraction of the Max price

Code Examples

from blockrun_llm import LLMClient

client = LLMClient()  # Uses BLOCKRUN_WALLET_KEY (never sent to server)
response = client.chat("qwen/qwen3.7-plus", "Hello!")

Pricing

Input$0.32 / 1M tokens
Output$1.28 / 1M tokens
Context1M tokens
Max Output131K tokens

5% markup on official openrouter API prices.

Payment

Network
Base
Currency
USDC
Protocol
x402

Pay per request with USDC on Base. No subscription required.

Try It

Send a message to try Qwen3.7 Plus

Connect your wallet to enable payments

About qwen Qwen3.7 Plus

Alibaba's balanced Qwen tier — 1M context with reasoning, coding, and agentic tool use at a fraction of the Max price. It is built by qwen and served through BlockRun's OpenAI-compatible API, which means you can call it without an account, an API key, or a subscription. Requests are paid for individually, in USDC, at the moment they are made.

What it costs

Qwen3.7 Plus is billed per token. The underlying rates are $0.32 per million input tokens and $1.28 per million output tokens; a flat platform margin and a small per-transaction fee covering on-chain settlement are added on top, and the resulting price is quoted in the 402 before you pay. You are charged for the tokens a request actually consumes — there is no monthly commitment and no unused balance to forfeit. With a context window of 1,000,000 tokens and up to 131,072 tokens of output, a single call can carry a substantial working set.

Specifications

Context window
1,000,000 tokens
Maximum output
131,072 tokens
API compatibility
OpenAI-compatible
Payment
USDC via x402
Categories
chat, reasoning, coding

Calling it from your code

Pass qwen/qwen3.7-plus as the model field. Because the endpoint mirrors the OpenAI chat completions schema, any existing OpenAI client works by changing the base URL — streaming, tool use, and multi-turn messages all behave the same way.

The first request comes back as an HTTP 402 carrying a signed price quote. Your client signs that quote with a wallet holding USDC and retries; the second request returns the completion, and the payment settles on-chain. Client libraries handle this handshake for you, so in practice it is a single call. See the documentation for request and response shapes, or browse the full catalog of 71 chat models to compare alternatives.

Related models

Every model on BlockRun is reached through the same endpoint and the same payment flow, so switching is a one-line change to the model field. These are the closest alternatives to Qwen3.7 Plus: