SDK Compatibility
This page summarizes compatibility at the SDK surface level for the hosted Sentinel gateway.
Compatibility matrix
| SDK | Base URL override | Sentinel auth fit | Verified working | Supported with caveats | Not yet recommended |
|---|---|---|---|---|---|
| OpenAI SDK | Yes | Native fit | Chat, responses, embeddings, images, moderations, speech, transcriptions, models | Advanced OpenAI control-plane-like surfaces | Realtime and assistant-style workflows unless explicitly verified |
| Anthropic SDK | Yes | Requires authToken | Messages and core native surfaces | Batches and files | Blanket claims across beta or unverified surfaces |
| Google GenAI SDK | Yes | Requires custom Bearer header injection | Generate, models, embeddings | Batches and some advanced workflows | File upload and live/websocket as general support claims |
How to read this matrix
- Verified working means the current docs and examples support a confident public claim.
- Supported with caveats means the surface exists and may work well, but needs environment-aware validation.
- Not yet recommended means the surface should not be positioned as generally supported in public docs.
Highest-confidence support
- OpenAI SDK for the OpenAI-compatible lane
- Anthropic SDK for messages and core native HTTP surfaces
- Google GenAI SDK for generate, models, and embeddings
Supported with caveats
- Anthropic and Google file or batch workflows, because transport details and SDK behavior matter more than simple JSON inference routes
- Google live workflows, because websocket and runtime behavior form a separate compatibility class
Not enough to claim support
Do not claim support based only on:
- raw HTTP route existence
- a single curl success path
- a working direct provider example that bypasses Sentinel auth behavior
Recommendation
Document and validate SDK support using a smoke-test matrix, not a route list.