H3 Official Context-IR:
The H3 Official Context-IR node connects your H3 context workflow to the official MiniMax remote Context-IR service through a separately configured provider connection. It prepares and validates your context information before passing it to the official provider, allowing you to obtain an official prompt result for use or comparison in your workflow. This is a connection to the official implementation, not a local recreation of it, and it does not queue native H3 image or video generation. Its main benefits are access to the official context-processing path, consistent request preparation, and explicit controls over remote processing and credential access. It requires an internet connection, runtime credentials, and host-side transport configuration; installing the node alone does not establish that connection. The provider does not advertise deterministic execution or seed support, so identical requests should not be assumed to produce identical results.
H3 Official Context-IR Input Parameters:
request
Required input of type H3_CONTEXT_REQUEST containing a typed RawContextRequest rather than plain text. This is the context information the node prepares for the official provider. Before sending it, the node reconciles its reference registry, normalizes the request into a validated form, and maps it to the official Context-IR request format. If this preparation fails, execution stops rather than sending an invalid request. Connect a compatible H3 request-producing node; a text string or unrelated socket value is not a substitute. No default value, numeric minimum, or numeric maximum is specified.
ratio
Required COMBO selection that controls the aspect-ratio setting used when mapping the request to the official Context-IR contract. Its default is the value of OfficialAspectRatio.ADAPTIVE, the adaptive selection. The available options are generated from the values defined in OfficialAspectRatio; the supplied source does not show that enumeration’s complete list or literal strings, so use the options displayed in your installed node rather than entering an assumed ratio. This controls the official request’s ratio setting, not a local image-resizing operation. Numeric minimum and maximum values do not apply.
upload_consent
Required BOOLEAN control with options True and False and a default of False. This explicitly confirms whether media may leave the machine running your workflow for remote processing. Because the official provider uses a remote execution policy, this permission is checked before provider execution; leaving it disabled prevents an otherwise valid remote request from proceeding. Enable it only after reviewing the material you intend to submit and confirming that you are comfortable sending it outside your host. This permission is separate from network access, so enabling it does not replace the need to enable network_allowed.
network_allowed
Required BOOLEAN control with options True and False and a default of False. This explicitly allows the selected official provider’s network connection. Internally, disabling it also marks the execution policy as offline, which conflicts with this provider’s requirement for internet access. Enable it when you intend to use the configured remote service, and keep it disabled when you do not want the workflow to contact that service. It does not configure the provider connection, grant upload consent, or supply credentials by itself.
credential_reference
Required single-line STRING with a default of env.official_minimax. This is an opaque reference that the runtime uses to locate credentials; it must not contain the credential value or API key itself. Your host’s credential resolver must recognize the reference and supply the corresponding credential during execution. The default is a reference name, not proof that a credential has already been configured. Dynamic prompt substitution is disabled for this field. No length limit or complete list of accepted references is specified in the supplied source; use a reference supported by your host configuration.
reference_registry
Optional input of type H3_REFERENCE_REGISTRY containing a canonical ReferenceRegistry that identifies the request’s reference assets consistently. When connected, the node uses it during request normalization before mapping media to the official format. If the request already has a registry containing assets, the connected registry must match it; conflicting registries cause execution to stop rather than risk using inconsistent references. If this input is omitted, the registry already attached to the request is retained. No separate default registry value, numeric range, or selectable options are declared.
media
Optional input of type H3_CONTEXT_IR_MEDIA containing already-admitted OfficialContextIRMedia values in canonical order. The node accepts a single typed media value or a list or tuple of those values and passes them into official request mapping. Ordinary file paths, image tensors, or untyped dictionaries are not accepted by this input merely because they represent media. Prepare compatible media upstream and preserve the required reference order. When omitted, the node supplies an empty media tuple to the request builder; whether the resulting request is valid depends on its content and the official mapping rules. No media-count limits or size ranges are shown in the supplied node interface.
H3 Official Context-IR Output Parameters:
prompt
Output of type H3_PROMPT_STRING containing the prompt returned through the official Context-IR provider execution. This is the prompt result of the remote context-processing step, not a generated image or video. You can connect it to compatible downstream prompt-processing or generation stages that accept this socket type. The provider output contract requires a prompt field, but the supplied source does not specify its wording, formatting, or length.
receipt
Output of type H3_PROVIDER_RECEIPT containing a structured ProviderReceipt associated with provider execution. It provides a record that compatible reporting or inspection tools can use to track the provider result alongside your workflow. Treat it as structured execution information rather than prompt text or generated artwork. The official output contract requires a receipt, but its individual fields are not included in the supplied source, so do not assume it contains particular billing, timing, or request-identification fields.
consent_notice
Output of type H3_PROVIDER_CONSENT containing a structured ProviderConsentNotice built from the official provider’s descriptor and your execution policy. It describes the consent-related context for using this remote provider, helping you keep the execution disclosure alongside the result. It is not an interactive permission dialog and does not replace explicitly enabling the required permissions before execution. Its complete field structure is not shown in the supplied source.
H3 Official Context-IR Usage Tips:
- Configure the official Context-IR transport on the host before queueing the workflow. This node depends on that external setup; enabling its permission switches cannot resolve an unconfigured connection.
- For an intended remote run, enable both
upload_consentandnetwork_allowed. Their defaults are deliberately restrictive, and either disabled permission can prevent execution. - Keep your actual API key out of
credential_reference. Useenv.official_minimaxonly if your host resolves that reference, or enter the reference provided by your host administrator. - Start with the adaptive
ratioselection unless your task requires another supported aspect ratio. Choose alternatives from the installed node’s dropdown; the supplied source does not establish which fixed ratios are available. - Keep the request’s reference registry and any separately connected
reference_registrysynchronized. If you do not need to supply a replacement registry, omit the optional connection and let the node use the request’s own registry. - Prepare
mediausing a compatible upstream process that produces admittedOfficialContextIRMediavalues. Preserve canonical ordering instead of manually rearranging references. - Connect the node’s results to an appropriate downstream stage or consumer. The node is not marked as an output node and does not itself launch native H3 generation.
- When comparing official results with another context-processing path, retain the receipt and consent notice alongside the prompt. Do not treat differences between repeated runs as proof of a workflow fault: this provider does not advertise deterministic or seeded execution.
H3 Official Context-IR Common Errors and Solutions:
transport_unconfigured — official provider transport is not configured
- Explanation: The node has no configured transport for communicating with the official provider. This can also be detected during preflight validation before execution.
- Solution: Configure the official Context-IR host integration before queueing again. If you do not manage the host, ask its administrator to configure the provider connection. Permission switches and a credential reference alone are not enough.
invalid_request — request must be a RawContextRequest
- Explanation: The connected request is not the typed request object required by the node.
- Solution: Connect a compatible
H3_CONTEXT_REQUESToutput from an H3 request-building stage. Do not substitute a plain prompt string or an unrelated object.
invalid_request — request normalization failed closed
- Explanation: The node could not turn the supplied request into a valid normalized request and stopped without proceeding to provider execution.
- Solution: Review the upstream request and its reference information. Correct incomplete or inconsistent request data, then rebuild the request using compatible H3 nodes. If available, inspect upstream validation reports for more specific details.
invalid_reference_registry — reference_registry must be a ReferenceRegistry
- Explanation: The optional registry connection does not contain the required typed registry object.
- Solution: Connect a compatible
H3_REFERENCE_REGISTRYoutput, or remove the optional connection if the request already carries the registry you intend to use.
reference_registry_mismatch — request and connected registries disagree
- Explanation: The request already contains a registry with assets, and the separately connected registry does not match it.
- Solution: Build the request and media from the same canonical registry. Alternatively, disconnect the separate registry if the request’s embedded registry is correct.
invalid_media — media must contain typed official values
- Explanation: The supplied media is neither a single
OfficialContextIRMediavalue nor a list or tuple of those values. - Solution: Use a compatible upstream media-preparation stage. Do not connect raw paths, arbitrary collections, or ordinary media objects that have not been converted to the official typed format.
invalid_media — media contains an invalid typed value
- Explanation: The media list or tuple contains at least one item that is not an
OfficialContextIRMediavalue. - Solution: Check every item in the collection and replace incompatible entries. All items must use the required official media type.
policy — provider controls must be booleans
- Explanation:
upload_consentornetwork_allowedwas supplied as something other than a Boolean value, such as text. - Solution: Use the node’s Boolean controls or supply actual
TrueorFalsevalues through workflow automation.
policy — credential_reference must be a string
- Explanation: The credential reference was supplied with an incompatible data type.
- Solution: Supply a text reference recognized by your host, such as the default
env.official_minimaxwhen configured. Do not pass a credential object or the secret itself.
policy — official provider controls are invalid
- Explanation: The execution-policy constructor rejected the combination of provider controls or credential reference. The supplied source does not expose the underlying validation details.
- Solution: Confirm that both permission controls are valid Booleans and that the credential reference follows your host’s supported configuration. For remote execution, enable both permissions only after reviewing the privacy implications.
policy — provider-policy diagnostic
- Explanation: The prepared policy does not meet the official provider’s requirements. This branch reports a diagnostic code whose possible strings are not shown in the supplied source; the provider requires internet access, explicit remote permissions, and credentials.
- Solution: Read the reported diagnostic, confirm that network access and upload consent are enabled for your intended remote run, and verify that your host can resolve the selected credential reference.
official request mapping failed
- Explanation: The normalized request could not be converted to the official Context-IR format. This message may appear with
invalid_requestor a more specific category from the request builder. - Solution: Select a ratio offered by the dropdown, check that the request and reference registry agree, and confirm that all connected media values are correctly typed and ordered. Use any accompanying error category to identify which part of the request needs correction.
