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

Use Dify and OmniDino to build production-ready AI applications.

Connect OmniDino text models, Embedding, Rerank, and tool-calling capabilities to Dify, then quickly build customer service systems, knowledge bases, automated workflows, and business applications with visual Workflows, Chatflows, Knowledge, and Agents.

FLOWVisual WorkflowsConnect inputs, models, knowledge retrieval, tools, conditions, and outputs with nodes.
RAGKnowledge BaseUpload documents and build RAG applications with Embedding and retrieval nodes.
AGENTAgentLet the model autonomously select tools, execute steps, and iterate on tasks.
SHIPPublish ApplicationsPublish as a Web App, API, embedded component, or internal workflow.
Platform Overview

What is Dify?

Dify is an open-source Agentic Workflow and AI application platform that integrates model providers, workflows, knowledge bases, tools, and application publishing.

Cherry Studio is for chatting. Dify is for building applications.

In Dify, you can embed OmniDino models into a complete business process. After receiving user input, the system can search a knowledge base, evaluate conditions, call HTTP APIs or tools, and then have the model generate the final answer.

Workflow / ChatflowUse nodes to design fixed, debuggable, and repeatable business processes.
Knowledge / RAGUpload company documents so the model can answer from private materials instead of relying only on public knowledge.
Agent / ToolsLet models that support Function Calling autonomously choose search, HTTP, database, or custom tools.
Deployment Options

Choose Dify Cloud or the self-hosted Community Edition.

Dify Cloud

Best for quick evaluation and lightweight projects, without maintaining databases, queues, plugin runtimes, or upgrades yourself.

Start creating applications immediately after signing up
No server deployment or maintenance required
Ideal for testing OmniDino model compatibility
Features and quotas depend on the current Dify plan

Self-hosted Community Edition

Best for teams that need a custom domain, private deployment, data control, and deeper system integration.

The open-source repository is maintained by langgenius/dify
Supports self-hosting with Docker Compose
You are responsible for upgrades, backups, and security
A dedicated server is recommended for production
Architecture

How does a typical Dify AI application work?

01User InputFrom a Web App, API, form, or chat window.
02Knowledge RetrievalRetrieve relevant company documents and knowledge-base chunks based on the question.
03OmniDino ModelCall the selected LLM for understanding, generation, and reasoning.
04Tools and ConditionsCall HTTP services, search, code, databases, or business APIs.
05Answer OutputReturn the result to a webpage, API client, or the next workflow node.
Setup Requirements

Prepare Dify and an OmniDino API Key first.

Official Dify Open-Source Project

Includes the Web app, API, Worker, Plugin Daemon, database, and self-hosting deployment files.

Open SourceDocker ComposeWorkflowRAG

OmniDino API Key

Create a dedicated API Key for Dify and configure quotas, groups, and model permissions for your use case.

Dedicated KeyQuota LimitsUsage TrackingDisable Anytime
Add a Model Provider

Install the OpenAI Provider in Dify and connect it to OmniDino.

Dify now uses plugin-based model providers. Menu names may vary slightly between Dify and plugin versions.

01

Open Model Providers

Open Dify Workspace settings, then go to the model service page under Model Providers, Models, or Integrations.

02

Install the OpenAI Provider Plugin

Install the official OpenAI Model Provider from the Marketplace or provider list. If it is already installed, open its configuration directly.

03

Select a Custom API Endpoint

Open the configuration option for a custom address, OpenAI-compatible Endpoint, or Base URL.

04

Enter OmniDino Settings

Use your OmniDino API Key, set the Base URL to https://api.omnidino.com/v1, and enter the exact model ID.

05

Save and Verify Credentials

Dify will test the provider credentials. After verification succeeds, add the LLM, Embedding, or Rerank models separately.

OmniDino Configuration

Recommended values for an OpenAI-compatible provider.

Core Fields

Depending on the Dify plugin version, this field may appear as API Base, Base URL, Endpoint, or API Endpoint.

ProviderOpenAI
API KeyYour OmniDino API Key
API Base / Endpointhttps://api.omnidino.com/v1
Model NameExact OmniDino Model ID
Model TypeLLM / Text Embedding / Rerank
Do not enter the full /chat/completions path. The Dify provider appends the appropriate endpoint based on the model type.
Dify Provider Configuration Summary
Provider: OpenAI
API Key: YOUR_OMNIDINO_API_KEY
API Base: https://api.omnidino.com/v1

LLM Model:
Enter the exact OmniDino chat model ID

Embedding Model:
Enter the exact OmniDino Embedding model ID

Rerank Model:
Enter the exact OmniDino Rerank model ID
Not every OpenAI Provider plugin version supports the same custom fields. If your current plugin does not allow a custom Base URL, check that version’s documentation or use a provider plugin that supports an OpenAI-compatible Endpoint.
Model Types

Distinguish at least three model types in Dify.

LLM

Language Model

Used for chat, summarization, writing, Workflows, Chatflows, and Agents. Final knowledge-base answers are also typically generated by an LLM.

EMB

Text Embedding

Converts document chunks and user questions into vectors. Without Embedding, a semantic knowledge base cannot index or retrieve content correctly.

