FAQ

Is Sentinel only for OpenAI-compatible clients?

No. Sentinel supports an OpenAI-compatible lane for broad client compatibility and native Anthropic and Google lanes when provider-specific behavior is the reason you are adopting the SDK.

Should I default to native lanes?

No. Default to the OpenAI-compatible lane unless you specifically need native provider SDK semantics or route shapes. That keeps client customization lower and portability higher.

Is route support the same as SDK support?

No. SDK compatibility should be validated by SDK method behavior, not only by HTTP path presence.

Does Sentinel replace provider security?

No. Sentinel centralizes model access governance, but provider account hygiene, application security, and environment isolation still matter.

Can I deploy Sentinel incrementally?

Yes. That is the recommended rollout model. Start with one provider, one route plan, one application, and one environment before broad adoption. Sentinel is easier to operationalize when the first rollout path is intentionally narrow.

Is Google Live part of the OpenAPI reference?

No. It is intentionally documented separately because it is transport-distinct from the generated HTTP route inventory.