Independent API gateway
One DeepSeek V4 API for apps and coding agents
Create one DeepSeek-V4.io key and use the protocol your client already understands. Upstream provider credentials and routing remain on our server.
deepseek-v4-flash; the gateway maps it to V4.1 server-side. Text input is supported today. Review model IDs and capability boundaries.What the paid usage pack includes
Paid API access only. DeepSeek-V4.io is independent and is not the official DeepSeek website.
Chat Completions
POST /api/v1/chat/completionsOpenAI SDKs, OpenCode, Pi, Cline, and OpenClaw
Responses
POST /api/v1/responsesCodex and agentic Responses tool loops
Anthropic Messages
POST /api/v1/messagesClaude Code and Anthropic-compatible clients
Make your first request
- Create a paid API key.
Open the Developer Dashboard and save the key when it is shown. - Use the public model id.
Usedeepseek-v4-flash; the gateway maps the upstream model internally. - Stream or call tools.
Structured messages, SSE, tool calls, and tool results are passed through the selected protocol.
curl https://deepseek-v4.io/api/v1/chat/completions \
-H "Authorization: Bearer $DEEPSEEK_V4_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "deepseek-v4-flash",
"messages": [{"role": "user", "content": "Explain this function."}]
}'Billing and service boundary
Paid token packs fund DeepSeek-V4.io web chat and DeepSeek-V4.io API usage. The free signup balance does not allow API key creation.
DeepSeek Platform and OpenRouter accounts, keys, and balances are separate from this service. This is not positioned as a cheaper OpenRouter replacement. The paid outcome is one DeepSeek-V4.io balance, compatible endpoints, setup guides, and usage visibility for the workflows documented here.
Usage is settled after the provider reports input and output tokens. Review requests and token usage in the Developer Dashboard.