DeepSeek R1 (0528) is a DeepSeek model available through Merge Gateway via Vertex AI. Use it with Gateway routing policies, spend controls, request logs, and a 65,536 token context window. It supports streaming, structured outputs through at least one Gateway vendor route.
DeepSeek R1 (0528) pricing
| Vendor | Input / 1M tokens | Output / 1M tokens | Zero data retention |
| --- | ---: | ---: | --- |
| Vertex AI | $0.5500 | $2.19 | No |
Test DeepSeek R1 (0528) with Merge Gateway’s Simulator
DeepSeek R1 (0528)
Synced
Synced
Run simulation to see response
—
—
—
Ready to try it out?
Start routing requests to hundreds of large language models in your product within minutes.
Route requests to DeepSeek R1 (0528) with Merge Gateway
Merge Gateway is a unified LLM API that lets your product route requests to DeepSeek R1 (0528) and every other major model through a single endpoint. You get built-in fallback routing, per-request cost tracking, zero data retention support, and observability without changing your application architecture.
To get started in seconds, add our Gateway Implementation skill to your project, or pick your preferred SDK below. Check out our other quick start skills here.
Install the Merge Gateway SDK
Python
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Make your first API call
Python
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Try a diffrent model
Python
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Install the Merge Gateway SDK
Python
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Make your first API call
Python
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Try a diffrent model
Python
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Install the Merge Gateway SDK
Python
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Make your first API call
Python
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Try a diffrent model
Python
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Install the Merge Gateway SDK
Python
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Make your first API call
Python
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Try a diffrent model
Python
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Explore other models available in Merge Gateway
DeepSeek R1 (0528) FAQ
In case you have any more questions on using DeepSeek R1 (0528), we’ve addressed several below.
Heading
What provider owns DeepSeek R1 (0528)?
DeepSeek R1 (0528) is a DeepSeek model.
Which vendors can run DeepSeek R1 (0528)?
Vertex AI is the default listed vendor, and other active vendors may also be available.
What context window does DeepSeek R1 (0528) support?
DeepSeek R1 (0528) supports 65,536 tokens on the primary listed vendor route.
What capabilities does DeepSeek R1 (0528) support?
Gateway currently lists streaming, structured outputs support for DeepSeek R1 (0528) across its available vendor routes.
Try DeepSeek R1 (0528) through Merge Gateway
Route, observe, and control AI requests across providers from one API.
