Save 4 hours! We auto-setup your workflow! Free!

Drop your workflow.json — we handle every dependency, custom node, and model. Just open the link and run.

Auto-Setup Workflow Json (Free) Now!
ComfyUI > Nodes > MiniMaxH3-Studio > H3 Provider Transparency

ComfyUI Node: H3 Provider Transparency

Class Name

comfyui_h3_context.H3Context.ProviderTransparency

Category
h3_context/providers
Author
rookiestar28 (Account age: 1077days)
Extension
MiniMaxH3-Studio
Latest Updated
2026-11-05
Github Stars
0.16K

How to Install MiniMaxH3-Studio

Install this extension via the ComfyUI Manager by searching for MiniMaxH3-Studio
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter MiniMaxH3-Studio in the search bar
After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • 16GB VRAM to 80GB VRAM GPU machines
  • 400+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 200+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

H3 Provider Transparency Description

Reviews provider privacy, permissions, costs, and execution policies without contacting services.

H3 Provider Transparency:

H3 Provider Transparency helps you review the privacy and execution implications of a provider configuration before using it in your workflow. It builds a policy-based description covering network access, media uploads, credential requirements, retention, potential costs, and fallback behavior, together with information about provider setup. This makes it easier to understand whether your intended workflow stays local or involves an external service, and whether your permissions are consistent with the selected provider. The node is strictly informational: it does not contact a provider, upload media, execute a route, or automatically switch to a fallback. Its checks describe policy compatibility rather than proving that a service is available or ready to run, so you can use it as a review step without initiating provider activity.

H3 Provider Transparency Input Parameters:

provider

Required COMBO input selecting the provider identity to describe. The default is manual, and the available options are generated from all values in ProviderIdentity; the supplied context confirms manual, local, and remote_custom, but does not include the complete enum definition. Select the appropriate identity explicitly, because the node does not infer a provider from other settings. This choice determines the provider profile used to describe network, credential, retention, and cost requirements, and it is evaluated alongside your privacy and permission settings. Selecting a provider does not connect to it. Minimum and maximum values do not apply to this dropdown.

privacy_mode

Required COMBO input expressing the privacy policy you intend to use. The default is local_only, and options are generated from all values in ProviderPrivacyMode; the supplied context confirms local_only and explicit_remote without showing the complete enum definition. This setting provides the privacy decision against which the selected provider and permissions are evaluated. For example, a local-only intention and a remote provider need to be reviewed for policy compatibility rather than treated as an automatic request to permit remote processing. Choosing a mode does not itself send data or execute a provider. Minimum and maximum values do not apply.

offline

Required BOOLEAN input with a default of True and possible values of True or False. It declares whether the selected route must remain offline. This affects policy evaluation and appears in the transparency information, helping you identify configurations that request an external provider while also requiring offline behavior. Setting it to False removes the offline requirement but does not, by itself, grant network permission or upload consent. The node remains non-executing regardless of this value.

network_allowed

Required BOOLEAN input with a default of False and possible values of True or False. It explicitly declares whether the selected provider's network path is permitted. The node compares this permission with the provider's requirements and the other policy controls, so a provider that requires network access may be reported as blocked when this is disabled. Setting it to True is not the same as consenting to remote media transfer, and it does not initiate a connection. Treat it as one separate permission within the overall privacy policy.

Required BOOLEAN input with a default of False and possible values of True or False. It records your explicit consent to remote media transfer for the policy being described. The transparency information reports both whether media upload is required and whether this consent has been supplied, allowing you to review those conditions separately. Enabling network access does not automatically enable this consent. Setting this value to True does not upload anything through this node; it changes the permission information used to evaluate the selected configuration.

credential_reference

