SShortSingh.
Back to feed

DeepSeek Introduces Time-Based Token Pricing With Higher Baseline Rates

0
·2 views

DeepSeek has rolled out a new peak and off-peak billing structure for its API, effective August 16, 2026, offering off-peak rates at 50% below peak prices. However, the new off-peak prices are still significantly higher than the previous flat rates — DeepSeek V4 Pro input tokens are now roughly 1.5 times more expensive off-peak and up to 3 times more at peak compared to the old pricing. The steepest increase affects cache hits, with V4 Pro cache-hit rates rising up to 6 times off-peak and 12 times during peak hours, a change that heavily impacts long-running agentic workloads. Peak hours are defined as 01:00–04:00 UTC and 06:00–10:00 UTC, which broadly align with China's business day, while the remaining 17 hours qualify as off-peak. Developers using DeepSeek in batch or agent-heavy applications are being advised to schedule intensive workloads during off-peak windows to partially offset the overall price increase.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

PHP & MySQL Dashboard Launched to Manage Cross-Border Personal Shopping

A web-based management dashboard built with native PHP and MySQL has been introduced for international personal shopping businesses. The platform is designed for companies that purchase overseas products on behalf of customers. It centralizes the management of orders, customers, products, shipments, payments, service fees, and delivery status. The tool aims to streamline cross-border order operations from a single interface.

0
ProgrammingDEV Community ·

Developer Builds Unit Testing Framework for AI Agent Skills to Replace Guesswork

A developer frustrated by the lack of rigor in AI agent skill deployment has built an open-source testing tool called skilleval. The tool takes a skill definition file and a prompt, runs a real agent, and lets developers assert on concrete outcomes such as tools used, files modified, cost incurred, and final messages. Unlike other evaluation approaches, skilleval avoids using a second language model to grade the first, relying instead on deterministic, artifact-based assertions. Test results are saved so developers can compare outcomes across skill edits and optionally run multiple iterations to establish a pass rate. The project aims to bring the same accountability to prompt-based agent skills that standard code changes already face through reviews and approvals.

0
ProgrammingDEV Community ·

Developer Builds High-Performance Nutrition and Finance Tracker API Using FastAPI

A developer has built the Daily Ledger API, a lightweight RESTful microservice using Python 3, FastAPI, Pydantic, and AsyncIO to track and analyze daily nutritional intake and financial expenditures. The project is structured into three modular components handling data validation, local JSON persistence, and API routing with asynchronous analytics. Pydantic models enforce strict data contracts, automatically rejecting invalid or malformed payloads with a 422 response before they reach core business logic. Data is persisted locally in a JSON file with safeguards against file corruption and accidental data overwriting. A key feature is the summary endpoint, which uses asyncio.gather() to run nutritional and financial aggregations concurrently rather than sequentially, improving response performance.

0
ProgrammingDEV Community ·

Developer Builds Auto-Curation Tool to Purge Unused Claude Code Skills and Cut Token Waste

A developer running an autonomous Claude Code business generating ¥1.2M per month identified a growing problem: unused AI skill files silently consuming context tokens in every conversation. As Claude Code auto-generates skill files for repeated or corrected tasks, these accumulate and degrade response quality while inflating token costs. To address this, the developer built a weekly automated curation system that tracks skill usage by scanning conversation logs for name mentions. Skills unused for 30 days are flagged as stale, while those idle for 90 days are moved to an archive folder rather than deleted outright. The system is designed to protect manually created skills by only targeting auto-generated files identified by a specific metadata field.