SDKs
Sentinel supports multiple official SDKs, but support should be evaluated by SDK surface, not just by raw HTTP route coverage.
The practical question is simple: which official client can you point at
https://gateway.caldorus.com with the least friction for your use case?
Default recommendation
Start with the OpenAI SDK and the OpenAI-compatible lane unless you need provider-native behavior.
This is usually the lowest-friction path and the broadest current compatibility surface.
Supported SDK families
Compatibility matrix
Use these pages to evaluate support at the client-behavior level, not just at the route level.
How to evaluate SDK support
When documenting or validating SDK support, ask:
- does the SDK support base URL override?
- can Sentinel auth be supplied in the way the SDK expects?
- does the SDK method call a route Sentinel implements exactly?
- are there route-shape or transport caveats for streaming, files, or live sessions?
A route can exist and still fall short of the behavior expected by an official SDK.
Practical recommendation
- default to the OpenAI-compatible lane if you want the least client customization
- use native Anthropic or Google lanes only when the official SDK behavior is the value you need
- treat file and live workflows as separate compatibility checks, not as implied by simple inference success
Choose the lane deliberately
- Stay OpenAI-compatible when portability and lower client customization matter most.
- Move to Anthropic native when native request and response behavior is the priority.
- Move to Google native when Gemini-specific SDK behavior matters more than a unified client shape.