Required STRING input whose interface default is "none". It accepts an opaque runtime credential reference: a reference used to identify credentials, rather than a field intended for entering a raw password or API key. Both an empty string and the exact string "none" are normalized to no credential reference. Other strings are passed into the policy as references, and the field's tooltip states that the reference is never returned in the disclosure. Whether credentials are required depends on the provider profile; providing a reference does not prove that credentials exist or will authenticate successfully. This is a single-line field with dynamic prompts disabled, and no minimum or maximum length is specified.

fallback_provider

Required COMBO input with a default of none. Available options are none followed by every value in ProviderIdentity; the supplied context does not provide the full enum definition. Select none when you do not want to declare a fallback, or select an explicit provider identity to include caller-selected fallback metadata in the policy. The node reports fallback policy and the declared fallback identity, but it never chooses, activates, or tests a fallback. This lets you make fallback intentions visible without silently changing where processing would occur. Minimum and maximum values do not apply.

local_backend

Optional COMBO input with a default of none. Its options are generated from all values in ProviderLocalBackend; the supplied context identifies none and ollama, and the tooltip also names comfyui_native as the preferred local backend. This setting affects the provider setup description, allowing local execution arrangements and process boundaries to be disclosed. Selecting none passes no explicit backend override to the setup builder; it should not be interpreted as proof that a backend has been selected or started. The tooltip describes Ollama as an explicit choice using a loopback process boundary, and the provided test confirms that selecting it can add media_transfer=ollama_process to the combined disclosure. No backend is launched by this node, and minimum and maximum values do not apply.

H3 Provider Transparency Output Parameters:

transparency

An H3_PROVIDER_TRANSPARENCY structured result describing the selected provider and the evaluated execution policy. It includes the provider identity and version, privacy mode, network requirement and permission, offline setting, media-upload requirement and consent, credential requirements, retention and cost policies, fallback information, diagnostics, and disclosure text. Its policy_valid and execution_allowed fields are both determined by whether policy diagnostics are present. Importantly, execution_allowed=True means that the policy evaluation found no blocking diagnostics; it does not mean a provider was called or that connectivity, authentication, or service readiness was tested. The result explicitly identifies its execution boundary as policy_only.

An H3_PROVIDER_CONSENT structured notice taken directly from the transparency result. It provides the consent-related information associated with the evaluated policy as a separate output, so you can keep consent information distinct from the broader provider description. It is generated from the configuration you supplied rather than from an interactive consent dialog, and receiving this output does not mean media has been uploaded or that a provider has executed. The supplied context does not show the notice's internal fields, so interpret it as a structured consent notice rather than assuming it is a plain-text message or a single approval flag.

disclosure

A STRING combining the transparency disclosure and the provider setup disclosure, separated by a space. This is the human-readable summary for reviewing provider/privacy implications together with setup information. Depending on the configuration, it can include policy status and local media-transfer details; the supplied tests confirm examples containing policy_valid=no for a blocked configuration and media_transfer=ollama_process for an explicit Ollama setup. Use it to inspect the configuration in an appropriate text-display node. It is a description of policy and setup, not a record of completed provider execution.

provider_setup

An H3_PROVIDER_SETUP structured result built from the same execution policy and the optional local backend selection. It complements the transparency result with provider setup information, including the local backend representation, policy validity, and its own disclosure. The supplied tests confirm that the default call produces a setup whose local backend is ProviderLocalBackend.NONE, and that a blocked remote configuration can produce policy_valid=False here as well as in the transparency result. This output describes setup rather than installing software, starting a backend, or verifying that a service is reachable.

