General Request Specifications (Base URL & Authentication)

Before initiating API requests, please familiarize yourself with our platform's global network endpoints (Base URLs) and standard authentication methods for different business lines.

1. Base URL

To ensure physical isolation of underlying computing resources and ultra-fast response times, DataEyesAI allocates independent endpoints for "Large Language Models (LLMs)" and "Search & Reader" services. Please select the appropriate Base URL based on the product you are calling.

1.1 LLM API Endpoints (For Text, Image, and Video Models)

Whether you are integrating with third-party tools (e.g., ClaudeCode, OpenClaw) or initiating code requests from a server, we strongly recommend using the following global primary endpoint by default. This node automatically routes your traffic through the optimal international leased lines:

https://cloud.dataeyes.ai

Region-Specific / Backup Nodes (Advanced Options)
If you encounter network issues (e.g., corporate firewall blocking), you may try the following backup nodes. Your LLM API Key is valid across all these endpoints:

Node Type	Base URL	Usage Scenario
Silicon Valley Direct	`https://cloud.dataeyes.ai`	Recommended default; high speed and stability.
CN2 Cross-border	`https://cloud-cn.dataeyes.ai`	Optimized CN2 lines for complex network environments.
HK Transit Node	`https://cloud-hk.dataeyes.ai`	Suitable for servers deployed in the Asia-Pacific region (Excluding Mainland China).

Tip: In most AI clients (e.g., Chatbox) or IDE plugins, simply enter the addresses above into the Base URL or API Endpoint field. (Note: Some plugins may require the /v1 suffix at the end; please follow the specific plugin's instructions).

1.2 Search & Reader API Endpoints (For Web Search and Doc Parsing)

When calling dedicated data acquisition interfaces such as /v1/search or /v1/reader, please ensure you use the following independent endpoint:

https://api.dataeyes.ai

(Note: When using this endpoint, you must use the exclusive API Key generated within the "Search & Reader" product section.)

2. Authentication

DataEyesAI supports both HTTP and HTTPS globally and utilizes the industry-standard Bearer Token method for authorization.

You must include your corresponding API Key in the Header of every HTTP request.

Header Format Example:

(Note: There must be a single space between Bearer and your API Key.)

3. Data Format (Content-Type)

Unless otherwise specified (e.g., file uploads), we use JSON format for both requests and responses. Ensure your request Header includes:

Next Steps

Now that you have configured the Base URL and authentication for your product, you can:

Consult the Efficiency Tools Integration Guide to fill your Key and Base URL into your development tools.

Or start coding immediately by calling the Chat Completions API.

Base Url

General Request Specifications (Base URL & Authentication)#

1. Base URL#

1.1 LLM API Endpoints (For Text, Image, and Video Models)#

1.2 Search & Reader API Endpoints (For Web Search and Doc Parsing)#

2. Authentication#

3. Data Format (Content-Type)#