OmniDino
Home Models Pricing Guides About Contact Login Get API Key
EN 中文
API Authentication

Create API Key / Access Token

Choose the correct token group, expiration date, and quota, then configure the Key securely in Codex, Claude Code, Cherry Studio, Dify, or your own application.

KEYSecure CredentialAuthenticates every OmniDino API request.
GROUPGroup MultiplierDifferent clients, models, and account pools may require different groups.
EXPExpirationUse no expiration for long-term use, and a shorter term for temporary projects.
LIMITQuota ControlLimit the maximum Credit a single Key can consume.
Before You Begin

An API Key is the secure credential used to connect to OmniDino.

Create separate Keys for different tools and projects so you can control quotas, revoke access, and track usage.

KEY

Separate Management

Use a separate Key for Codex, Claude Code, Cherry Studio, and Dify.

GROUP

Choose a Group

Different clients, models, or account pools may use different groups and billing multipliers.

LIMIT

Quota Control

Set a small quota for testing, then increase it after confirming the model and pricing.

Creation Process

From signing in to copying the token.

01

Sign in to the OmniDino Console

Open https://api.omnidino.com, sign in, then open Tokens or API Keys.

02

Create a New Token

Click Create Token and name it by purpose, such as codex-personal, claude-code, dify-project, or image-test.

03

Choose a Token Group

Different clients, models, or account pools use different groups and multipliers. Choose based on the actual use case. For Codex, select the corresponding CodeX dedicated or Plus pool group in the console.

04

Set an Expiration Date

For beginners, No Expiration avoids unexpected client failures. Temporary tests or shared environments can use 7 days, 30 days, or a shorter period.

05

Set a Quota

The quota is the maximum Credit this token may consume. Start small, confirm calls and billing, then increase it.

06

Submit and Copy the Token

Click Submit. Return to the token list and confirm the new token appears. Click the copy icon on its row, or select it and click Copy Selected Tokens.

07

Store and Configure the Client

Store the copied token securely, then paste it into the installer, CC Switch, Codex, Cherry Studio, or another client configuration.

Multiplier Groups

For now, groups can be understood by their multiplier names.

Group names may change later, but the billing principle remains the same.

0.2×

0.2× Group

Base model usage multiplied by 0.2. Suitable for cost-sensitive use, testing, or specific lower-cost pools.

1× Group

Base model usage multiplied by 1. Suitable for standard calls and everyday use.

2× Group

Base model usage multiplied by 2. It may correspond to a different pool, route, or service strategy.

Available models, group names, and multipliers are determined by what the console shows when creating the token.
Client Configuration

General OpenAI-compatible configuration.

OmniDino General Configuration
Base URL: https://api.omnidino.com/v1 API Key: sk-your-omnidino-key Model: Enter the exact model ID shown in the console

Claude Code Exception

When using native Anthropic-compatible configuration, normally enter the root URL https://api.omnidino.com, rather than automatically appending an OpenAI Chat path.

CodexCherry StudioDifyClaude Code
Treat an API Key like an account password. Never upload it to GitHub, embed it in a public frontend, include it in screenshots, or share it with strangers. If exposed, delete the old Key, create a new one, and review usage logs immediately.
FAQ

Common questions about creating tokens.

Check account balance, token quota, group, model permissions, and model ID. Test authentication with /v1/models before testing a chat request.
Separate Keys make it easier to limit quotas, review usage, identify leaks, and revoke one tool without affecting others.
Account balance is your total Credit. Token quota is the maximum that Key may consume. Requests still fail if the Key quota is exhausted even when the account has balance.
It depends on the console. The safer approach is to create a new Key and update the client configuration.