Seed-OSS 36B Instruct vs Stockmark 2 100B Instruct
Seed-OSS 36B Instruct (2025) and Stockmark 2 100B Instruct (2025) are compact production models from ByteDance and Stockmark. Seed-OSS 36B Instruct ships a 4K-token context window, while Stockmark 2 100B Instruct ships a 128K-token context window. This comparison covers specs, pricing, capabilities, benchmarks, provider availability, and production fit. It focuses on practical selection signals rather than broad model-family marketing. The goal is to make the tradeoff clear before deeper testing.
Stockmark 2 100B Instruct fits 32x more tokens; pick it for long-context work and Seed-OSS 36B Instruct for tighter calls.
Decision scorecard
Local evidence first| Signal | Seed-OSS 36B Instruct | Stockmark 2 100B Instruct |
|---|---|---|
| Decision fit | General | Long context |
| Context window | 4K | 128K |
| Cheapest output | - | - |
| Provider routes | 1 tracked | 1 tracked |
| Shared benchmarks | 0 rows | 0 rows |
Decision tradeoffs
- Use Seed-OSS 36B Instruct when your own prompt tests beat the comparison signals; the local data does not show a decisive standalone advantage yet.
- Stockmark 2 100B Instruct has the larger context window for long prompts, retrieval packs, or transcript analysis.
- Local decision data tags Stockmark 2 100B Instruct for Long context.
Monthly cost at traffic
Estimate token spend from the cheapest tracked input and output prices on this page.
Seed-OSS 36B Instruct
Unavailable
No complete token price in local provider data
Stockmark 2 100B Instruct
Unavailable
No complete token price in local provider data
Cost delta unavailable until both models have sourced input and output token prices.
Switch friction
- Provider overlap exists on NVIDIA NIM; start route-level A/B tests there.
- Provider overlap exists on NVIDIA NIM; start route-level A/B tests there.
Specs
| Specification | ||
|---|---|---|
| Released | 2025-06-01 | 2025-06-01 |
| Context window | 4K | 128K |
| Parameters | 36B | 100B |
| Architecture | decoder only | decoder only |
| License | 1 | 1 |
| Knowledge cutoff | - | - |
Pricing and availability
| Pricing attribute | Seed-OSS 36B Instruct | Stockmark 2 100B Instruct |
|---|---|---|
| Input price | - | - |
| Output price | - | - |
| Providers |
Pricing not yet sourced for either model.
Capabilities
| Capability | Seed-OSS 36B Instruct | Stockmark 2 100B Instruct |
|---|---|---|
| Vision | No | No |
| Multimodal | No | No |
| Reasoning | No | No |
| Function calling | No | No |
| Tool use | No | No |
| Structured outputs | No | No |
| Code execution | No | No |
Benchmarks
No shared benchmark rows are currently sourced for this pair.
Deep dive
The capability footprint is close: both models cover the core production surface. That makes context budget, benchmark fit, and provider maturity more important than a simple checklist. If your application depends on one integration detail, verify it against the provider route you plan to use, not just the base model listing.
Pricing coverage is uneven: Seed-OSS 36B Instruct has no token price sourced yet and Stockmark 2 100B Instruct has no token price sourced yet. Provider availability is 1 tracked routes versus 1. Treat unknown pricing as an integration gap, then verify the route you will actually call before estimating production spend.
Choose Seed-OSS 36B Instruct when provider fit are central to the workload. Choose Stockmark 2 100B Instruct when long-context analysis and larger context windows are more important. For production, rerun your own prompts through the exact provider, region, and tool stack you plan to ship. This keeps the decision grounded in measurable tradeoffs instead of brand-level assumptions. It also helps separate model capability from provider packaging, which can change cost and latency. For teams standardizing a stack, that distinction is often the difference between a benchmark win and a reliable deployment.
FAQ
Which has a larger context window, Seed-OSS 36B Instruct or Stockmark 2 100B Instruct?
Stockmark 2 100B Instruct supports 128K tokens, while Seed-OSS 36B Instruct supports 4K tokens. That gap matters most for long documents, large codebases, retrieval-heavy agents, and conversations where earlier context must remain visible.
Is Seed-OSS 36B Instruct or Stockmark 2 100B Instruct open source?
Seed-OSS 36B Instruct is listed under 1. Stockmark 2 100B Instruct is listed under 1. License labels affect whether you can self-host, redistribute weights, or rely only on hosted APIs, so confirm the upstream license before deployment.
Where can I run Seed-OSS 36B Instruct and Stockmark 2 100B Instruct?
Seed-OSS 36B Instruct is available on NVIDIA NIM. Stockmark 2 100B Instruct is available on NVIDIA NIM. Provider coverage can affect latency, region availability, compliance posture, and fallback options. Use this as a quick comparison signal, then confirm the provider-specific limits before committing to production.
When should I pick Seed-OSS 36B Instruct over Stockmark 2 100B Instruct?
Stockmark 2 100B Instruct fits 32x more tokens; pick it for long-context work and Seed-OSS 36B Instruct for tighter calls. If your workload also depends on provider fit, start with Seed-OSS 36B Instruct; if it depends on long-context analysis, run the same evaluation with Stockmark 2 100B Instruct.
Continue comparing
Last reviewed: 2026-05-01. Data sourced from public model cards and provider documentation.