Skip to main content
Version: Next

API compatibility

Limitations​

  • Supported gateway providers. External LLM Gateway clients can use OpenAI, Anthropic, Generic Responses Compatible, Amazon Bedrock, Amazon Bedrock API key, Azure, and Azure Entra providers. Other configured providers such as Google Vertex are not exposed through provider-specific gateway routes yet.
  • Access is policy-bound. You can only call models an administrator has granted you through a Model Access Policy, and /v1/models returns only those models. A request for a model you don't have access to is rejected.
  • Send the exact model name. Use the model name shown on the Models page, or a configured llm / llm-mini alias. Aliases still require the matching provider route and access to the resolved model; see Model aliases.
  • Azure model discovery is OpenAI-only. The Azure /v1/models and /openai/v1/models routes return accessible OpenAIResponses deployments. Microsoft Foundry does not expose an Anthropic Models API, so pass AnthropicMessages deployment names explicitly.
  • Claude Code model discovery caveats. Gateway model discovery is off by default and requires Claude Code v2.1.129 or later for the standard Anthropic gateway path. Claude Code's Bedrock Mantle mode may not populate the /model picker from Obot, so pass --model or select an enabled Mantle model manually.
  • OpenAI-compatible routes use the Responses API. The OpenAI, Generic Responses Compatible, Bedrock, and Azure OpenAI-compatible routes support the Responses API (/v1/responses); the Chat Completions endpoint is not currently supported. Codex uses the Responses API by default.
  • Usage is recorded. Requests count toward Obot token usage.
  • Audit logs can be exported. Administrators can create one-time or scheduled exports for LLM gateway audit logs. See Audit Log Export.