Data as of November 13, 2026 · How the score is built
Decision readingLongCat-2.0 is tracked, but not publicly ranked yet. The profile exposes 0 sourced benchmark rows and leaves unsupported fields blank until a published record exists.
Email me when its price, rank or availability changes.
Lineage
The sequence follows explicit supersedes links. Each score is estimated for that model; a relative can inform a sparse estimate but never sets a floor, so a newer release can score below an earlier one. Scores and prices remain blank when the corresponding public row or first-party rate is unavailable.
Base entry
Spec sheet
Each documented value carries its source. Missing fields stay visible as not sourced or not published, rather than disappearing from the page.
- API model ID
- Not published
- Context window
- 1M
- Maximum output
- Not sourced yet
- Knowledge cutoff
- Not sourced yet
- Input modalities
- Not sourced yet
- Output modalities
- Not sourced yet
- Parameters
- Not sourced yet
- Availability
- Not sourced yet
- Cloud regions
- Not tracked yet
- Lifecycle
- Superseded
- API capabilities
- Tool calling, structured outputs, and batch support are not tracked yet
- Prompt caching
- Not documented in the pricing record
- Self-host
- LongCat-2.0 needs ~1536GB VRAM (8× NVIDIA B200 (192GB)).
- Rate limits
- Not tracked yet
How to read this profile
The visual layer above carries the decisions. These notes preserve the model, ranking, coverage, and family context behind the numbers.
We track LongCat-2.0, but no weighted text-model benchmark result is published on the site yet. This page shows the metadata and separate protocol evidence we can verify now; a BenchLM score will appear only if compatible public evaluations land.
LongCat-2.0 is a open weight model with a 1M context window. It uses an explicit reasoning mode, which can improve complex problem solving while adding latency and token use.
Reviewed from the LongCat-2.0 launch page bundle. The source confirms a 1.6T-total-parameter MoE with about 48B active parameters per token, 1M-context training, and open-source release positioning. Its benchmark section is rendered from bundled app data and not safely extractable into BenchLM's current exact-value schema, so benchmark fields remain empty for now.
The profile has no source-displayable benchmark row yet.
Last updated November 13, 2026. Runtime fields remain blank until a sourced snapshot exists.
Deployment options
Self-host and provider-specific paths stay separate from benchmark evidence so operating constraints are visible before a score becomes the whole decision.
Where to run LongCat-2.0 by API
OpenRouter is the one host we track that publishes a per-token price for it. Prices read from each host’s own pages on November 11, 2026.
| Host | Input /1M | Output /1M | Cached /1M | Context |
|---|---|---|---|---|
| OpenRouter | $0.30 | $1.20 | $0.006 | 1.05M |
Self-host vs API cost
Estimates at 50,000 req/day · 1000 tokens/req average.
Questions
How does LongCat-2.0 perform overall in AI benchmarks?
LongCat-2.0 does not have any source-displayable benchmark rows yet, so this profile does not assign a public score or rank. Documented specifications remain visible, while score-led charts and claims stay unavailable until a published evaluation can be attached to the exact model.
Is LongCat-2.0 open source?
LongCat-2.0 is an open-weight model from Meituan. Its weights can be downloaded for local or hosted deployment, subject to the published license. Open weight does not automatically mean open source: training data and training code may remain private, and commercial restrictions can still apply.
Does LongCat-2.0 have full benchmark coverage on BenchLM?
No. LongCat-2.0 currently has 0 source-displayable rows. The profile exposes published, non-generated evidence and leaves missing categories blank until an exact evaluation is available. Coverage describes how much was measured; it is not a penalty added to an individual benchmark result.
What is the context window size of LongCat-2.0?
LongCat-2.0 has a reported context window of 1M in the exact-model catalog record. The value stays visible, but the profile marks its source link as unavailable instead of presenting it as directly documented. Maximum output length remains separate because providers often publish a different limit.