Compatibility
Know which path is governed before you route production traffic.
CachePilot supports multiple provider surfaces, but their enforcement capabilities are not identical. This matrix reflects the proxy currently running behind Caddy on CachePilot's VPS.
| Traffic | Endpoint | Client | Mode | Receipts | Notes |
|---|---|---|---|---|---|
| OpenAI Responses | /v1/responses | OpenAI SDK / compatible client | Observe, govern, govern_transform | Full X-CP policy receipt | Recommended OpenAI path |
| OpenAI Chat Completions | /v1/chat/completions | OpenAI-compatible chat client | Observe telemetry only | Request ID; no policy receipt guarantee | No policy mutation today |
| Native Claude | /v1/messages | Anthropic SDK | Observe, govern, govern_transform | Provider, mode, policy, mutation, and cache receipts | Recommended Claude/Fable path |
| Claude/Fable via adapter | /v1/responses | Adapter emitting Responses-compatible traffic | Same as Responses when request shape and headers are preserved | Full X-CP policy receipt | Test adapter streaming/tools before production |
Adapter rule: compatibility is determined by the surface the adapter emits, not only by the model name. A Claude model sent through Chat Completions receives telemetry-only behavior today; a Responses-compatible adapter can use the governed Responses path.