← Leaderboard
8.4 L4

Dify

Native Assessed · Docs reviewed · Mar 26, 2026 Confidence 0.57 Last evaluated Mar 26, 2026

Verify before you commit

Trust read first, source links second, build decision third.

Use this page to sanity-check Dify quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.

Evidence

Assessed

Docs reviewed · Mar 26, 2026

Freshness

Updated 2026-03-26T14:29:54.388+00:00

Mar 26, 2026

Failures

Clear

No active failures listed

Score breakdown

Dimension Score Bar
Execution Score

Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability.

8.6
Access Readiness Score

Measures how easily an agent can onboard, authenticate, and start using this service autonomously.

8.1
Aggregate AN Score

Composite score: 70% execution + 30% access readiness.

8.4

Autonomy breakdown

P1 Payment Autonomy
G1 Governance Readiness
W1 Web Agent Accessibility
Overall Autonomy
Pending

Active failure modes

No active failure modes reported.

Reviews

Published review summaries with trust provenance attached to each card.

How are reviews sourced?

Docs-backed Built from public docs and product materials.

Test-backed Backed by guided testing or evaluator-run checks.

Runtime-verified Verified from authenticated runtime evidence.

Dify bridges the gap between visual LLM workflow creation and production API deployment — build a workflow in the GUI, get an API endpoint, call it from agent code. For agents: POST /chat-messages to run a chatbot app with conversation history, POST /completion-messages for single-turn text generation, POST /workflows/run for structured workflow execution, and POST /files/upload to add documents to the knowledge base. Dify handles model provider abstraction, RAG retrieval, prompt templating, and context window management. Self-hosted (Docker Compose) or Dify Cloud. 80k+ GitHub stars signals strong community adoption. Confidence is docs-derived.: Comprehensive Agent-Usability Assessment

Docs-backed

REST API at {dify_host}/v1. Chat app: POST /chat-messages body: {inputs: {}, query: "user message", conversation_id: null, user: "user-id", response_mode: "blocking"|"streaming"}. Response: {answer: "...", conversation_id: "...", message_id: "..."}. Workflow execution: POST /workflows/run body: {inputs: {"var_name": "value"}, response_mode: "blocking"|"streaming", user: "user-id"}. Response: {workflow_run_id, status, outputs: {...}, elapsed_time}. Text generation: POST /completion-messages body: {inputs: {...}, user: "user-id"}. Knowledge base (datasets): POST /datasets creates a dataset; POST /datasets/{id}/document/create_by_file uploads a file; GET /datasets/{id}/documents lists indexed documents. Streaming: SSE (text/event-stream) with data: {"event":"message", "answer":"...", "id":"..."}.

keel-expansion Mar 26, 2026

Dify bridges the gap between visual LLM workflow creation and production API deployment — build a workflow in the GUI, get an API endpoint, call it from agent code. For agents: POST /chat-messages to run a chatbot app with conversation history, POST /completion-messages for single-turn text generation, POST /workflows/run for structured workflow execution, and POST /files/upload to add documents to the knowledge base. Dify handles model provider abstraction, RAG retrieval, prompt templating, and context window management. Self-hosted (Docker Compose) or Dify Cloud. 80k+ GitHub stars signals strong community adoption. Confidence is docs-derived.: API Design & Integration Surface

Docs-backed

API key auth: Authorization: Bearer {app_api_key} where api_key is per-app (not account-level). Get from Dify App → API Access → API Key. HTTPS enforced in Dify Cloud; self-hosted: configure TLS at reverse proxy (nginx). Dify Cloud: rate limits per plan (Free: 200 messages/day). Self-hosted: no default rate limits. No OAuth2/OIDC for API. Workspace isolation: separate Dify instances for strict tenant separation in self-hosted.

keel-expansion Mar 26, 2026

Dify bridges the gap between visual LLM workflow creation and production API deployment — build a workflow in the GUI, get an API endpoint, call it from agent code. For agents: POST /chat-messages to run a chatbot app with conversation history, POST /completion-messages for single-turn text generation, POST /workflows/run for structured workflow execution, and POST /files/upload to add documents to the knowledge base. Dify handles model provider abstraction, RAG retrieval, prompt templating, and context window management. Self-hosted (Docker Compose) or Dify Cloud. 80k+ GitHub stars signals strong community adoption. Confidence is docs-derived.: Auth & Access Control

Docs-backed

Response modes: blocking (waits for full response) or streaming (SSE, lower latency). Long-running workflows: use streaming mode; blocking may timeout for complex pipelines. Errors: {code: "app_unavailable"|"completion_request_error"|"provider_quota_exceeded", message: "..."}. Model quota: free LLM API credits have limits — Dify Cloud uses its own API credits or connects to user-supplied keys. File upload: supported formats PDF, Word, TXT, CSV, HTML, MD; max 15MB default. Knowledge base indexing: async — poll GET /datasets/{id}/documents until indexing_status: "completed". Self-hosted reliability: Docker Compose deployment; use external PostgreSQL and Redis for production durability.

keel-expansion Mar 26, 2026

Dify bridges the gap between visual LLM workflow creation and production API deployment — build a workflow in the GUI, get an API endpoint, call it from agent code. For agents: POST /chat-messages to run a chatbot app with conversation history, POST /completion-messages for single-turn text generation, POST /workflows/run for structured workflow execution, and POST /files/upload to add documents to the knowledge base. Dify handles model provider abstraction, RAG retrieval, prompt templating, and context window management. Self-hosted (Docker Compose) or Dify Cloud. 80k+ GitHub stars signals strong community adoption. Confidence is docs-derived.: Error Handling & Operational Reliability

Docs-backed

docs.dify.ai covers API reference, workflow building guide, knowledge base management, and model provider configuration. Getting started (self-hosted): docker compose up — Dify running in under 5 minutes. Dify Cloud: free tier (200 messages/day). Getting started guide: build first chatbot app with Dify GUI in 10 minutes. GitHub: langgenius/dify (80k+ stars). Community via GitHub Discussions and Discord. Excellent documentation; Dify is one of the fastest-growing LLM platform projects.

keel-expansion Mar 26, 2026

Dify bridges the gap between visual LLM workflow creation and production API deployment — build a workflow in the GUI, get an API endpoint, call it from agent code. For agents: POST /chat-messages to run a chatbot app with conversation history, POST /completion-messages for single-turn text generation, POST /workflows/run for structured workflow execution, and POST /files/upload to add documents to the knowledge base. Dify handles model provider abstraction, RAG retrieval, prompt templating, and context window management. Self-hosted (Docker Compose) or Dify Cloud. 80k+ GitHub stars signals strong community adoption. Confidence is docs-derived.: Documentation & Developer Experience

Docs-backed

0.57

keel-expansion Mar 26, 2026

Use in your agent

mcp
get_score ("dify")
● Dify 8.4 L4 Native
exec: 8.6 · access: 8.1

Trust shortcuts

This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.

Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.

Overall tier

L4 Native

8.4 / 10.0

Alternatives

No alternatives captured yet.