--- title: "Cloudflare Workers AI free inference" description: "A recurring no-cost API allowance covering 8 cataloged models." canonical_url: "https://freeinferencing.com/provider/cloudflare_workers_ai/" md_url: "https://freeinferencing.com/provider/cloudflare_workers_ai.md" last_updated: "2026-09-19" --- # Cloudflare Workers AI > A recurring no-cost API allowance covering 8 cataloged models. ## Classification - **Directory:** Current - **Free access:** Always-free quota - **Status:** Available now - **Confidence:** High - **Payment card:** No - **Account:** Required - **Equivalent paid value:** $3.35/mo ## Models mentioned - `@cf/google/gemma-4-26b-a4b-it` - `@cf/zai-org/glm-4.7-flash` - `@cf/nvidia/nemotron-3-120b-a12b` - `@cf/openai/gpt-oss-120b` - `@cf/meta/llama-3.1-8b-instruct` - `@cf/deepseek-ai/deepseek-r1-distill-qwen-32b` - `@cf/mistralai/mistral-small-3.1-24b-instruct` - `@cf/qwen/qwen3.8-27b` ## Limits and terms ```yaml neurons_per_day: 10000 reset: 00:00 UTC free_plan_exhausted_behavior: Requests fail until reset. paid_plan_overage: $0.011 per 1,000 neurons. ``` ## What happens to your prompts? **Private.** Workers AI excludes Customer Content from storage, training, and improvement unless the customer deliberately enables a feature or consents. Privacy is audited separately from price. Review the current governing terms before sending sensitive or regulated data. ## Data governance and agreements ```yaml data_governance: review_status: reviewed plan_scope: Workers AI under Cloudflare self-serve or enterprise terms; optional Cloudflare storage products have their own retention configuration. prompt_retention: Inputs, outputs, embeddings, and training data are treated as Customer Content and are not stored by Workers AI unless the customer deliberately combines the service with storage products. response_retention: Same policy as other Customer Content. ordinary_logging: Operational account and service metadata is processed under the applicable Cloudflare agreement; the Workers AI data-use page does not claim that all metadata is zero retention. model_training: Cloudflare states it does not use Workers AI Customer Content to train models without explicit consent. product_improvement: Cloudflare states it does not use Workers AI Customer Content to improve Cloudflare or third-party services without explicit consent. human_or_operator_access: Access is governed by the applicable subscription agreement and DPA; no public Workers AI-specific human-review workflow is documented. subprocessors_and_routing: Cloudflare hosts inference for third-party model weights; model licenses may separately govern permitted use, while Cloudflare remains the service processor. deletion_controls: Customer-controlled storage services such as R2, KV, Durable Objects, or Vectorize determine storage and deletion when used with Workers AI. caveat: The no-training and no-improvement commitments apply to Customer Content in Workers AI; separately enabled storage and other Cloudflare products can persist that content. agreements: self_serve_subscription_agreement: https://www.cloudflare.com/terms/ privacy_policy: https://www.cloudflare.com/privacypolicy/ data_processing_addendum: https://www.cloudflare.com/cloudflare-customer-dpa/ ``` ## Eligibility ```yaml account_required: true payment_method_required: false model_license_acceptance_may_be_required: true ``` ## API compatibility and modalities - **Compatibility:** OpenAI Chat Completions, OpenAI Responses, OpenAI Embeddings - **Modalities:** Text generation, Embeddings ## Before you build with Cloudflare Workers AI ### Read the classification narrowly This record describes the bounded offer supported by evidence on 2026-09-19; it does not guarantee permanence, production suitability, uptime, latency, model quality, or access from every account and region. “Always-free quota” should be interpreted together with the Current directory placement, High confidence, No payment-card status, and the plan-specific sources below. ### Resolve the live model route The snapshot records 8 model IDs. Match the exact ID against the provider's current catalog before using it in code because zero-price routes, aliases, context limits, and feature support can rotate while an older documentation page remains online. ### Match the quota to the workload shape Translate the allowance into peak requests per minute, input and output tokens, concurrency, retries, and every daily or monthly ceiling that applies to the intended account. The first limit reached by the workload is the practical ceiling. A large token pool can still fail interactive bursts, and a high request limit can still fail long-context work. Include tool calls and retry traffic, test the largest realistic payload, and treat research, experimental, and community access as conditional on their eligibility and fair-use terms. ### Preserve billing and privacy boundaries The recorded payment-card requirement is No, and account access is required. Confirm both in the live signup flow, set provider-side budgets when charges are possible, and observe the balance or usage fields after a complete request. The prompt-handling classification is **Private** because Workers AI excludes Customer Content from storage, training, and improvement unless the customer deliberately enables a feature or consents. Re-read the terms for the exact route and plan before sending sensitive, regulated, or proprietary content. ### Follow the evidence, then re-check it This record links 11 first-party sources covering the offer, catalog, limits, pricing, terms, privacy, or adoption evidence available to the audit. Prefer the newest and most specific governing document or live catalog when sources disagree. A dated finding can become stale even when the page remains online, so retain the source and snapshot that supported the decision and submit a correction when a provider changes a material term. ### Plan fallback without policy drift A fallback should preserve modality, context length, streaming, structured output, tools, safety controls, and data terms, not only API syntax. Decide which errors may retry, cap retry storms, and prevent an exhausted free route from silently switching to a billable model. Rotating aliases and free pools can change behavior without changing the endpoint, so retain the response model field and test at least one substitute route before the primary offer becomes unavailable. ### Monitor the offer as a dependency Capture the model ID, response model, rate-limit headers, usage fields, latency, HTTP status, and provider request identifier. Watch authorization failure, quota exhaustion, catalog removal, policy revision, and balance movement as separate failure modes. Re-check the live catalog and governing sources on a schedule proportionate to the workload's importance, and keep an owner and exit path for any production dependency on volatile free capacity. ### Test one complete request before scaling Start with the smallest permitted request using the exact credential, model ID, endpoint, region, and account type intended for deployment. Record the status, headers, usage fields, response model, latency, and dashboard balance movement. Then exercise an invalid model, quota exhaustion, or rate limit so failure is explicit and cannot silently switch to a paid route. Validate streaming, structured output, and tool calls separately because a free model can expose fewer features than its paid counterpart. Keep a budget ceiling outside the application whenever billing is possible, and do not send sensitive data until the observed route matches the reviewed agreement. ## Primary sources - [Workers AI pricing](https://developers.cloudflare.com/workers-ai/platform/pricing/): Official Pricing - [Workers AI models](https://developers.cloudflare.com/workers-ai/models/): Official Catalog - [Models that require Workers Paid](https://developers.cloudflare.com/changelog/post/2026-07-28-models-require-workers-paid/): Official Changelog - [Workers AI general availability](https://blog.cloudflare.com/workers-ai-ga-huggingface-loras-python-support/): Announcement - [Self-Serve Subscription Agreement](https://www.cloudflare.com/terms/): Official Terms - [Privacy Policy](https://www.cloudflare.com/privacypolicy/): Official Privacy - [Customer Data Processing Addendum](https://www.cloudflare.com/cloudflare-customer-dpa/): Official Dpa - [Your Data and Workers AI](https://developers.cloudflare.com/workers-ai/platform/data-usage/): Official Docs - [Cloudflare Developer Week 2024 citing two million developers on the platform (2024-03-31)](https://blog.cloudflare.com/welcome-to-developer-week-2024/): Official Blog - [npm download stats for workers-ai-provider](https://www.npmjs.com/package/workers-ai-provider): Package Registry Stats - [2025 Stack Overflow Developer Survey technology section](https://survey.stackoverflow.co/2025/technology): Independent Survey ## Sitemap See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.