Tabbit
ResourcesBlogModels
Tabbit LogoTabbit

Tabbit — The AI Browser that Works for You

Topics

  • AI Browser Resources
  • Agentic Browser Resources
  • Browser Downloads and Install Guides
  • Browser Comparisons
  • AI Browser Alternatives
  • Browser Productivity Resources

Popular Guides

  • AI Browser
  • Agentic Browser Download
  • Best AI Browser 2026: Top 9 Tested & Ranked
  • AI Browser Download
  • Free AI Browser
  • Best AI Browser 2026
  • AI Browser Comparison 2026
  • AI Browser for Windows
  • AI Browser for Mac
  • Chrome Alternative 2026

Events

  • Tabbit Skill Competition
  • KPOP SBTI Fandom Personality Test
  • Tabbit Campus Creator Program
  • fifi's Picks: AI Skills for Research Papers
  • User Survey

About

  • Tabbit Blog
  • Press & Media
English
简体中文English
Reviews and evidence

LongCat 2.0 · Community source · Personal experience

r/vibecoding field test: LongCat 2.0's "insane" pricing — a real bill with free cache hits

A user tested a $2 package containing 50 million tokens: a single task used 27 million prompt tokens, but only 570,000 tokens were deducted because of cache hits. The official rule — "cache hits are not billed; only misses and output count" — expands effective usage to roughly 2 billion tokens in a real agent workflow, making this the most counterintuitive part of LongCat's pricing.

Unverified: the original source could not be rechecked. Historical figures below are not current verified results.

Community sourcePersonal experienceEdited 2026-09-20

Test conditions

Model/version
LongCat-2.0; source date: 2026-08-18.
Harness/task
Motivation: The user was intrigued by Meituan's LongCat 2.0 but hesitant because there were not many benchmarks. Everyone was praising Owl Alpha, though, and "it turned out to be the same model."; Purchase: The official 50M-token package costs $2 (the actual charge was €0.86, "not sure why"); installing AliPay on a phone was required and took about 15 minutes.
Sample/gaps
Limitations noted: A user tested a $2 package containing 50 million tokens: a single task used 27 million prompt tokens, but only 570,000 tokens were deducted because of cache hits. The official rule — "cache hits are not billed; only misses and output count" — expands effective usage to roughly 2 billion tokens in a real agent workflow, making this the most counterintuitive part of LongCat's pricing.

Key data and applicable tasks

One-sentence takeaway

A user tested a $2 package containing 50 million tokens: a single task used 27 million prompt tokens, but only 570,000 tokens were deducted because of cache hits. The official rule — "cache hits are not billed; only misses and output count" — expands effective usage to roughly 2 billion tokens in a real agent workflow, making this the most counterintuitive part of LongCat's pricing.

Original report (key points)

  • Motivation: The user was intrigued by Meituan's LongCat 2.0 but hesitant because there were not many benchmarks. Everyone was praising Owl Alpha, though, and "it turned out to be the same model."

  • Purchase: The official 50M-token package costs $2 (the actual charge was €0.86, "not sure why"); installing AliPay on a phone was required and took about 15 minutes.

  • Key billing rule: The 50M tokens apply only to cache misses or output; cache hits are free!

  • Test: One task used 27 million tokens (apparently the total prompt/context volume), while the bill deducted only 570,000 tokens.

  • Conclusion: "At this rate I guess I can use around 2 billion effective tokens lol."

Verification and applicable limits

  • This billing model matches the official pricing page (the pricing entry in prompt directory 01: Cached Input ¥0.10 → discounted ¥0.04, far below Uncached ¥5 → ¥2). It is also consistent with OpenRouter's 88.92% cache-hit rate and actual weighted input price of $0.03872/M (review 03), confirming that caching is the core lever behind LongCat's value.

  • Best-fit tasks: Agents that repeatedly reread the same context (coding loops and long-document research) benefit most (the same conclusion as AlphaSignal); one-shot prompts receive almost none of the caching benefit.

  • Limits: These prices were promotional ($2 package; the $4.9 package had a 67% discount), and the current price should be checked on the platform. AliPay registration is a barrier for users in China (other commenters mentioned needing a phone number/AliPay; international users can bypass it through OpenRouter/Nous Portal channels; see prompt directory 03/06).

