// Cloudflare AI Gateway

Route PasClaw through Cloudflare's AI Gateway.

Cloudflare AI Gateway lands in the PasClaw catalog as three rows. cloudflare uses the OpenAI-compat endpoint with the gateway's <provider>/<model> routing. cloudflare-anthropic and cloudflare-gemini are native passthroughs that carry each provider's own auth header. The catalog is the only change — existing provider units already handle the wire shape.

workers-ai defaultNative passthroughCatalog-onlyBring your gateway
01

Compat endpoint default

The cloudflare row points at the OpenAI-shape endpoint with a default of workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast. The gateway handles <provider>/<model> routing on the other side.

02

Native passthroughs

cloudflare-anthropic and cloudflare-gemini are passthroughs that preserve each provider's native wire shape and auth header, so cache_control, tool-call shapes, and streaming behaviour match the upstream provider exactly.

03

No new provider unit

These rows are catalog-only. Once api_base is set, the existing Anthropic, OpenAI, and Gemini provider units do all the wire work — no new code paths to learn.

From the documentation

Technical details

Implementation notes drawn from the PasClaw repository documentation.

Three catalog rows

Catalog-only — once api_base is set the existing provider units do the wire work.

  • cloudflare → workers-ai compat endpoint, default @cf/meta/llama-3.3-70b-instruct-fp8-fast.
  • cloudflare-anthropic → native Anthropic passthrough with its own auth header.
  • cloudflare-gemini → native Gemini passthrough with its own auth header.

Source documentation

Common questions

Frequently asked questions

Keep exploring

See how the rest of PasClaw fits together.

Relay pull-worker