Dify
Dify is an open-source platform for building AI applications, combining Backend-as-a-Service and LLMOps to streamline the development of generative AI solutions for developers and non-technical innovators alike. Teams build agentic workflows, chatflows, agents and RAG knowledge pipelines on a visual canvas, then publish each one as a web app, an embeddable widget, a REST API or an MCP server. Dify is operated by Langgenius, Inc. and ships as Dify Cloud, a self-hosted Community Edition and a commercial Enterprise edition.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Dify the way a machine reads it — 37 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Dify scores 64.0/100 (strong), with a separate agent-readiness read of 42/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Dify's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/dify/"
title="Dify on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/dify.svg"
alt="Dify Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/dify/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/dify/"
title="Dify on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/dify/card.svg"
alt="Dify Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Dify
Each block below is one kind of artifact we hold for Dify. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 19
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Dify
Dify is an open-source platform for building AI applications, combining Backend-as-a-Service and LLMOps. Every app published in Dify doubles as a REST API, and so does every kno...
Dify Chat Messages API
Operations related to chat messages and interactions. 3 operation(s) from the Dify Service API.
Dify Completion Messages API
Operations related to text generation and completion. 2 operation(s) from the Dify Service API.
Dify Conversations API
Operations related to managing conversations. 6 operation(s) from the Dify Service API.
Dify Knowledge Bases API
Operations for managing knowledge bases, including creation, configuration, and retrieval. 6 operation(s) from the Dify Service API.
Dify Files API
File upload and preview operations. 2 operation(s) from the Dify Service API.
Dify Workflow Runs API
Operations for executing and managing workflows. 6 operation(s) from the Dify Service API.
Dify Applications API
Operations to retrieve application settings and information. 4 operation(s) from the Dify Service API.
Dify Annotations API
Operations related to managing annotations for direct replies. 6 operation(s) from the Dify Service API.
Dify Audio API
Text-to-Speech and Speech-to-Text operations. 2 operation(s) from the Dify Service API.
Dify Feedback API
User feedback operations. 2 operation(s) from the Dify Service API.
Dify End Users API
Operations related to end user information. 1 operation(s) from the Dify Service API.
Dify Human Input API
Endpoints for resuming paused workflows that require human input. 2 operation(s) from the Dify Service API.
Dify Documents API
Operations for creating, updating, and managing documents within a knowledge base. 12 operation(s) from the Dify Service API.
Dify Chunks API
Operations for managing document chunks and child chunks. 9 operation(s) from the Dify Service API.
Dify Knowledge Tags API
Operations for managing knowledge base tags and tag bindings. 7 operation(s) from the Dify Service API.
Dify Metadata API
Operations for managing knowledge base metadata fields and document metadata values. 7 operation(s) from the Dify Service API.
Dify Models API
Operations for retrieving available models. 1 operation(s) from the Dify Service API.
Dify Knowledge Pipeline API
Operations for managing and running knowledge pipelines, including datasource plugins and pipeline execution. 4 operation(s) from the Dify Service API.
Scroll within the panel for all 19 ·
Open Collections 8
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONDify Chat API
OPEN COLLECTIONDify Chat Completion API
OPEN COLLECTIONDify Chat Conversations API
OPEN COLLECTIONDify Chat Datasets API
OPEN COLLECTIONDify Chat Files API
OPEN COLLECTIONDify Chat Workflows API
OPEN COLLECTIONDify API
OPEN COLLECTIONScroll within the panel for all 8 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Dify Docs MCP
Dify's MCP posture has two distinct surfaces. (1) A live, anonymous, remote documentation MCP server at https://docs.dify.ai/mcp, confirmed by an unauthenticated tools/list call...
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Dify Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Dify Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Dify Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Dify Events
ASYNCAPISecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Dify — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 5
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 6
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 6
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/dify · machine-readable index on apis.io
This is an independent, third-party profile of Dify, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.