Skip to main content

Cloudflare AI Gateway

Route Keeptrusts traffic through a Cloudflare AI Gateway with an explicit provider-specific endpoint. Applications call the local Keeptrusts endpoint; the gateway owns the upstream credential and applies the configured policy chain.

Use this page when​

  • You already have access to Cloudflare AI Gateway and need to route it through Keeptrusts.
  • You want one explicit provider target that can be linted and reviewed before rollout.
  • You need a stable integration contract without copying mutable prices, context limits, or retirement dates into your config.

Prerequisites​

  • Install the kt CLI.
  • Obtain the upstream credential and an enabled model or endpoint from Cloudflare AI Gateway.
  • Obtain a Keeptrusts runtime API token for the gateway and a separate gateway key, access key, or personal API token for client requests. --agent uses only the runtime token.

Configure the provider​

Replace the replace-with-... values before starting the gateway. The example uses the current cloudflare-gateway runtime contract.

pack:
  name: cloudflare-gateway-integration
  version: 1.0.0
  enabled: true
policies:
  chain:
    - prompt-injection
    - pii-detector
    - audit-logger
providers:
  targets:
    - id: cloudflare-gateway-primary
      provider: cloudflare-gateway
      model: "replace-with-upstream-model-id"
      base_url: https://gateway.ai.cloudflare.com/v1/replace-with-account-id/replace-with-gateway-id/openai
      path_template: /chat/completions
      secret_key_ref:
        env: KEEPTRUSTS_OPENAI_API_KEY

The provider credential is resolved inside the gateway process. It is not the credential that client applications send to Keeptrusts.

Start and verify​

export KEEPTRUSTS_API_TOKEN="replace-with-keeptrusts-api-token"
export KEEPTRUSTS_OPENAI_API_KEY="replace-with-upstream-credential"

kt policy lint --file policy-config.yaml
kt gateway run \
  --agent cloudflare-gateway-integration \
  --listen 127.0.0.1:41002 \
  --policy-config policy-config.yaml

KEEPTRUSTS_API_TOKEN authenticates the gateway runtime and control-plane synchronization. Do not reuse it as the client credential.

In another terminal, export the separate client token, confirm the gateway is healthy, and send one request:

export KEEPTRUSTS_CLIENT_TOKEN="replace-with-separate-client-token"

curl -fsS http://127.0.0.1:41002/healthz
curl -fsS http://127.0.0.1:41002/v1/chat/completions \
  -H "Authorization: Bearer ${KEEPTRUSTS_CLIENT_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{"model":"replace-with-upstream-model-id","messages":[{"role":"user","content":"Reply with one short sentence."}]}'

Use the same model identifier in the request and target unless you have configured an explicit multi-model route.

Current Keeptrusts contract​

SettingBehavior
providercloudflare-gateway
Upstream requestThe OpenAI provider route at /openai/chat/completions
Upstream authenticationThe upstream provider credential for the BYOK path shown here
Client endpoint/v1/chat/completions on the Keeptrusts gateway

Cloudflare gateway URLs vary by underlying provider. This example uses Cloudflare's OpenAI provider route. The explicit path_template is required because that route ends in /openai/chat/completions, not /openai/v1/chat/completions. Construct a different target from Cloudflare's official provider instructions and the matching Keeptrusts adapter contract; changing only the URL is not sufficient when the provider uses a different request format.

Model and production checks​

  • Verify the model ID, region, endpoint availability, and account permissions in the official provider surface before rollout.
  • Treat pricing, max_context_tokens, retention metadata, and certifications as operator declarations. Add them only after checking your current contract.
  • Validate streaming, tools, structured output, and other optional request features for the selected request family and model; provider-wide assumptions are unsafe.
  • Keep the upstream credential server-side. Bind production listeners only to the intended interface and protect them with your normal ingress controls.

Next steps​