Overview
The Omnifact provider connects to the Omnifact API Gateway — an OpenAI-compatible endpoint for chat completions. Use your Omnifact organization API key and any model enabled for your organization.Installation
createOmnifact()
Create an Omnifact provider instance.Options
string
Your Omnifact organization API key.
string
Custom gateway base URL. Defaults to
https://connect.omnifact.ai/v1/gateway.Returns
OmnifactProvider with method chatModel().
Model IDs
Use the exactid values returned by GET /v1/gateway/models. The SDK passes the model id through unchanged.
EU-hosted backends (Azure OpenAI, Vertex Google, Vertex Anthropic, Mistral, etc.) always use the eu/ prefix:
eu/gpt-5-mini— Azure OpenAIeu/claude-4-6-sonnet— Vertex Anthropiceu/mistral-large— Mistral
gpt-5-mini— OpenAIclaude-4-6-sonnet— Anthropic
Provider support
Model capabilities
Every chat model exposesmodel.capabilities:
eu/gpt-5-mini and IDs for other backend providers do not match that
registry, so they receive generic OpenAI-compatible fallback capabilities.
For those IDs, treat model.capabilities as defaults rather than an exact
description of the backend model. In particular, the fallback reports
'image' and 'file' in modalities.input, so multimodal requests are
forwarded to the backend rather than rejected locally.
Examples
Basic chat
Streaming
Provider-specific options
The gateway follows the OpenAI Chat Completions API. Pass options viaproviderOptions.openai:
reasoning_content and reasoning output
fields. See the OpenAI-compatible provider for
the compatibility behavior and available Chat Completions options.