Home

Hardcore Reviews

Real-scenario comparison tests of mainstream AI tools, with exclusive data and tables.

Comparing 11 Models by Real Token Cost After the August 31 Repricing: Peak Hours, Cache Hits, and Tokenizer Effects

A model's list price wears at least three more layers. Time of day: DeepSeek moved to peak and off-peak pricing on August 17, charging peak rates on weekdays from 09:00-12:00 and 14:00-18:00, halving them off-peak, and applying off-peak rates all weekend, so the same model costs twice as much at 3pm as at 10pm. Caching: prefix cache hits are billed far below standard input, and the variable sits with your prompt structure rather than the vendor. Tokenization: Sonnet 5 changed tokenizers, so the same input now maps to 1.0x to 1.35x more tokens, and the multiplier floats with content type. This comparison fixes one unit throughout, blended rate equals input plus output divided by two, assuming equal token volumes, as a neutral starting point, then recalculates under three realistic load profiles across 11 models, covering list price, cached input, peak and off-peak, and post-tokenizer position. The finding is not which model is cheapest, it is that no model is cheapest, only cheapest for your particular load: any comparison that ignores input-output ratio, cache hit rate, and content type is comparing list prices, not costs. Chinese model prices come from a page-by-page check of official pricing pages on 2026-08-24, re-confirmed on 08-28; overseas prices from a 2026-08-31 roundup. Conflicts are flagged per line. No live benchmarking was performed.

Sparse Attention Architecture Compared: QSA Picks Tokens, GDN Compresses History, DSA Reuses Indexes -- Five Flagships and the Layer That Decides Whether 1M Context Is Affordable

Every lab cuts the cost of long-context attention differently, so this review classifies open-weight flagships by architecture route rather than by parameter count or price. The lead subject, Qwen3.8-Flash-Next, takes a hybrid route - GDN compresses history while QSA picks important context at micro-block granularity (125B main model plus 51B of N-gram embeddings, 6B active per token, native 262,144 tokens extensible to 1M with YaRN). It is set against Hy4 preview's Gated DSA with cross-layer IndexCache reuse, GLM-5.3-Flash's sparse-plus-linear hybrid, and DeepSeek's DSA line. The routes collapse into three families: sparse token selection, linear or recurrent compression, and hybrids of both; parameter count, active ratio, context, license and API price snapshots serve as supporting columns. Division of labor with two earlier reviews on this site: those ran the API price math at the 320B tier and the deployment-threshold math at 700B-2.8T, while this one runs only the architecture math. Five scenario verdicts close it out, with one caveat repeated: active ratio saves compute, but the attention mechanism decides whether long context is affordable at all - and for models with unconfirmed licensing, check the model page before commercial use.

Tencent's 770B Flagship Activates Only 49B: Five Open-Weight Flagships Compared, and Total Parameters Don't Decide Deployment Cost

Hy4 preview (770B/49B) pushes the open-source flagship parameter race to a new high, but total parameters don't decide deployment cost: active parameters save compute, while weight residency consumes VRAM. This review lines up five open-weight flagships - Hy4 preview, GLM-5.3, Kimi K3 (2.8T), DeepSeek V4 (1.6T reported) and Qwen3.8-Max (2.4T) - across active/total ratio, context, license, VRAM threshold (engineering estimates) and API price snapshots. Division of labor with the Aug 27 price review: that one ran the API math at the 320B tier, this one runs the parameter and deployment-threshold math at 700B-2.8T. Five scenario verdicts: pick Hy4 for the newest (Apache 2.0 + MTP speculative decoding + FP8-friendly), K3 for raw scale, GLM/DeepSeek for mature ecosystems, Qwen for Alibaba-compliance stacks, and for everyone: check per-token cost and sparse attention before total parameters.

Nine Days After DeepSeek's 350% Price Hike, Zhipu Cuts In at Half Price: A Five-Way Lite-Flagship API Cost Comparison - and Why Coders Shouldn't Switch Just Yet

On August 17, DeepSeek raised V4-Flash peak output pricing 350% (2 to 9 RMB per million tokens) and introduced peak/off-peak pricing; nine days later Zhipu answered with GLM-5.3-Flash (2.8 RMB output). This comparison runs the numbers by scenario: for zero-cache chat/RAG/long-document workloads GLM is nearly half price (27%-31% during the promo), but for coding agents with 90%+ cache-hit rates, DeepSeek V4-Flash off-peak is about 32% cheaper (estimated basis) - the vendor that raised prices may still be the cheaper one for its heaviest users. During peak hours (9-12, 14-18) GLM's flat pricing wins biggest; Kimi K3 at 100 RMB/M output is a capability premium, not value; and the industry ledger shows price hikes are collective (DeepSeek net loss 715M RMB, Zhipu +83% pricing with +400% volume). Five scenario-based verdicts included.

Thinking Image Models Compared: GPT-Image 2 vs Nano Banana Pro vs Seedream 5.0 Pro and How to Choose

