Overview

Overview

DeepIntShield supports a wide range of AI providers, all accessible through a consistent OpenAI-compatible interface. This standardization allows you to switch between providers without modifying your application code, as all responses follow the same structure regardless of the underlying provider.

DeepIntShield can also act as a provider-compatible gateway (for example, Anthropic, Google Gemini, Cohere, Bedrock, and others), exposing provider-specific endpoints so you can use existing provider SDKs or integrations with no code changes, see What is an integration? for details.

Provider Support Matrix

The following table summarizes which operations are supported by each provider via DeepIntShield’s unified interface.

Provider	Models	Text	Text (stream)	Chat	Chat (stream)	Responses	Responses (stream)	Images	Images (stream)	Image Edit	Image Edit (stream)	Image Variation	Embeddings	TTS	TTS (stream)	STT	STT (stream)	Files	Batch	Count tokens
Anthropic (anthropic/<model>)	✅	✅	❌	✅	✅	✅	✅	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	✅	✅	✅
Azure (azure/<model>)	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	❌	✅	✅	✅	❌	✅	✅	❌
Bedrock (bedrock/<model>)	✅	✅	❌	✅	✅	✅	✅	✅	❌	✅	✅	❌	✅	❌	❌	❌	❌	✅	✅	✅
Cerebras (cerebras/<model>)	✅	✅	✅	✅	✅	✅	✅	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌
Cohere (cohere/<model>)	✅	❌	❌	✅	✅	✅	✅	❌	❌	❌	❌	❌	✅	❌	❌	❌	❌	❌	❌	✅
Elevenlabs (elevenlabs/<model>)	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	✅	✅	✅	❌	❌	❌	❌
Fireworks AI (fireworks/<model>)	✅	✅	✅	✅	✅	✅	✅	❌	❌	❌	❌	❌	✅	❌	❌	❌	❌	❌	❌	❌
Gemini (gemini/<model>)	✅	❌	❌	✅	✅	✅	✅	✅	❌	✅	❌	❌	✅	✅	✅	✅	✅	✅	✅	✅
Groq (groq/<model>)	✅	🟡	🟡	✅	✅	✅	✅	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌
Hugging Face (huggingface/<model>)	✅	❌	❌	✅	✅	✅	✅	✅	✅	✅	✅	❌	✅	✅	❌	✅	❌	❌	❌	❌
Mistral (mistral/<model>)	✅	❌	❌	✅	✅	✅	✅	❌	❌	❌	❌	❌	✅	❌	❌	✅	✅	❌	❌	❌
Nebius (nebius/<model>)	✅	✅	✅	✅	✅	✅	✅	✅	❌	❌	❌	❌	✅	❌	❌	❌	❌	❌	❌	❌
Ollama (ollama/<model>)	✅	✅	✅	✅	✅	✅	✅	❌	❌	❌	❌	❌	✅	❌	❌	❌	❌	❌	❌	❌
OpenAI (openai/<model>)	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
Opencode (opencode-zen/<model>, opencode-go/<model>)	✅	❌	❌	✅	✅	✅	✅	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌
OpenRouter (openrouter/<model>)	✅	✅	✅	✅	✅	✅	✅	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌
Parasail (parasail/<model>)	✅	❌	❌	✅	✅	✅	✅	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌
Perplexity (perplexity/<model>)	✅	❌	❌	✅	✅	✅	✅	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌
Replicate (replicate/<model>)	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	❌	❌	❌	❌	❌	❌	✅	❌	❌
SGL (sgl/<model>)	✅	✅	✅	✅	✅	✅	✅	❌	❌	❌	❌	❌	✅	❌	❌	❌	❌	❌	❌	❌
Vertex AI (vertex/<model>)	✅	❌	❌	✅	✅	✅	✅	✅	❌	✅	❌	❌	✅	❌	❌	❌	❌	❌	❌	✅
vLLM (vllm/<model>)	✅	✅	✅	✅	✅	✅	✅	❌	❌	❌	❌	❌	✅	❌	❌	✅	✅	❌	❌	❌
xAI (xai/<model>)	✅	✅	✅	✅	✅	✅	✅	✅	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌

• 🟡 Not supported by the downstream provider, but internally implemented by DeepIntShield as a fallback.
• ❌ Not supported by the downstream provider, hence not supported by DeepIntShield.
• ✅ Fully supported by the downstream provider, or internally implemented by DeepIntShield.