H3 Provider Transparency Usage Tips:

  • Start with the defaults when you want to review a conservative configuration: provider=manual, privacy_mode=local_only, offline=True, network_allowed=False, upload_consent=False, credential_reference="none", and fallback_provider=none. These settings do not request remote access.
  • Connect disclosure to a compatible text-display node so you can read the combined privacy and setup summary. This node is not an output node, so include it in a workflow path that is actually evaluated when you want to inspect its results.
  • Before planning remote processing, review privacy_mode, offline, network_allowed, and upload_consent together. They are separate controls; enabling one does not automatically grant the others. Supply a runtime credential reference when the selected provider requires one.
  • Check policy_valid, execution_allowed, and the available diagnostics instead of assuming that successful node evaluation means the configuration is permitted. A blocked policy can still be returned as a valid descriptive result.
  • For a local Ollama setup review, the supplied test uses provider=local, privacy_mode=local_only, offline=False, network_allowed=True, upload_consent=False, and local_backend=ollama. Inspect the disclosed ollama_process boundary rather than assuming that every local backend operates entirely inside ComfyUI.
  • Keep fallback_provider=none unless you intentionally want to document an alternative provider. If you declare one, review its privacy implications separately; this node will not automatically switch to it.
  • Use a credential reference rather than a raw secret. Although the reference is excluded from the disclosure, that does not establish that arbitrary secrets entered into workflow fields are protected everywhere the workflow may be stored or shared.

H3 Provider Transparency Common Errors and Solutions:

provider must be an explicit provider identity

  • Explanation: The provider value is not a string. This can occur when a programmatic call or modified workflow supplies an object or another incompatible value instead of a provider identity.
  • Solution: Select a provider from the dropdown. If you call the node programmatically, pass a string matching a supported ProviderIdentity value.

privacy_mode must be an explicit privacy mode

  • Explanation: The privacy_mode value is not a string, so the node cannot interpret it as an explicit privacy decision.
  • Solution: Choose a supported privacy mode from the dropdown, such as the confirmed local_only or explicit_remote values, rather than supplying a Boolean or another object.
  • Explanation: At least one of these controls is not an actual Boolean. Text such as "False" and numeric values are not accepted as substitutes by this validation.
  • Solution: Use the Boolean controls in ComfyUI. In programmatic calls, supply actual True or False values for all three parameters.

credential_reference must be a string

  • Explanation: The credential reference was supplied as a non-string value, such as a credential object or a null value.
  • Solution: Supply a string containing your runtime credential reference. If no reference is needed, use "none" or an empty string rather than a non-string value.

fallback_provider must be an explicit identity or none

  • Explanation: The fallback_provider value is not a string. The node expects either the string "none" or a supported provider identity.
  • Solution: Choose none or an available provider from the dropdown. In programmatic calls, use the string "none" rather than a null value when you do not want a fallback.

local_backend must be an explicit backend identity

  • Explanation: The optional local_backend value was supplied as something other than a string.
  • Solution: Select a backend from the dropdown, use the string "none" to provide no explicit override, or omit the optional argument in a programmatic call.

provider transparency controls are invalid

  • Explanation: This is the node's general error message when enum conversion, contract validation, or security-policy construction raises an error. Unsupported provider, privacy, fallback, or backend strings can trigger it, and the visible message does not identify the precise underlying cause.
  • Solution: Restore supported dropdown values and verify that all settings are appropriate for the selected provider. Check any available underlying error details when troubleshooting programmatic calls or edited workflows. Do not assume every policy conflict raises this error; some are reported through output diagnostics instead.

policy_valid=no

  • Explanation: This is a disclosure status rather than necessarily an exception. It indicates that the described policy is blocked or inconsistent. The supplied test demonstrates this for remote_custom with privacy_mode=explicit_remote, offline=True, network_allowed=False, and upload_consent=False.
  • Solution: Review the transparency diagnostics and setup status. If you intend to remain offline, choose an appropriate non-remote configuration. If you intentionally need remote processing, review and explicitly grant the required permissions and credential reference as appropriate; do not enable remote access merely to remove the warning.

H3 Provider Transparency Related Nodes

Go back to the extension to check out more related nodes.
MiniMaxH3-Studio
RunComfy
Copyright 2025 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals. RunComfy also provides AI Models, enabling artists to harness the latest AI tools to create incredible art.

H3 Provider Transparency