API Relay Check
Verify your OmniDino API connection in minutes.
Check the Base URL, API key, model list, Chat Completions, and response latency. Results help troubleshoot configuration issues and do not replace usage, billing, or channel records in the OmniDino console.
URLConnection CheckCheck whether the API Base is reachable and whether the browser can complete cross-origin requests.
AUTHAuthentication CheckUse /models to verify that the API key is valid and authorized.
MODELModel CheckConfirm that the target model exists and run a minimal Chat Completions request.
MSLatency ReferenceRecord browser-side latency for the model-list request and text-generation request separately.
Online Check Tool
Test the OmniDino API directly in your browser.
The information entered is used only for requests from this browser. This page does not intentionally save it to the WordPress database or send it to another testing service.
Security note: Do not test long-lived or high-quota keys on a public computer. Create a dedicated low-quota test key. Browser requests may be affected by CORS, proxies, extensions, and the local network.
API StatusWaiting
Authentication StatusWaiting
Model StatusWaiting
Total Time— ms
omnidino-api-check
Waiting for the check to begin…
If the browser reports Failed to fetch, it does not necessarily mean the API is down. CORS, Cloudflare, security plugins, browser extensions, or a local proxy may be blocking the cross-origin request. Continue with the curl or Postman checks below.
Manual Checks
Use curl to verify authentication and model calls separately.
Replace the example API key and model name with your own real values.
1. Retrieve the Model List
curl https://api.omnidino.com/v1/models \
-H "Authorization: Bearer YOUR_OMNIDINO_API_KEY"2. Chat Completions
curl https://api.omnidino.com/v1/chat/completions \
-H "Authorization: Bearer YOUR_OMNIDINO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "YOUR_MODEL_ID",
"messages": [
{
"role": "user",
"content": "Reply with exactly: OmniDino API connection successful."
}
],
"stream": false,
"max_tokens": 50
}'3. Streaming
curl -N https://api.omnidino.com/v1/chat/completions \
-H "Authorization: Bearer YOUR_OMNIDINO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "YOUR_MODEL_ID",
"messages": [
{
"role": "user",
"content": "Count from 1 to 5."
}
],
"stream": true
}'4. Embeddings
curl https://api.omnidino.com/v1/embeddings \
-H "Authorization: Bearer YOUR_OMNIDINO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "YOUR_EMBEDDING_MODEL_ID",
"input": "OmniDino embedding connection test."
}'5. Image Generation
curl https://api.omnidino.com/v1/images/generations \
-H "Authorization: Bearer YOUR_OMNIDINO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-image-2",
"prompt": "A small blue dinosaur checking an API dashboard",
"size": "1024x1024"
}'
Image generation may incur noticeable charges. When troubleshooting the API connection, test
/models and a low-cost chat model first. After that succeeds, test Images, Embeddings, or high-cost reasoning models.
Recommended Testing Tools
These tools are useful when you prefer not to use the command line.
POST
Postman
Save request collections, environment variables, headers, and JSON bodies, and inspect complete responses.
GitHub
HOP
Hoppscotch
An open-source web API client for quickly testing REST, SSE, WebSocket, and GraphQL.
GitHub
BRUNO
Bruno
An open-source desktop API client whose request collections can be stored locally and managed with Git.
GitHub
INS
Insomnia
Supports REST, GraphQL, gRPC, and environment variables for debugging requests and authentication.
GitHub
CURL
curl
The most direct command-line test, useful for ruling out client configuration and plugin issues.
GitHubRecommended Check Order
Verify each layer in order, starting with the lowest-cost check.
01Create a Test KeySet a low quota and allow only the models you need to test.
02Check /modelsFirst confirm that the domain, HTTPS, key, and authentication path work.
03Test ChatChoose a low-cost model and send a minimal non-streaming request.
04Test Advanced CapabilitiesTest streaming, embeddings, images, or tools as needed.
05Connect a ClientConfigure Cherry Studio, TRAE, Dify, and other tools only after the basic API checks pass.
Common Errors
Use the HTTP status code to narrow down the issue quickly.
Check the Authorization header, Bearer prefix, whether the API key is complete and enabled, and whether copied spaces, line breaks, or quotes were included.
Usually indicates that the key or user group lacks model permission, the channel is restricted, an IP or regional policy blocked the request, or a security rule rejected it.
Check the Base URL and endpoint. OpenAI-compatible URLs normally use
https://api.omnidino.com/v1 as the base. Avoid appending it twice. /v1。The model ID must exactly match the real name in the OmniDino model catalog, including case, hyphens, and version suffixes.
Check the balance, key quota, user-group multiplier, RPM/TPM limits, and upstream rate limits. Reduce concurrency and try again.
The upstream model, channel, reverse proxy, or gateway may be temporarily unavailable. Review OmniDino request logs and cross-check with another model or channel.
Common causes include CORS, Cloudflare, browser extensions, local proxies, HTTPS certificates, or network issues. Verify again with curl, Postman, or a server-side script.
Confirm the request actually targets api.omnidino.com and check whether the client cached another provider, proxy URL, or old Base URL.
Not necessarily. Browser timing includes the local network, DNS, TLS, international routing, and model time-to-first-token. Repeat the test from the target server or actual client environment.
Prove the connection works before integrating the API into production.
Start with /models, complete a minimal chat request with a low-cost model, then test streaming, images, embeddings, and client integration.