- deepseek/deepseek-v4-pro
deepseek/deepseek-v4-pro
- context · $0.3480 / M input tokens · $0.6960 / M output tokens
DeepSeek V4 Pro is a DeepSeek model route on OurToken for developers who need a higher-capability option for reasoning, coding, chat, and production assistant workloads.
Pricing
Pay-per-use
No upfront costs, pay only for what you use
API Usage
API Access Guide
Code examples
Use the OurToken API endpoint for this model. The examples below use direct HTTP requests and the recommended endpoint for the model family.
curl https://api.ourtoken.ai/v1/chat/completions \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '{
"model": "deepseek-v4-pro",
"messages": [
{
"role": "user",
"content": "Hello!"
}
],
"max_tokens": 256
}'Chat Completions API Reference
Create a chat response with the OpenAI Chat Completions-compatible endpoint. Use https://api.ourtoken.ai/v1 as the SDK Base URL and POST /chat/completions as the endpoint.
Authorization
| Content-Type | application/json |
| Authorization | Bearer YOUR_API_KEY |
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
| model | string | Required | Model ID to call. |
| messages | array<object> | Required | Conversation messages sent to the model. |
| max_tokens | integer | Optional | Maximum number of output tokens. |
| temperature | number | Optional | Sampling temperature. |
| top_p | number | Optional | Nucleus sampling parameter. |
| stream | boolean | Optional | Whether to return a streaming response. |
| stream_options | object | Optional | Additional options for streaming responses. |
| tools | array<object> | Optional | Tools available to the model. |
| tool_choice | string | object | Optional | Controls how the model selects tools. |
| response_format | object | Optional | Controls structured output, such as JSON object responses. |
Response Body
| Field | Type | Required | Description |
|---|---|---|---|
| id | string | Required | Unique chat completion identifier. |
| object | "chat.completion" | Required | Object type returned by the Chat Completions API. |
| created | integer | Required | Unix timestamp when the response was created. |
| model | string | Required | Model that produced the response. |
| choices | array<object> | Required | Candidate responses returned by the model. |
| choices[].message.role | string | Required | Role of the returned chat message. |
| choices[].message.content | string | Optional | Text content in the returned chat message. |
| choices[].finish_reason | string | Optional | Reason generation stopped. |
| usage | object | Optional | Token usage information for the chat completion. |
| usage.prompt_tokens | integer | Optional | Input token count. |
| usage.completion_tokens | integer | Optional | Output token count. |
| usage.total_tokens | integer | Optional | Total token count. |
| usage.prompt_tokens_details | object | Optional | Breakdown of input token usage. |
| usage.prompt_tokens_details.cached_tokens | integer | Optional | Tokens served from cache. |
Model Introduction
DeepSeek deepseek-v4-pro
DeepSeek V4 Pro is a DeepSeek model route on OurToken for developers who need a higher-capability option for reasoning, coding, chat, and production assistant workloads.
DeepSeek V4 Pro gives teams a DeepSeek route for application work where model quality, predictable pricing, and a simple API integration path matter. Use DeepSeek V4 Pro API when you want to test DeepSeek workflows through the OurToken unified API while keeping model IDs, usage logs, and price review in one dashboard.
Why It Looks Great
- 80% of the official DeepSeek V4 Pro reference price for input and output tokens.
- OpenAI-compatible API setup through the same OurToken endpoint used by other supported models.
- Clear cache read and cache write pricing for workloads that use cached prompt tokens.
- Useful for evaluating DeepSeek chat, coding, reasoning, and assistant workflows without separate provider-specific integration.
- Dashboard logs and usage visibility help teams review request cost after launch.
Key Features
- Model ID: deepseek-v4-pro
- Input price: $0.3480 per 1M tokens on OurToken
- Output price: $0.6960 per 1M tokens on OurToken
- Cache read price: $0.0030 per 1M tokens on OurToken
- Cache write price: $0 per 1M tokens on OurToken
- Provider: DeepSeek
Specifications
DeepSeek V4 Pro API Features for Developers
Use DeepSeek V4 Pro API on OurToken for unified DeepSeek V4 API access, transparent pricing, cache cost visibility, model ID setup, and production evaluation.
Unified Access
Call DeepSeek V4 Pro API through the OurToken unified endpoint while keeping model access, API key management, and usage history in one place. Developers can use the deepseek-v4-pro model ID without maintaining separate provider-specific integration paths.
Pricing Clarity
Review DeepSeek V4 Pro API pricing before scaling traffic. OurToken lists $0.3480 input and $0.6960 output per 1M tokens, making the DeepSeek V4 Pro pricing ratio easy to explain while keeping the DeepSeek V4 Pro price visible.
Cache Costs
Plan repeated-context workloads with explicit cache pricing. DeepSeek V4 Pro API cache read is listed at $0.0030 per 1M tokens on OurToken, while cache write is $0, helping teams separate cache behavior from normal input and output spend.
Coding Workflows
Use DeepSeek V4 Pro for code explanation, debugging notes, implementation planning, and assistant-style engineering tasks. Test repository prompts, coding conventions, expected outputs, and latency before routing production developer workflows to this model.
Benchmark Review
Use DeepSeek V4 Pro benchmark claims as evaluation prompts, not production guarantees. Competitor content highlights coding, reasoning, and agentic benchmark results, but teams should compare those claims against their own prompts, logs, and quality targets.
Production Logs
Track request count, input tokens, output tokens, cache read tokens, and spend in OurToken history. This helps teams compare DeepSeek V4 pricing against real traffic instead of relying only on benchmark pages or provider listing assumptions.
How to Use DeepSeek V4 Pro API on OurToken
Create an API key, copy deepseek-v4-pro, compare DeepSeek V4 Pro API pricing, call the unified endpoint, and monitor real usage.
Create API Key
Create an OurToken API key from the dashboard and store it in a secure server-side environment variable. This gives your backend access to DeepSeek V4 Pro API while keeping credentials out of client-side code and public repositories.
01Copy Model ID
Use deepseek-v4-pro as the model value in your request body. Keeping the exact model ID in configuration helps developers avoid naming variants when comparing DeepSeek V4 API routes across local tests, staging traffic, and production deployments.
02Call Unified Endpoint
Send requests to the OurToken unified API endpoint with your API key, model ID, and prompt payload. Existing OpenAI-compatible request patterns can usually be reused after changing the base URL, credential, and model value.
03Compare Pricing
Compare DeepSeek V4 Pro pricing before rollout: OurToken lists $0.3480 input, $0.6960 output, and $0.0030 cache read per 1M tokens. Use those values to estimate DeepSeek V4 Pro price for your expected prompt, output, and cache token volumes.
04Test Benchmarks
Treat every DeepSeek V4 Pro benchmark claim as a starting point for your own evaluation. Run representative coding, reasoning, retrieval, and assistant prompts, then compare response quality, latency, token usage, and error handling against production requirements.
05Monitor Cost
After launch, review OurToken history logs for request count, input tokens, output tokens, cache read tokens, and spend. Real usage data helps teams compare DeepSeek V4 pricing against actual traffic instead of relying only on provider listing assumptions.
06DeepSeek V4 Pro API FAQ
Answers about DeepSeek V4 Pro API pricing, DeepSeek V4 API access, cache costs, model ID setup, benchmark claims, and production evaluation.