Note

Some operations are not supported by the downstream provider but can be emulated on top of a supported one. 🟡 For example, Text Completions are not supported by Groq, but DeepIntShield can serve them via the Chat Completions API. This is disabled by default; enable it by setting the enable_litellm_fallbacks flag to true in the client configuration. We do not recommend relying on these fallbacks, since text completions and chat completions behave differently. The option exists mainly to ease migration from LiteLLM (which offers the same fallbacks).

Notes:

• “Models” refers to the list models operation (/v1/models).
• “Text” refers to the classic text completion interface (/v1/completions).
• “Responses” refers to the OpenAI-style Responses API (/v1/responses). Non-OpenAI providers map this to their native chat API under the hood.
• Reranking (/v1/rerank) is currently supported for Cohere, Bedrock, Vertex AI, and vLLM. See each provider page for model-specific requirements.
• “Images” refers to the Image Generation API (/v1/images/generations).
• “Image Edit” refers to the Image Edit API (/v1/images/edits).
• “Image Variation” refers to the Image Variation API (/v1/images/variations).
• TTS corresponds to /v1/audio/speech and STT to /v1/audio/transcriptions.
• “Files” refers to the Files API operations (/v1/files) for uploading, listing, retrieving, and deleting files.
• “Batch” refers to the Batch API operations (/v1/batches) for creating, listing, retrieving, canceling, and getting results of batch jobs.

Response Format

All providers return responses in the OpenAI-compatible format. To switch providers, change the model prefix (for example openai/gpt-4o-mini to anthropic/claude-3-sonnet) - the response structure stays the same.

# Same response format regardless of provider
curl -X POST https://app.deepintshield.com/v1/chat/completions \
  -H "Authorization: Bearer sk-bf-your-virtual-key" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "openai/gpt-4o-mini",
    "messages": [{"role": "user", "content": "Hello!"}]
  }'

# Returns OpenAI-compatible format:
{
  "id": "chatcmpl-123",
  "object": "chat.completion",
  "choices": [
    {
      "index": 0,
      "message": {
        "role": "assistant",
        "content": "Hello! How can I help you?"
      },
      "finish_reason": "stop"
    }
  ],
  "usage": {
    "prompt_tokens": 10,
    "completion_tokens": 9,
    "total_tokens": 19
  }
}

Custom Providers

In addition to the built-in providers, DeepIntShield supports custom provider configurations. Custom providers allow you to create multiple instances of the same base provider with different configurations, request type restrictions, and access patterns. This is useful for environment-specific configurations, role-based access control, and feature testing.

Learn more: Custom Providers

Benefits

The consistent interface across providers enables:

• Provider switching without code modifications
• Fallback configurations for improved reliability
• Load balancing across multiple providers
• OpenAI-compatible patterns for all providers

Provider Metadata

Provider information is included in the extra_fields section of each response, providing transparency into which provider handled the request and any provider-specific metadata.

Raw Request/Response Access

You can optionally have each response include the raw request that was sent to the provider and the raw response received back. This is useful for debugging, auditing, and cost analysis.

What’s included:

• raw_request - The exact request body (JSON/data structure) that was sent to the provider’s API endpoint
• raw_response - The exact response body received from the provider

Example: When you send a Chat Completions request with max_completion_tokens to Anthropic, the raw request shows the provider-native max_tokens field that was actually sent. Enable raw request/response to inspect these provider-native fields.

{
  "extra_fields": {
    "provider": "anthropic",
    "raw_request": {
      "model": "claude-3-5-sonnet",
      "max_tokens": 4096,
      "messages": [...]
    },
    "raw_response": {
      "id": "msg_...",
      "type": "message",
      "content": [...],
      "usage": {
        "input_tokens": 123,
        "output_tokens": 456
      }
    }
  }
}

Use cases:

• Debugging - See the exact provider-native request your call produced
• Auditing - Track exactly what was sent to external APIs
• Cost analysis - See the provider’s raw token counts
• Integration testing - Validate provider-specific request/response details

Configuration options:

• Gateway Provider Configuration - Configure send_back_raw_response via API, UI, or config file

Note

Enabling raw request/response may increase response payload size and has minimal performance impact. Use it selectively in debugging/testing environments or when you need audit trails.