Dify
Register RouteMux as a model provider in Dify workflows and agents.
Dify supports OpenAI-API-compatible providers, so RouteMux plugs in without a custom connector.
Configure
| Field | Value |
|---|---|
| Model provider | OpenAI-API-compatible |
| API endpoint URL | https://api.routemux.com/v1 |
| API Key | your RouteMux key (sk-...) |
| Model name | a slug from GET /v1/models |
| Model type | LLM |
Register one model entry per slug you intend to use — Dify binds workflow nodes to specific model names.
Function calling and vision
Declare these per model entry to match what the underlying model actually supports. Dify will offer the capability in the node editor once declared, and the upstream will reject the request if the model cannot do it — so an over-declared capability fails at run time, not at configuration time.
Multi-tenant cost control
Dify workspaces share whichever key you register. If you need per-team accounting, create separate RouteMux keys and register them in separate Dify workspaces — per-key spend is visible in the console.
Errors surfaced in Dify
| RouteMux status | What Dify shows |
|---|---|
402 | Provider error — wallet empty. Top up and re-run the node. |
429 | Rate limited. Dify's retry policy applies. |
400 AMBIGUOUS_API_KEY | Two different keys configured. Clear the unused field. |