What this supports

  • A user tested a $2 package containing 50 million tokens: a single task used 27 million prompt tokens, but only 570,000 tokens were deducted because of cache hits. The official rule — "cache hits are not billed; only misses and output count" — expands effective usage to roughly 2 billion tokens in a real agent workflow, making this the most counterintuitive part of LongCat's pricing.
  • Motivation: The user was intrigued by Meituan's LongCat 2.0 but hesitant because there were not many benchmarks. Everyone was praising Owl Alpha, though, and "it turned out to be the same model."

What this does not support

  • A user tested a $2 package containing 50 million tokens: a single task used 27 million prompt tokens, but only 570,000 tokens were deducted because of cache hits. The official rule — "cache hits are not billed; only misses and output count" — expands effective usage to roughly 2 billion tokens in a real agent workflow, making this the most counterintuitive part of LongCat's pricing.

Method, limits, and reproduction

The figures, task set, reasoning tier, and client conditions apply only to the listed source and collection snapshot. Different versions, harnesses, or providers must not be compared directly; undisclosed parameters remain unknown.

For a reproduction, fix the model version, provider or client, reasoning tier, tools, task-set version, sample count, and collection date, and record failures, retries, and human corrections. Full steps are in the source notes below.

Original source

Reddit (r/vibecoding) · u/PedroSanchezPSOE · Original publication date Unknown · Site edit date 2026-09-20

Open original source

LongCat 2.0

Compare LongCat 2.0 in Tabbit

Download the Tabbit client to check model access

Read the full analysis

Overview · English

LongCat 2.0: what changed, where to use it, and what the price misses

LongCat 2.0 combines 1M context, open weights, and low provider pricing with real questions about tooling, data terms, and operational cost.

Related reviews

OpenRouter Channel Data: LongCat-2.0 Pricing, Measured Performance, and Third-Party Benchmarks (Artificial Analysis)The OpenRouter page provides a third-party view beyond the official figures: LongCat-2.0 is listed at $0.30/$1.20 per 1M tokens (with a 60% discount at collection time), while the actual weighted transaction price for input was only $0.03872/M (88.9% cache-hit rate); throughput was P50 29 tok/s, three-day availability 99.93%, and tool-call error rate 0.90%, with real traffic mainly coming from Hermes Agent (7.77B tokens) and Claude Code (3.31B tokens).LongCat-2.0 Official Model Card: Specifications and Official Benchmarks (Including Comparison Tables with Gemini/GPT-5.5/Claude Opus)The official model card is the primary authoritative source for judging LongCat-2.0's suitable tasks: it scores 59.5 on SWE-bench Pro, ahead of GPT-5.5 (58.6) and Gemini 3.1 Pro (54.2), and reaches 70.8 on Terminal-Bench 2.1. However, it trails GPT-5.5 and Claude Opus 4.8 on several benchmarks including BrowseComp, GPQA, and IFEval—in short, it is strong at coding and agent tasks, but not a leader in retrieval and general reasoning.LongCat-2.0 Official Technical Blog: Architecture, Training on Domestic Compute, and Inference Deployment (Release Notes)The official technical blog provides the complete technical foundation for LongCat-2.0 (LSA sparse attention, N-gram Embedding, 6D parallel training on domestic compute, and prefill-decode disaggregated deployment), making it useful for assessing the model's intended long-context and Agent capabilities, as well as reproducing the official benchmarks and deployment path.eesel Independent Review: LongCat-2.0's Agent Reliability and Hard Blockers to Production DeploymentThis independent review separates LongCat-2.0 into two questions: "can the model complete Agent work?" and "can the product enter enterprise production?" Public user reports support it as an inexpensive, stable coding executor, but its context specifications, tool contract, and data-governance documentation are insufficient to pass a sensitive-data production review.LongCat-2.0 API Platform Quick Start (Official Quick Start + Chat Completions Reference + Pricing)The LongCat Claude Code guide configures a compatible endpoint and keeps the first task in a disposable worktree.LongCat-2.0 Chat Template and Tool-Calling Configuration (Official Hugging Face Model Card)The official model card’s chat template and tool-call examples are converted into a local inference configuration check.Claude Code Integration with LongCat-2.0 (Official Documentation)The official LongCat integration guide configures a named client and keeps the first run observable and reversible.Official Account Showcase: Five “One-Prompt Generation” Creative Projects (Voxel/3D/CG/Landing Page/Mini-game)Source “Official Account Showcase: Five “One-Prompt Generation” Creative Projects (Voxel/3D/CG/Landing Page/Mini-game)” is organized as an executable task guide; its environment, inputs, and acceptance boundary follow the source.