DataEyesAI uses two independent types of keys:| Key type | Where to get it | APIs it can call | Billing |
|---|
| Model API key | Console → Model API key | All model APIs: text, image, video, audio (https://studio.dataeyes.ai) | Deducted from your model balance by usage |
| Search & Reader API key | Console → MCP Products → Access & Keys | Search, reader, document parsing, and related APIs (https://openapi.dataeyes.ai) | Deducted per call |
Model API key#
Create a key#
When you sign up, 3 keys are created for you automatically, one for each group type, and are ready to use. To manage projects, team members, or environments separately, click "New" on the Model API key page.Group type#
When you create a key, you choose a group type. It decides which channel group your requests are routed to:| Group type | Behavior | Best for |
|---|
| Stability First | Automatically picks the most available channel among your groups | Production |
| Price First | Automatically picks the cheapest channel among your groups | Cost-sensitive batch jobs |
| Specify group | Always uses the group you choose | Locking in a price or channel |
There are two kinds of groups:default (Official price): all models, billed at official prices.
Brand groups (such as gemini, openai, claude-aws): discounted prices for that brand's models. See Group pricing on the model detail page for the exact discount.
Security settings#
When you create or edit a key, consider setting:Quota limit: a USD spending cap for the key. The key stops working once the cap is reached, protecting you from runaway costs caused by bugs.
Expiration: useful for temporary tests or contractor projects.
IP whitelist: only allow calls from specific IPs (one per line, CIDR supported), so a leaked key cannot be abused.
Model limits: optional; restrict the key to specific models. Usually not needed.
Search & Reader API key#
Switch to "MCP Products" at the top of the console and open Access & Keys to see your base URL and API key.The full key is shown only once, when your account is created or when you rotate the key. Afterwards only the first and last characters are shown. Save it right away. If you lose it, click "Rotate" to generate a new key; the old key stops working immediately.
Pass the key in requests#
All APIs require HTTPS. Each protocol uses its standard header, and the gateway supports all of them:| Protocol | Header | Example |
|---|
| OpenAI-compatible (including Search & Reader APIs) | Authorization | Authorization: Bearer sk-xxx |
| Anthropic Messages | x-api-key or Authorization | x-api-key: sk-xxx |
| Gemini native | x-goog-api-key | x-goog-api-key: sk-xxx |
When entering the key in an SDK or third-party tool, enter only the raw string starting with sk-. Do not add the Bearer prefix yourself; the SDK handles it.
Security best practices#
Never put keys in frontend code, mobile app packages, or public repositories. Read them from environment variables instead, for example export DATAEYES_API_KEY=sk-xxx.
Use a separate key per project so you can set limits, disable, and reconcile each one independently.
If you suspect a key has leaked, delete or disable it in the console immediately and create a replacement.
Next steps#