Nex-N2-Pro
openrouter/nex-n2-pro出品方： openrouter · 系列: agi · 發布 2026-06-08
Prices in USD per 1M tokens. Unknown means the provider does not publish per-token pricing.
能力清單
Model fit scores
0–100 · higher is betterThese scores reward declared capabilities, context size, price and provider availability — they are not benchmark results. Use them as a directional signal alongside your own evaluation.
Coding19
- Tool calling0/40
- Structured output0/20
- Reasoning10/10
- Context window (100K → 1M)8/20
- Provider availability1/10
Agents31
- Tool calling0/35
- Structured output0/25
- Reasoning15/15
- Output token limit15/15
- Provider availability1/10
JSON / structured output28
- Structured output / JSON mode0/50
- Tool calling0/20
- Temperature control10/10
- Price-friendly for high-volume18/20
Cost efficiency65
- Headline price (log-scaled)60/95
- Has prompt-cache pricing5/5
Long context61
- Context window (100K → 2M)51/90
- Has published price for full window10/10
Vision82
- Accepts image input50/50
- Context window (10K → 1M)21/30
- Has published price10/10
- Provider availability1/10
Production-readiness65
- Number of independent providers5/40
- Has published per-token price20/20
- Context window ≥ 8K15/15
- No data inconsistencies across providers10/10
- Official model (not derivative)15/15
Cost Efficiency Index
Open full calculator →Estimated cost using the recommended provider's headline rate. Each scenario fixes average input/output tokens — the assumptions are shown in the third column.
| Scenario | Cost | Assumption |
|---|---|---|
RAG answer per 1,000 RAG answers | $1.75 < $0.01 per request | 5K input tokens (query + 4 retrieved chunks of ~1K each) and a 500-token answer. Typical SaaS knowledge-base bot. |
Support ticket triage per 10,000 tickets | $3.50 < $0.01 per request | 1K input tokens (ticket body + system prompt) and a 100-token JSON classification reply. High-volume customer support. |
Data extraction per 1,000 documents | $1.00 < $0.01 per request | 2K input tokens (a single document page) and a 500-token JSON extraction. ETL / invoice / form pipelines. |
Code review per 1,000 PRs | $3.00 < $0.01 per request | 8K input tokens (diff + surrounding files) and a 1K-token review comment. PR-bot workloads. |
Agent step per 1,000 steps | $3.60 < $0.01 per request | 12K input tokens (long-running tool history) and a 600-token tool-call decision. Cost per agent step. |
定價詳情
推薦定價來自 openrouter · nex-agi/nex-n2-pro
於 1 家供應商可用
| 服務商 | 服務商模型 ID | 輸入 / 1M | 輸出 / 1M | 上下文 | 發布日期 |
|---|---|---|---|---|---|
| OpenRouter openrouter | nex-agi/nex-n2-pro | $0.250 | $1.00 | 262K | 2026-06-08 |
Frequently asked questions
How much does Nex-N2-Pro cost?
Nex-N2-Pro costs $0.250 per 1M input tokens and $1.00 per 1M output tokens, sourced from openrouter. Cache reads, audio tokens and >200K-context tiers (where applicable) are listed in the Pricing detail block above.
What is the context window of Nex-N2-Pro?
Nex-N2-Pro has a context window of 262K tokens, with a max output of 262K tokens per reply. This is the total combined size of prompt + completion.
Does Nex-N2-Pro support tool calling?
No. Nex-N2-Pro does not support tool calling (function calling). If your workflow requires it, look at the /capabilities/tool-calling list for alternatives.
Does Nex-N2-Pro support structured output / JSON mode?
No. Nex-N2-Pro does not support structured output / JSON-schema-constrained decoding. If your workflow requires it, look at the /capabilities/structured-output list for alternatives.
Can Nex-N2-Pro accept image input?
Yes. Nex-N2-Pro accepts both text and image input. Vision pricing per image is usually billed on top of the regular token rate — check openrouter's docs for the exact rule.
Is Nex-N2-Pro open-weight?
Yes. Nex-N2-Pro's weights are publicly available, so you can self-host or fine-tune. Note that open weights ≠ open source — the training data and code are typically not released.
What are the best alternatives to Nex-N2-Pro?
If Nex-N2-Pro doesn't fit, consider Ling-2.6-1T, Ring-2.6-1T, Ling-2.6-flash. Each one targets the same use case — see the Related links below for direct head-to-head pages.
Where does this data come from?
All numbers are normalised into a single canonical model record and reconciled with each provider's official documentation. We re-pull daily and write any changes (price, context, capability) to the /changelog page.
Explore more
More openrouter models
- Ling-2.6-1T$0.07 in / $0.63 out
- Ring-2.6-1T$0.07 in / $0.63 out
- Ling-2.6-flash$0.01 in / $0.03 out
- Granite 4.0 Micro$0.02 in / $0.11 out
- Granite 4.1 8B$0.05 in / $0.10 out
Capability lists this model is in
最近更新：
Pricing and capabilities are refreshed daily and reconciled against each provider's official documentation. Always verify critical production decisions with the provider directly.