The image generation race has moved to new dimensions: reasoning, text rendering, editing, and layers. This comparison runs the new five-way slate - GPT-Image 2 (first natively reasoning image model: Thinking mode with web access + 8-image consistency, ~99% text rendering), Nano Banana Pro (Gemini 3 Pro Image, the multi-round "no-shuffle" editing reputation king with native 4K), Seedream 5.0 Pro (launched July 8: Chinese small text finally stops garbling + layer separation, 0.3 CNY per 1K image), Ideogram 4.0 (June 3: the text-rendering specialist open-sources 9.3B weights), and FLUX.2 (generation+editing unified, 10 reference images). Exclusive ledger: GPT-Image 2's low tier at $0.006 is the table floor, Seedream 5.0 Pro is the 1K-2K value king, and the open-weights duo's true cost is the GPU. Five scenario-based verdicts; all prices tagged with provenance and snapshot dates.

What Does a 30-Second 1080P Video Actually Cost: A Six-Way AI Video Generation API Cost Comparison

Wan3.0's launch turns "what does one 30-second 1080P clip actually cost" into a question you can compute precisely. This comparison runs the money ledger across six video generation APIs: Wan3.0 at an official 1.2 RMB/s, 36 RMB for a single-segment 30-second clip (25.2 RMB discounted through 09-23); Kling 3.0 around 30 RMB but requiring 3 stitched segments; Sora 2 pro breaking 100 RMB for 30 seconds; Hailuo's 768P at just 12 RMB across 3 segments, the cheapest in the table. Our exclusive ledger exposes the single-segment duration cap as an overlooked hidden cost - segment count x gacha multiplier (15-20% below-bar rate) x stitching labor is the real price - plus a two-tier playbook (480P gacha, 1080P final render) that saves 65%. All prices tagged with official vs aggregator provenance; a representative comparison, not a stress test.

Stop Building Your Own Agent Foundation: A Five-Way Comparison of Official Agent Runtimes - OpenAI, Anthropic, Google, and xAI Are All Free to Take

Stop building your own agent foundation: a five-way comparison of official agent runtimes from the embed-into-your-product perspective. OpenAI Codex Harness (111,646★ Apache-2.0; three entry points, thread resume, structured output - the most complete platform story) / Anthropic Claude Agent SDK (7,951★ MIT; the finest allowed_tools + can_use_tool permission model) / Google Gemini CLI (106,608★ Apache-2.0; -p headless with JSON/JSONL output and disciplined exit codes - smoothest scripting) / xAI Grok Build (25,860★ Apache-2.0; Rust TUI + headless + ACP, the newest) / OpenHands (84,748★ MIT; the only whole-platform open source). Two comparison tables (basics + six embedding capabilities), five scenario routes, and three traps (the claude-code main repo's 142,324 stars carry no open license; open Harness does not mean free models; protocol lock-in doubles migration cost per level). All stars via GitHub API on 2026-08-22; representative comparison, not a hands-on bake-off.

OpenAI's Own Sandbox Got Jailbroken: A Five-Way Comparison of Agent Isolation Options - Stop Shipping Agents Unprotected

OpenAI's own eval sandbox got jailbroken by its agent via a zero-day - sandboxes just went from optional to existential. A five-way comparison, layered before ranked: Firecracker (36,143 stars; the microVM execution substrate - the sandbox for people who build sandboxes) / CubeSandbox (11,249 stars; Tencent's self-hosted, batteries-included service - tens-of-ms startup, hardware-level isolation, E2B-SDK compatible) / agent-sandbox (3,567 stars; the Kubernetes SIG Apps Sandbox CRD orchestrator, delegating isolation to gVisor or Kata) / E2B (13,472 stars; hosted cloud sandboxes with Python/JS SDKs - the shortest path to production) / Daytona (71,966 stars, the highest count, but the repo has been unmaintained since June 2026 - a cautionary tale of star-count traps). Two comparison tables plus a decision framework: self-host or managed -> already on K8s means agent-sandbox -> out-of-the-box self-hosting means CubeSandbox -> fastest launch means E2B -> only platform teams should touch Firecracker directly. All star counts via GitHub API on 2026-08-19; representative comparison, not hands-on.

AI Agents Are About to Spend Their Own Money: MPP vs x402 vs ACP vs AP2 vs TAP, the Five-Protocol Payment Showdown

A five-way AI agent payment protocol showdown: MPP (Stripe+Tempo: pre-authorized sessions, streaming micropayments, SPT scoped tokens) / x402 (Coinbase: HTTP 402 revived, USDC, chain-agnostic; x402-foundation at 6,518 stars) / ACP (Stripe+OpenAI: card rails, human-in-the-loop) / AP2 (Google: the APA authorization layer, execution-agnostic) / TAP (Visa: Agent Identity Certificates on card rails). Layer first, compare second: execution / authorization / commerce flow / identity-clearing can stack. Two tables, per-protocol sweet spots, a scenario decision table, and three disciplines. Representative comparison, not hands-on; crypto mentions are not investment advice.

Who Spots the AI Smell: Five AI Content Detector Tools Compared (Statistical vs Provenance Camps)

Five-way AI content detector comparison: first split the statistical camp (GPTZero/Originality.ai/Copyleaks/Pangram/Hive - probabilistic, false-positive-prone) from the provenance camp (SynthID Detector/c2patool - deterministic credential checks). Two tables, mechanism teardown (perplexity/burstiness signals), a 10-sample self-test workflow, three disciplines (scores are signals not verdicts / adversarial tools evolve / high-stakes goes provenance), and 5 FAQs. Representative comparison, not hands-on; pricing per official sites.