Evidence boundary: Dify documents provider plugins and model credentials. The documentation verifies supported integration surfaces, not the provider behind any unrelated hosted application.
Documented integration pattern
- Install or select the documented provider integration.
- Configure credentials through the platform's secret controls.
- Map the exact model and capability.
- Test limits, structured output, tools, and cost with a representative workflow.
Relevant provider records
- OpenAI API · official channel
- Anthropic API · official channel
First-party evidence
- Dify model provider documentationFirst-party model configuration guide.
What this page does not claim
It does not claim that the project's hosted service uses these providers in production, that the integration handles every feature, or that any private cost or revenue figure is known.
Questions developers ask
Does this page prove Dify's private production stack?
No. It documents only the linked public repository or first-party documentation evidence and makes no private deployment claim.
Does APIDir know this project's provider spend or revenue?
No. APIDir does not infer private usage, cost, customer, or revenue information from a public integration.
How should I reuse this integration pattern?
Open the cited source, confirm its current license and configuration, then test the relevant provider record against your own workload.