Supported Providers

The Igris LLM Gateway supports 60 providers out of the box. Each is accessible through the same unified API — no code changes needed to switch between them. Add a provider by creating a connection in the dashboard and selecting from the list below. The slug column is what you use in the connection type selector and in model strings (@<your-connection-slug>/<model-name>).

OpenAI-compatible providers

These providers expose an OpenAI-compatible /v1/chat/completions endpoint. The gateway passes requests through with minimal transformation — just credential injection and streaming normalization.

Slug	Name	Base URL	Auth	Endpoints
`openai`	OpenAI	`https://api.openai.com/v1`	bearer	chat.completions, embeddings, images.generate, audio.transcriptions, audio.speech
`groq`	Groq	`https://api.groq.com/openai/v1`	bearer	chat.completions
`mistral-ai`	Mistral AI	`https://api.mistral.ai/v1`	bearer	chat.completions, embeddings
`deepseek`	DeepSeek	`https://api.deepseek.com/v1`	bearer	chat.completions
`cerebras`	Cerebras	`https://api.cerebras.ai/v1`	bearer	chat.completions
`sambanova`	SambaNova	`https://api.sambanova.ai/v1`	bearer	chat.completions
`together-ai`	Together AI	`https://api.together.xyz/v1`	bearer	chat.completions, embeddings
`fireworks-ai`	Fireworks AI	`https://api.fireworks.ai/inference/v1`	bearer	chat.completions, embeddings
`perplexity-ai`	Perplexity	`https://api.perplexity.ai`	bearer	chat.completions
`x-ai`	xAI	`https://api.x.ai/v1`	bearer	chat.completions
`anyscale`	Anyscale	`https://api.endpoints.anyscale.com/v1`	bearer	chat.completions, embeddings
`deepinfra`	DeepInfra	`https://api.deepinfra.com/v1/openai`	bearer	chat.completions, embeddings
`openrouter`	OpenRouter	`https://openrouter.ai/api/v1`	bearer	chat.completions, embeddings
`nebius`	Nebius AI Studio	`https://api.studio.nebius.ai/v1`	bearer	chat.completions, embeddings
`lambda`	Lambda	`https://api.lambdalabs.com/v1`	bearer	chat.completions
`dashscope`	Alibaba DashScope	`https://dashscope-intl.aliyuncs.com/compatible-mode/v1`	bearer	chat.completions, embeddings
`hyperbolic`	Hyperbolic	`https://api.hyperbolic.xyz/v1`	bearer	chat.completions
`moonshot`	Moonshot AI	`https://api.moonshot.cn/v1`	bearer	chat.completions
`novita-ai`	Novita AI	`https://api.novita.ai/v3/openai`	bearer	chat.completions
`upstage`	Upstage	`https://api.upstage.ai/v1/solar`	bearer	chat.completions, embeddings
`siliconflow`	SiliconFlow	`https://api.siliconflow.cn/v1`	bearer	chat.completions, embeddings
`lingyi`	01.AI (Lingyi)	`https://api.lingyiwanwu.com/v1`	bearer	chat.completions
`inference-net`	Inference.net	`https://api.inference.net/v1`	bearer	chat.completions
`lepton`	Lepton AI	`https://api.lepton.run/api/v1`	bearer	chat.completions
`kluster-ai`	Kluster AI	`https://api.kluster.ai/v1`	bearer	chat.completions
`nscale`	Nscale	`https://inference.api.nscale.com/v1`	bearer	chat.completions
`featherless-ai`	Featherless AI	`https://api.featherless.ai/v1`	bearer	chat.completions
`bytez`	Bytez	`https://api.bytez.com/v1`	bearer	chat.completions
`krutrim`	Krutrim	`https://cloud.olakrutrim.com/v1`	bearer	chat.completions
`302ai`	302.AI	`https://api.302.ai/v1`	bearer	chat.completions
`cometapi`	CometAPI	`https://api.cometapi.com/v1`	bearer	chat.completions
`matterai`	MatterAI	`https://api.matterai.so/v1`	bearer	chat.completions
`nextbit`	Nextbit	`https://api.nextbit.io/v1`	bearer	chat.completions
`z-ai`	Z.AI	`https://api.z.ai/api/paas/v4`	bearer	chat.completions
`iointelligence`	IO Intelligence	`https://api.intelligence.io.solutions/api/v1`	bearer	chat.completions
`aibadgr`	AIBadgr	`https://api.aibadgr.com/v1`	bearer	chat.completions
`ovhcloud`	OVHcloud AI Endpoints	`https://oai.endpoints.kepler.ai.cloud.ovh.net/v1`	bearer	chat.completions
`predibase`	Predibase	`https://serving.app.predibase.com/v1`	bearer	chat.completions
`monsterapi`	MonsterAPI	`https://llm.monsterapi.ai/v1`	bearer	chat.completions
`deepbricks`	Deepbricks	`https://api.deepbricks.ai/v1`	bearer	chat.completions
`lemonfox-ai`	Lemonfox AI	`https://api.lemonfox.ai/v1`	bearer	chat.completions

