Skip to main content
This page lists supported providers, authentication pairings, and filter-window bounds. Refer to Models concept for how connections work. Configure on Models.

​
Providers

Provider IDs fall into three groups. You cannot change the provider after adding the model.
  • Native providers. Dome translates between the Gateway request and the provider’s native wire format. openai, anthropic, google, azure_openai, and bedrock.
  • Hosted OpenAI-compatible providers. Dome sends requests through the provider’s OpenAI-compatible API. mistral, groq, together, fireworks, deepseek, xai, perplexity, cohere, openrouter, cerebras, nvidia, deepinfra, sambanova, ai21, and databricks.
  • Bring your own endpoint. Use openai_compatible for an OpenAI-shaped endpoint such as vLLM or Ollama. Use custom when Dome should forward provider-specific requests without translating them.
Dome supplies a base URL for hosted providers that have a default. For Google, Azure OpenAI, Bedrock, Databricks, openai_compatible, and custom, you must provide an endpoint or the provider-specific details needed to locate the model. These details can include an Azure deployment, a Google project and location, or a Bedrock region. Hosted OpenAI-compatible providers share the OpenAI chat and embeddings wire shape. Native and bring-your-own adapters differ:

​
Provider capabilities

An unsupported Gateway operation for the resolved provider returns HTTP 501 with a structured error.

​
Custom passthrough

POST /gateways/<id>/v1/passthrough/:name forwards the request body byte-exact to a custom-provider connection. Identity, tenant match, and Cedar (llm:passthrough) still apply. The canonical content filter is bypassed (no canonical shape to filter against). Configure header_passthrough_allow (and related custom keys such as endpoint and request_shape_doc_url) on the model connection. See Create LLM model connection.

​
Credentials

When the provider requires no authentication, set both to none. When the provider uses an API key or OAuth, the credential type must be shared or per-user. If you omit both settings, Dome uses api-key with shared. Per-user provisioning and workload identity are on Models.

​
Filter window

A model can buffer at most 1 MiB or 4,096 tokens of streamed output before outbound Guards run. Dome uses the largest window configured on the workspace, model, or request. A value of 0 uses the workspace setting. Layer sources and effective-max rules are on the Guards reference.

​
Next steps

Add connections, or jump to pools when you need routing:
  • Models concept for connections, attributes, and direct vs pool
  • Models to add models, rotate credentials, and attach Gateways
  • Pools reference for routing across connections
  • LLM gateway concept for the model ingress