okhp3-cloudflare-worker-api-proxy

Topics in the source

• okhp3-cloudflare-worker-api-proxy
• Scope
• When to use this
• The 30-line Worker
• Setup steps (dashboard, no CLI required)
• Client-side fetch pattern
• Anthropic-specific variant
• Current Cloudflare limits

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 A Cloudflare Worker is a serverless function that runs at Cloudflare's edge. It handles the API call server-side, holds the API key in secrets, and returns | In scope | Out of scope | |---|---| | A narrow static-frontend-to-keyed-API proxy, CORS policy, secret binding, request validation, and client fetch example | Hiding a public endpoint, replacing authentication or authorization, rate-abuse prevention by assumption, or promising current plan limits without verification | the result to your browser. The key never appears in your JavaScript bundle. Use this pattern when: Your static site needs to call an API that requires a key (Anthropic, OpenAI, SendGrid, etc.) Exposing the key in client JavaScript would be a security risk or ToS violation You don't want to set up a full backend server 1. Create the Worker Cloudflare dashboard → Workers & Pages → Create Worker Name it (e.g., my-api-proxy) Paste the Worker code above Edit env.UPSTREAMAPIURL reference and auth header to match your API 2. Add secrets (not visible in code) Worker → Settings → Variables → Add variable Add as Secret (encrypted at rest): APISECRETKEY = your actual

This is an excerpt. Refer to the complete source and its current requirements.