Give every Dify app one model provider
Dify is one of the most widely used platforms for building LLM apps and agent workflows. Each app you ship needs a model provider behind it — and juggling one vendor account per family means separate keys, bills, and failure modes. Registering Router One once as an OpenAI-API-compatible provider puts the whole catalog behind a single credential, with every app call traced for cost.
Configure Dify to use the Router One base URL
In Dify, open Settings → Model Provider → add an OpenAI-API-compatible model, then fill in the model ID, base URL, and key:
# Dify → Settings → Model Provider → OpenAI-API-compatible Model Name: <model-id-from-/models> API endpoint: https://api.router.one/v1 API Key: sk-your-router-one-key
Which model ID should Dify send?
Copy the exact model ID from /models, preserving case, hyphens, and version suffixes; do not substitute a display name. Open its detail page and match the supported API endpoints, context window, and capabilities such as tool calling to the provider and features selected in Dify. A catalog listing does not mean the client can use every feature of that model. Give each tool a dedicated API key with a maxSpend cap.
Which API protocol is Dify using?
OpenAI-compatible describes an interface format; it does not make Chat Completions (/v1/chat/completions), Responses (/v1/responses), and Anthropic Messages (/v1/messages) interchangeable. Check the installed client version, provider configuration, and actual request path against the model detail page and API compatibility fact sheet. A successful plain-text chat does not establish support for hosted tools, conversation state, or file-editing features.
Verify the Dify call in your request trace
Send a simple text request from Dify, then match its trace in Dashboard → Logs by time, model, and request_id: tokens, cost, latency, and status. Next, test streaming, tool calls, and multi-turn history separately. For failures, retain the actual request path, full error message, and request_id. If there is no matching log, check client configuration and connectivity before attributing the error to the gateway or upstream.
FAQ
Which provider type do I pick in Dify?
Choose "OpenAI-API-compatible" in the model-provider list. Add one entry per model you want to expose, using the exact model ID from /models — each becomes selectable in your Dify apps.
Which models can Dify use through the gateway?
Choose a current catalog model that supports both the endpoint and the features Dify uses. Check /models and the model detail page for the exact ID, current rates, and capabilities; a family name such as GPT or Claude is not a compatibility guarantee. Seeing a model in the picker confirms discovery, so verify an actual request too.
Models are listed, but requests fail with 400 or 404. What should I check?
Record the actual request path and error message, then check the exact model ID. A 400 can indicate invalid parameters, unsupported tools, or a model/endpoint mismatch; a 404 can indicate an incorrect path or missing resource, so it does not by itself establish that a model was retired. If the error says must be called via, use the named endpoint or select a model supported on the current endpoint. Do not add or remove /v1 or /chat/completions across all clients indiscriminately.
Does this work from Mainland China?
Yes. The gateway is reachable from Mainland China without a VPN, and the configuration is identical to the global setup.
How do I debug a 401/402/403/429?
Match the request and error message in Dashboard → Logs. For 401, check whether the key was sent and is valid; for 402, check wallet balance and maxSpend; for 403, check key permissions and access restrictions. For 429, distinguish request/token limits from upstream throttling using the error details. Keep the request_id and follow the error-codes reference.