Integrations

Meet teams in the tools they already operate.

Review what is implemented, experimental, deployment baseline, and planned across providers, coding agents, OIDC identity, infrastructure, and security operations.

Provider status is labeled honestly
OpenAI and Anthropic protocol simulators
OIDC and AWS deployment baseline

Working AI Gateway HQ provider inventory showing write-only provider-account boundaries and managed Bedrock status — **Integrations begin with an explicit credential boundary.**Provider accounts are named and health-visible in the working console while their secret values remain write-only.

Providers

BetaOpenAI

OpenAI-compatible Responses, chat-completions, embeddings, streaming, BYOK, and credential pools.

BetaAnthropic

Anthropic Messages-compatible forwarding, streaming, BYOK, and credential pools.

AvailableAWS Bedrock

Native Converse integration with a reviewed catalog of U.S. conversational models, settled-prepaid eligibility, reusable card or Stripe Link authorization, conservative reservation, and usage reconciliation. Model availability is checked before it appears in the customer catalog.

BetaAzure OpenAI

Azure endpoint, deployment, API-version, and API-key forwarding through the compatible runtime.

BetaGoogle Gemini

Gemini API keys through Google's OpenAI-compatible HTTPS endpoint.

BetaMistral AI

First-class Mistral BYOK with a fixed official host, zero-inference model-catalog verification, Chat Completions, and embeddings eligibility.

BetaGroq

First-class Groq BYOK with the official OpenAI-compatible base, model-catalog verification, Chat Completions, and Responses routing.

BetaTogether AI

First-class Together BYOK with the official API base, model-catalog verification, Chat Completions, and embeddings eligibility.

BetaFireworks AI

First-class Fireworks BYOK with the official inference base, serverless catalog verification, and Chat Completions eligibility.

BetaDeepSeek

First-class DeepSeek BYOK with its unversioned official API base, model-catalog verification, and Chat Completions eligibility.

Gateways

BetaOpenRouter

OpenRouter BYOK routes with the same gateway policy, prepaid billing, and metadata evidence path.

Agents & CLIs

Client configurationCodex CLI

Use an isolated Codex profile, a workload key, and the gateway's Responses endpoint without changing the user's normal provider configuration.

Client configurationClaude Code

Use Claude Code's documented gateway base URL and token variables with a workload key on the Messages-compatible boundary.

Client configurationOpenCode

Add an OpenCode v2 custom provider that reads a workload key from the environment and uses the gateway's Chat Completions boundary.

Operations

AWS baselineTerraform

A validated AWS deployment module is implemented. A customer-facing provider for routes, policies, budgets, and identities is planned.

Identity

Identity + SCIMMicrosoft Entra ID

Owner-managed OIDC or SAML 2.0 sign-in, exact Entra group-to-built-in-role rules, and connection-bound SCIM 2.0 user/group lifecycle with optional active-user login enforcement; live Entra conformance and workload federation remain planned.

Identity + SCIMOkta

Owner-managed OIDC or SAML 2.0 sign-in, exact Okta group-to-built-in-role rules, and connection-bound SCIM 2.0 user/group lifecycle with optional active-user login enforcement; live Okta conformance remains planned.

Security operations

PlannedSplunk

Native HEC delivery, signing, retry, and export checkpoints are planned; evidence is currently available through the control API.