ModelsDeepSeekDeepSeek v4 Pro

DeepSeek v4 Pro

deepseek-v4-pro

DeepSeek-V4-Pro is provided directly by DeepSeek. TokenHub does not provide SLA guarantees for this service. By using this model, users acknowledge and agree to follow DeepSeek's terms of service and should read the relevant terms before use. If the terms are not accepted, use should be stopped.

Published price
From $0.676 / 1M tokensPrices from the model catalog
Billing unit
/ 1M tokens
Context / Max output
1000K / 384K
Listed routes
2
Auto route · $0.676 / 1M tokens

Provider routes

Published route pricing and available performance data. A dash means no data has been published.

ProviderPricingLatencyUptimeSupplyRoute
TencentLive
Input $0.676 / 1M tokens
Output $2.029 · Cache $0.023
1448ms—Verified
DeepSeekLive
Input $0.710 / 1M tokens
Output $2.131 · Cache $0.023
0ms—Verified
Selected pricing · TencentUSD / 1M tokens
Input
$0.676
Output
$2.029
Cache read
$0.023
Cache write
—

Prices are shown in each route’s billing unit. A dash means no price has been published. Source: the selected provider route in OpenAny's public model catalog. A price update timestamp is not supplied.

Time-based pricing · UTC · Tencent

USD / 1M tokens
PEAK1
Mon, Tue, Wed, Thu, FriUTC 01:00–04:00
Input
$1.353
Output
$4.058
Cache read
$0.045
Cache write
—
PEAK2
Mon, Tue, Wed, Thu, FriUTC 06:00–10:00
Input
$1.353
Output
$4.058
Cache read
$0.045
Cache write
—

Prices are shown in each route’s billing unit. A dash means no price has been published.

Model API questions

How do I call DeepSeek v4 Pro through OpenAny?

Use model ID deepseek-v4-pro with an OpenAny key and the operation published in this model's API tab. The model API base is https://api.openany.si/v1. Confirm the protocol and request schema; model availability does not imply every OpenAI API operation is supported.

How is DeepSeek v4 Pro billed?

Compare the published rate and billing unit of the selected provider route. Input, output and cache token rates may differ. Image, audio and video models can use other units. Recorded usage determines the charge under that route's billing contract.

Are Community and Verified routes the same as an official publisher API?

No. Inspect the provider name and supply classification for the specific route. A marketplace listing or a supply label is not a claim of publisher endorsement, identical service or measured uptime. Different route prices may reflect different supply and conditions.

Where do these prices come from, and when were they updated?

Rates come from the provider routes in OpenAny's public model catalog, not an independent quote from the model publisher. The catalog does not supply a price update timestamp. A page or catalog snapshot date is not a price revision date. Compare supply, billing units, tiers and conditions; a lower listed rate alone does not establish equivalent service or explain the price difference.