Connect
Point your application at the Interdict base URL instead of the provider directly. Your provider credential is stored encrypted and used server-side only when a request passes the pre-provider controls.
Keep the OpenAI SDK and Chat Completions request format. Point the base URL at Interdict to apply request policy, structured PII protection on requests and responses, protected streaming, audit, usage accounting, budgets, and alerts.
The interface stays OpenAI-compatible — only the base URL changes.
https://www.interdictai.com/api/proxy/v1POST /v1/chat/completionsPoint your application at the Interdict base URL instead of the provider directly. Your provider credential is stored encrypted and used server-side only when a request passes the pre-provider controls.
Interdict applies application policy, prompt-injection checks, structured PII inspection, provider/model allowlists, token ceilings, and configured budgets before the upstream provider credential is retrieved.
Supported model output passes through response PII inspection and protected streaming. The call is correlated with audit, normalized usage/cost metadata, and configured alert evaluation.
Start on Free with no card required. Bring your own OpenAI credential and route through the checkpoint with the provider interface preserved.