-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Verification Conflict
Automated verification found conflicting information about:
Platform: DeepSeek Open Models
Feature: DeepSeek-V3 / DeepSeek-R1
Current Stored Data
What our data file currently says
{
"name": "DeepSeek-V3 / DeepSeek-R1",
"category": "other",
"status": "ga",
"gating": "free",
"availability": [
{
"plan": "Self-hosted",
"available": "✅",
"limits": "Your hardware",
"notes": "V3: 671B MoE, R1: reasoning model"
}
],
"platforms": [
{
"platform": "Windows",
"available": "✅",
"notes": "Via Ollama (quantized)"
},
{
"platform": "macOS",
"available": "✅",
"notes": "Via Ollama (quantized)"
},
{
"platform": "Linux",
"available": "✅",
"notes": "Best support"
},
{
"platform": "iOS",
"available": "❌",
"notes": "Not practical"
},
{
"platform": "Android",
"available": "❌",
"notes": "Not practical"
},
{
"platform": "Chrome",
"available": "❌",
"notes": ""
},
{
"platform": "web",
"available": "❌",
"notes": "Local only"
},
{
"platform": "terminal",
"available": "✅",
"notes": "Ollama CLI"
},
{
"platform": "API",
"available": "✅",
"notes": "Ollama REST API"
}
]
}
Model Responses
Gemini Flash
Result: No change detected
Full response
Okay, I will check the information provided against available sources to verify its accuracy.
Perplexity
Result: Detected change
Full response
1. Pricing tier availability
INCORRECT. The stored data lists only "Self-hosted" as the plan with availability ✅ and limits "Your hardware". While self-hosting remains valid for open-weight versions of DeepSeek-V3 (671B MoE) and DeepSeek-R1 (reasoning model), DeepSeek also offers these (or close variants like V3.1/V3.2 and R1 distillations) via a hosted API with pay-as-you-go pricing (e.g., V3 at $0.014/$0.028 per 1M input/output tokens; R1 at $0.55/$2.19; V3.2 at $0.26/$0.38), free tiers/trials on most models, and off-peak discounts (e.g., -50% on V3.2). Usage limits vary by API tier (e.g., multimillion-token trials, volume discounts), not just hardware.[1][2][5]
2. Platform/surface availability
CORRECT. Matches stored data: ✅ on Windows, macOS (quantized via Ollama), Linux (best support), terminal (Ollama CLI), API (Ollama REST API or DeepSeek API); ❌ on iOS, Android (not practical), Chrome, web (local only). No evidence of changes; open-weight models remain self-hosted/local via Ollama or similar, with API access as noted.[1][2]
3. Current status
INCORRECT. Stored status "ga" is partially accurate for open-weight self-hosted versions, which are generally available. However, original DeepSeek-V3 and R1 are listed as deprecated in API contexts, replaced by unified V3.2 (handles chat/reasoning) since at least March 2026 with no pricing changes since February 2026.[2]
4. Access gating
CORRECT. Matches stored "free": Open-weight models are free to download/self-host; API has free tiers/trials alongside paid usage.[2][5]
5. Regional availability
No change detected. Stored info ("No restrictions - runs locally. Note: DeepSeek is a Chinese company; some orgs restrict use") remains accurate; no new region-specific limits noted for open/self-hosted versions, which run locally globally.[2]
6. Official URL
No official product/feature page identified in results. DeepSeek API docs cover pricing/models (active): https://api-docs.deepseek.com/quick_start/pricing[7]. For open-weight models, no direct DeepSeek page cited; typically via Hugging Face (not in results). Stored data lacks a URL, so no mismatch.
7. Recent changes
INCORRECT (changes detected). Within last 30 days (post-Feb 2026): No pricing changes since February 2026 for V3.2/R1 successors (updated March 2, 2026); V3.2 fully replaced V3 and R1 as unified chat/reasoning model at flat rates ($0.28/$0.42 per 1M tokens, cache $0.028), deprecating priors. Some promotions (e.g., V3.2-Speciale ends Dec 2025, outside 30 days).[2][3]
Action Required
Please manually verify this feature's current status:
- Check the official pricing page
- Verify platform availability
- Update the data file if needed
- Close this issue with findings
This issue was automatically generated by the pricing verification system.