RR

Rerank

Reorders initial retrieval results to prioritize the content most relevant to the user’s question. It is optional, but often valuable.

The corresponding model types and endpoints must actually exist in OmniDino. A chat model cannot substitute for an Embedding model, and an Embedding model cannot be used for normal conversation.
Create Your First Chatflow

Build a minimal chat application with an OmniDino model.

01StartReceive user input and system variables.
02LLMSelect the OmniDino provider and model.
03PromptDefine the role, task, and output format.
04AnswerSend the model output to the user.
05PublishPublish a Web App or API.
01

Create a Blank Chatflow

In Studio, click Create App, choose Chatflow, and start from a blank canvas.

02

Add an LLM Node

Choose the OmniDino provider and a configured text model in the model selector.

03

Bind User Input

Pass the user question from the Start node into the LLM Prompt, then connect it to the Answer node.

04

Run a Minimal Test

Enter a simple question, confirm that Dify returns a result, and verify the request in the OmniDino console.

05

Publish Applications

After confirming that all nodes run without errors, publish the app as a Dify Web App or externally callable application API.

Knowledge-Base Support

Turn company files into searchable answer sources.

DOCUpload DocumentsPDFs, Word files, FAQs, webpages, or structured data.
CHUNKDocument ChunkingSplit content by length, headings, or structure.
EMBEmbeddingConvert chunks into vectors and build an index.
RAGKnowledge RetrievalFind relevant chunks based on the user’s question.
LLMGenerate an AnswerThe OmniDino LLM answers using the retrieved content.
If the knowledge base cannot create an index, first check whether a default Text Embedding model is configured in the Workspace. Changing the Embedding model usually triggers re-vectorization.
Agents and Tools

Let the model decide when to call external capabilities.

An Agent is not just a longer conversation. It lets the model call tools autonomously.

In an Agent node, the model can iteratively decide which tools to use and in what order. Common tools include HTTP requests, search, code execution, databases, custom APIs, and knowledge bases.

Function CallingThe selected OmniDino model must support tool calling, or the Agent may not run reliably.
Maximum IterationsKeep this value reasonable to avoid workflow loops, timeouts, and unnecessary token usage.
Tool PermissionsEnable only the tools required for the current task, and handle writes, deletions, and external requests carefully.
Two API Keys

An OmniDino Key and a Dify App Key serve different purposes.

OmniDino API Key

Stored by the Dify Model Provider and used by Dify to call OmniDino LLM, Embedding, Rerank, or other model services.

Created in the OmniDino console
Controls model access, groups, and balance
Must not be exposed to end users

Dify App API Key

Generated after a Dify application is published and used by external websites, programs, or servers to call the orchestrated Dify app.

Created under API Access in the Dify app
Calls the published Dify App
Cannot directly access the OmniDino model gateway
Recommended Use Cases

These scenarios are ideal for Dify + OmniDino.

CS

Enterprise Knowledge-Base Support

Answer customer questions from product materials, FAQs, and support documents while citing knowledge sources.

DOC

PDF Analysis Assistant

Upload contracts, reports, or manuals to extract key points, risks, and structured information automatically.

MAIL

Email Classification and Replies

Detect intent, assign priority, generate drafts, and connect to internal systems.

CONTENT

Content Generation Pipeline

Move from keywords to outlines, full drafts, review, translation, and multi-platform output.

REVIEW

Multi-Model Review Workflow

Use different models to generate, critique, and verify content for higher quality on complex tasks.

API

Internal Business Assistant

Connect CRM, ERP, inventory, quotation, or ticketing systems for queries and automation.

Troubleshooting

When a connection fails, troubleshoot the model, provider, and nodes layer by layer.

Confirm that the Base URL is https://api.omnidino.com/v1, the key is valid and has available balance, and the current OpenAI Provider plugin supports a custom Endpoint.
The model name entered in Dify must exactly match the real model ID in the OmniDino console. Do not use a display name, translated name, or omit version suffixes.
Check whether a Text Embedding model is configured and whether it has a working endpoint, available balance, and the correct dimensions. A chat model cannot replace an Embedding model.
Check chunking rules, the Embedding model, Top K, Score Threshold, and Rerank settings. Chunks that are too long or too fragmented can both reduce quality.
Confirm that the current OmniDino model supports Function Calling, then check the tool parameter schema, permissions, authentication, and maximum iterations.
Reduce the Agent’s maximum iterations, add explicit stopping conditions, remove irrelevant tools, and limit context and output length at each node.
Check whether the LLM node is using the OmniDino provider. Requests will not pass through OmniDino if another default Dify provider is selected.
Dify may display plugin-defined or manually configured local pricing. Actual charges are determined by the model price, multiplier, and request logs in the OmniDino console.
No. A Dify App Key calls a published Dify application, while an OmniDino Key is used by the Dify provider to call the underlying models.

Turn OmniDino from a model gateway into the engine behind your AI applications.

Start with a minimal Chatflow containing only Start, LLM, and Answer. Once the connection is stable, add a knowledge base, tools, and Agent nodes.

Continue Reading

After configuring third-party clients, continue to account and billing setup.