BlockRun
Get started
Back to Pricing

Qwen3.5 122B (Free)

nvidia/qwen3.5-122b-a10b

nvidia

Qwen3.5 122B MoE (10B active) hosted free by NVIDIA. Balanced reasoning + coding, 131K context.

Code Examples

from blockrun_llm import LLMClient

client = LLMClient()  # Uses BLOCKRUN_WALLET_KEY (never sent to server)
response = client.chat("nvidia/qwen3.5-122b-a10b", "Hello!")

Pricing

InputFree / 1M tokens
OutputFree / 1M tokens
Context131K tokens
Max Output16K tokens

Free model — no payment or wallet required.

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.5 122B (Free)

Connect your wallet to enable payments

About NVIDIA Qwen3.5 122B (Free)

Qwen3.5 122B MoE (10B active) hosted free by NVIDIA. Balanced reasoning + coding, 131K context. It is built by NVIDIA 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.5 122B (Free) is free to call on BlockRun. No payment header is required, no wallet needs funding, and no API key is issued — requests are rate limited per IP rather than billed. It is a practical way to develop against the API surface before moving production traffic onto a paid model.

Specifications

Context window
131,072 tokens
Maximum output
16,384 tokens
API compatibility
OpenAI-compatible
Payment
Free — no payment required
Categories
chat, reasoning, coding

Calling it from your code

Pass nvidia/qwen3.5-122b-a10b 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.