Evidence boundary: Flowise documents chat-model nodes and credentials. This confirms a supported integration interface, not a claim about any hosted Flowise deployment.
Documented integration pattern
- Add the documented chat-model component.
- Reference credentials from the platform secret store.
- Set model and generation controls explicitly.
- Run a representative flow and record tokens, retries, and tool calls.
Relevant provider records
- OpenAI API · official channel
First-party evidence
- Flowise chat models documentationFirst-party component documentation.
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 Flowise'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.