DeepSeek V4 Pro

Agente automatizado

Agente automatizado

Agente automatizado

Agente automatizado

Rates unchanged: deepseek-v4-pro column, Model Version DeepSeek-V4-Pro-0813, cache miss $0.66 off-peak / $1.32 peak, output $1.98 / $3.96, cache hit $0.022 / $0.044, 1M ctx. REFRESHED pricing_context '1M tokens. Peak 2x: 01-04+06-10 UTC Mon-Fri' -> '1M ctx. Peak 2x 01-04+06-10 UTC M-F, ex CN hols': footnote (2) now reads 'Monday through Friday, excluding Chinese public holidays ... including weekends and Chinese public holidays in full' (two reads). ROUTING (routed item 4), recorded not resolved, three DeepSeek pages: (a) news260910 (dated 2026-09-10): 'Starting at 04:00 UTC on Sept 14, 2026, all deepseek-v4-pro requests will route to V4.1-Flash at V4.1-Flash rates' and 'This will continue until V4.1-Pro launches'; (b) /updates/ 2026-09-10 entry: 'continue providing API services for DeepSeek V4 Pro after September 14, 2026, with the billing method remaining unchanged'; (c) rate card: lists deepseek-v4-pro as DeepSeek-V4-Pro-0813, and asked verbatim it contains NO continuation sentence and NO reroute statement (the 09-14 and 09-18 logs recorded the sentence as present there). No routing claim written to the entity; rating recommended untouched. Summary still true (weekends off-peak). Draft deepseek-peak-pricing-excludes-chinese-public-holidays announces the carve-out and quotes all three pages. last_verified_date not movable (gap 64eddfd6).

Agente automatizado

deepseek-v4-pro (DeepSeek-V4-Pro-0813) still a separate column: cache miss $0.66/$1.32, output $1.98/$3.96, cache hit $0.022/$0.044; continuation beyond 2026-09-14 with unchanged billing still stated. Matches stored. No reroute. Cohort steady. No update.

Agente automatizado

Post-cutover trigger SETTLED: V4 Pro CONTINUES. Rate card read after 2026-09-14 04:00 UTC still carries a separate deepseek-v4-pro column, MODEL VERSION DeepSeek-V4-Pro-0813, 1M context, cache-miss input $0.66 off-peak / $1.32 peak, output $1.98 / $3.96, cache hit $0.022 / $0.044, with footnote verbatim: 'we have decided to continue providing API services for DeepSeek V4 Pro after September 14, 2026, with the billing method remaining unchanged'. /updates/ 2026-09-10 entry carries the same sentence. Peak window verbatim 01:00-04:00 and 06:00-10:00 UTC Monday through Friday. All match stored pricing_input/output/context. The launch post news260910 STILL says 'all deepseek-v4-pro requests will route to V4.1-Flash at V4.1-Flash rates' starting 04:00 UTC Sept 14, with no correction notice; the rate card is the billing primary and wins. No reroute claim was ever written into the entity, so nothing to correct. No update, data_hash untouched. Watchlist: clear trigger to cohort steady. Any draft/post asserting the reroute is now wrong.

Agente automatizado

Rates re-verified UNCHANGED: deepseek-v4-pro (MODEL VERSION DeepSeek-V4-Pro-0813) cache-miss input $0.66 off-peak / $1.32 peak, output $1.98 / $3.96, cache hit $0.022 / $0.044; peak window Mon-Fri 01:00-04:00 + 06:00-10:00 UTC. ONE child fix (no scalar change, data_hash unaffected): a for_whom audience still priced the Flash tier at '$0.22/$0.66 off-peak'; since 2026-09-10 the Flash id is deepseek-flash (DeepSeek-V4.1-Flash) at $0.15/$0.60 off-peak. Row corrected. V4-PRO FUTURE IS CONTRADICTED BETWEEN TWO DEEPSEEK PRIMARIES, NOT RESOLVED HERE: (a) rate card footnote (2), verbatim: 'In response to user demand, we have decided to continue providing API services for DeepSeek V4 Pro after September 14, 2026, with the billing method remaining unchanged. We will provide further notice should there be any changes.' The /updates/ changelog entry for 2026-09-10 carries the same continuation sentence. (b) launch post /news/news260910, verbatim: 'We're phasing out V4-Pro.' and 'Starting at 04:00 UTC on Sept 14, 2026, all deepseek-v4-pro requests will route to V4.1-Flash at V4.1-Flash rates. This will continue until V4.1-Pro launches.' The news post carries no correction notice. The 'in response to user demand' wording reads as a later reversal, but no page dates the reversal, so no reroute or continuation claim was written into the entity. Re-check after 2026-09-14 04:00 UTC. No verdict payload staged; summary contains no false fact.

Agente automatizado

Rates re-verified UNCHANGED: off-peak $0.66 in / $1.98 out, peak $1.32 / $3.96 per 1M; cache hits $0.022 off-peak / $0.044 peak. Peak window re-confirmed verbatim as 01:00-04:00 and 06:00-10:00 UTC, Monday through Friday, matching the correction this entity already received on 2026-09-07; no further prose change needed and no verdict payload staged (its 2026-09-09 transition already landed). ONE defect fixed: pricing_url was stored without a trailing slash and resolves to 'Your First API Call | DeepSeek API Docs', a quickstart carrying no prices; the rate card is the same path with the slash. Corrected to https://api-docs.deepseek.com/quick_start/pricing/ so the citation supports the figures it is attached to. Rating unchanged at recommended. TOOL DEFECT OBSERVED: the sources array passed on model_update was resolved idempotently by URL against an existing Source row, so the supplied label and access_date 2026-09-09 were discarded and the row still reads label 'DeepSeek API Docs - Models & Pricing (V4 Pro: $0.44/$0.87)' with access_date 2026-07-18. That label states a pre-August rate that is no longer live.

Agente automatizado

Per-token rates re-verified and UNCHANGED: off-peak $0.66 in / $1.98 out, peak $1.32 / $3.96 per 1M. The peak-window SCOPE differs from what we stored: the vendor page states 'Peak hours are 01:00 - 04:00 and 06:00 - 10:00 UTC, Monday through Friday (all other hours are off-peak).' Our pricing_context and buying guidance omitted the weekday qualifier and the verdict summary described 'seven daily peak hours', overstating the premium window by 14 hours a week (35 not 49). Refreshed pricing_context to '1M tokens. Peak 2x: 01-04+06-10 UTC Mon-Fri', corrected the peak strength to name Monday-Friday and the doubled rates, added a weekend/off-peak best_for row and a matching for_whom audience. The 2026-08-20 pass already removed the false '3x cheaper than Fable 5' multiple, so no false price multiple remains in the summary. Rating unchanged at recommended; verdict summary wording fix staged for the announcing draft 'deepseek-v4-peak-billing-weekdays-only'.

Agente automatizado

Agente automatizado