UCloud-Global.com is the international site of UCloud. It has recently launched a DeepSeek R1 & V3 API page, powered by the UCloud UModelVerse model marketplace. This service supports online access to DeepSeek R1 and V3 models and also allows API integration. You can obtain access to DeepSeek R1 and V3 APIs in just 5 minutes. The service is currently available for free, and new users receive 500,000 free tokens upon registration.
DeepSeek R1 & V3 API page: https://www.ucloud-global.com/en/product/UModelVerse
API Advantages
Comprehensive API interface: UModelVerse provides full-parameter DeepSeek-R1 and DeepSeek-V3 models (671B), supporting flexible API calls.
One-click integration: DeepSeek can be deployed quickly within minutes, making it easy to build enterprise-level knowledge systems.
Low-latency experience: Optimized network ensures smooth performance and global accessibility.
DeepSeek Front-End Experience
After registering with an email or Google account and logging in, users can try 3 free conversations on the frontend. After reaching the limit, you can continue via the console or connect through the API.
Frontend interface
Console interface and experience
API Integration Steps
Step 1: Get API Key
Open the API List page. No parameters are required—just click “Send Request”.
In the popup window, click “Confirm Send Request”.
From the returned list, select the required key according to the model name.
Step 2: Chat API Call
Request
Request Headers
Name
Type
Required
Description
Content-Type
string
Yes
Fixed value: application/json
Authorization
string
Yes
The API Key obtained in Step 1
Request Parameters
Name
Type
Required
Description
model
string
Yes
Model ID
messages
List[message]
Yes
Chat context information. Instructions: (1) messages cannot be empty; each entry represents a conversation round; multiple entries indicate multi-turn chat. Example: single message [{“role”:”user”,”content”:”Hello”}]; multi-turn messages include alternating roles. (2) The last message is the current request; previous messages are history. (3) Role rules: first message must be user or system; last must be user or tool; if no function calls: roles alternate user → assistant → user…
stream
bool
No
Whether to return streaming output. Beam search models must be false. Default: false
stream_options
stream_options
No
Controls whether usage stats are included in streaming responses