Providers with divergent APIs

These providers have non-OpenAI APIs. The gateway handles request/response transformation internally.

Slug	Name	Base URL	Auth	Endpoints
`anthropic`	Anthropic	`https://api.anthropic.com/v1`	x-api-key	chat.completions
`google`	Google Gemini	`https://generativelanguage.googleapis.com`	query-param	chat.completions, embeddings
`cohere`	Cohere	`https://api.cohere.com/v1`	bearer	chat.completions, embeddings
`ai21`	AI21 Labs	`https://api.ai21.com/studio/v1`	bearer	chat.completions
`reka-ai`	Reka AI	`https://api.reka.ai/v1`	bearer	chat.completions
`zhipu`	Zhipu AI	`https://open.bigmodel.cn/api/paas/v4`	bearer	chat.completions, embeddings

Notes:

Anthropic uses x-api-key header (not Bearer). The gateway injects this automatically.
Google authenticates via ?key=<API_KEY> query param, appended by the gateway. Use igris.chat.completions.create({ model: "@google-prod/gemini-2.0-flash", ... }) or raw HTTP. The Google subpath adapter (@igris-security/sdk/adapters/google) returns connection config for manual wiring since the official SDK doesn’t expose a unified baseURL override.
Cohere and AI21 speak their own chat API formats. The gateway translates OpenAI chat completions requests to their native format transparently.

Embeddings-only providers

Slug	Name	Base URL	Auth	Endpoints
`voyage`	Voyage AI	`https://api.voyageai.com/v1`	bearer	embeddings
`jina`	Jina AI	`https://api.jina.ai/v1`	bearer	embeddings
`nomic`	Nomic	`https://api-atlas.nomic.ai/v1`	bearer	embeddings

Passthrough / image / 3D providers

These providers use the passthrough endpoint — the gateway forwards the raw request body without transformation. Use them for image generation, 3D model generation, or any non-chat workload.

Slug	Name	Base URL	Auth	Endpoints
`stability-ai`	Stability AI	`https://api.stability.ai`	bearer	images.generate, passthrough
`segmind`	Segmind	`https://api.segmind.com/v1`	bearer	images.generate, passthrough
`recraft-ai`	Recraft AI	`https://external.api.recraft.ai/v1`	bearer	images.generate, passthrough
`tripo3d`	Tripo3D	`https://api.tripo3d.ai/v2`	bearer	passthrough
`meshy`	Meshy	`https://api.meshy.ai/v2`	bearer	passthrough

Self-hosted providers

These providers require you to supply a customBaseUrl on the connection. The gateway will reject requests if customBaseUrl is not set.

Slug	Name	Auth	Endpoints
`ollama`	Ollama	bearer	chat.completions, embeddings
`huggingface`	HuggingFace Inference	bearer	chat.completions, embeddings, passthrough
`triton`	NVIDIA Triton	bearer	chat.completions, passthrough
`modal`	Modal	bearer	chat.completions, passthrough
`openai-compatible`	OpenAI-compatible (custom)	bearer	chat.completions, embeddings

For Ollama running locally:

// Connection dashboard: set customBaseUrl to http://localhost:11434
await igris.chat.completions.create({
	model: "@ollama-local/llama3.2",
	messages: [{ role: "user", content: "Hello" }],
});

Adding a new provider

Providers are code-only — adding one requires a PR to packages/proxy/src/llm-providers/ with the provider implementation following the existing template.

Requesting a provider

Open a support request from the Igris dashboard with the provider name, API docs URL, and auth style.

Get Started

Connect

Govern

Monitor

Reference

Supported Providers

Supported Providers

OpenAI-compatible providers

Providers with divergent APIs

Embeddings-only providers

Passthrough / image / 3D providers

Self-hosted providers

Adding a new provider

Requesting a provider

​Supported Providers

​OpenAI-compatible providers

​Providers with divergent APIs

​Embeddings-only providers

​Passthrough / image / 3D providers

​Self-hosted providers

​Adding a new provider

​Requesting a provider

Supported Providers

OpenAI-compatible providers

Providers with divergent APIs

Embeddings-only providers

Passthrough / image / 3D providers

Self-hosted providers

Adding a new provider

Requesting a provider