# Cloudflare AI Gateway vs Hugging Face Inference Providers (slim)

> Cloudflare AI Gateway scores 67.8 (B) to Hugging Face Inference Providers's 54 (C) for llm inference. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-hugging-face-inference-providers.md (~7,550 tokens) · this version ~3,330 tokens · JSON https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-hugging-face-inference-providers.json · canonical https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-hugging-face-inference-providers
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Cloudflare AI Gateway scores 67.8 (B) on agent readiness against Hugging Face Inference Providers's 54 (C), and leads in 6 of 7 scored categories. Hugging Face Inference Providers leads on maintenance & community. Both do llm inference.

- Cloudflare AI Gateway: B 67.8, rank #300 of 1486 · https://www.anchorterminal.com/tools/cloudflare-ai-gateway.min.md
- Hugging Face Inference Providers: C 54, rank #920 of 1486 · https://www.anchorterminal.com/tools/hugging-face-inference-providers.min.md
- Cloudflare AI Gateway, good for Teams that already hold a Cloudflare account and want one token, one bill, logs, budgets and fallbacks in front of several model providers, or that want to keep their own provider keys behind a proxy with spend limits. Ahead on Reliability, 66 against 25; Schema & documentation, 75 against 62; Agent ergonomics, 73 against 58; Payments & pricing, 52 against 20.
- Hugging Face Inference Providers, good for Agents and developers who want open-weight models from several hosts on one token and one bill, with a public price and capability list per provider. Ahead on Maintenance & community, 80 against 75. Also No incidents deducted, where Cloudflare AI Gateway loses 3 points for them.

| Category | Cloudflare AI Gateway | Hugging Face Inference Providers |
| --- | --- | --- |
| Reliability (16%) | 66 | 25 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 75 | 62 |
| Agent ergonomics (13%) | 73 | 58 |
| Security & auth (14%) | 80 | 79 |
| Payments & pricing (10%) | 52 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 80 |
| Transparency & trust (7%) | 74 | 71 |

| Fact (where they differ) | Cloudflare AI Gateway | Hugging Face Inference Providers |
| --- | --- | --- |
| Vendor | Cloudflare, Inc. | Hugging Face, Inc. |
| Hosted endpoint | `https://api.cloudflare.com/client/v4/accounts/{account_id}/ai` | `https://router.huggingface.co/v1` |
| Pricing | Freemium | Pay per use |
| x402 | payer tooling only | no |
| Licence | Proprietary service under Cloudflare's Self-Serve Subscription Agreement and its service-specific terms. Third-party models carry their providers' terms, linked from each model page. `ai-gateway-provider` is MIT and Cloudflare's OpenAPI repository is BSD-3-Clause | Proprietary service under the Hugging Face Terms of Service, which name Inference Providers. The `huggingface_hub` Python client is Apache-2.0 and `@huggingface/inference` is MIT |
| Last release | 2026-10-21 | 2026-10-29 |
| Terms last updated | 2025-09-12 | 2022-09-15 |
| Privacy policy last updated | no date given | 2023-03-28 |
| Terms restrict automated access | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 251k npm/wk | 483k npm/wk, 71.5M PyPI/wk |
| Agent reviews | 3/5 (4) | none |

Why the edge:
- Reliability, Cloudflare AI Gateway +41: Cloudflare AI Gateway 66 (Hosted reading. www.cloudflarestatus.com is a Statuspage with AI Gateway, Workers AI and API as separate components (20). The incidents feed read on 9 October held 50 incidents from 21 September to 8 October 2026, none naming AI Gateway, with an 18-minute minor API incident on 7 October and delayed permission changes on 30 September. On 1 November the host's history.atom held only scheduled maintenance for 2 to 6 November, and the history page loads by script. Whether the incidents posted from 16 to 31 October name AI Gateway wasn't read for this listing (cloudflare-r2, cloudflare-workers-ai and cloudflare-email-service read that list for their own components only), and 3 August to 20 September and 9 to 15 October went unread too. An unread window isn't credited, so the line rests on the 21 September to 8 October reading alone, as on 9 October (10 of 30). Unified Billing traffic is limited to 200 requests per 60 seconds per gateway, re-read on 1 November, the Cloudflare API to 1,200 requests per five minutes per token, and BYOK traffic has no gateway limit (15). Over-limit and over-budget requests return 429, the Cloudflare API returns `retry-after` and `Ratelimit` headers for its own limit, and retries with backoff and model fallbacks can be set per request or per gateway. No `Retry-After` was found for the gateway's own 429, and nothing separates a rate-limit 429 from a spend-limit 429 (11 of 15). No SLA naming AI Gateway was found. The Enterprise SLA lists service-specific SLAs for R2, Queues and Workers only (0). The core product carries no beta label, and Machine Payments is in beta (10). 20 + 10 + 15 + 11 + 0 + 10 = 66.); Hugging Face Inference Providers 25 (Hosted lines. status.huggingface.co is a Better Stack page with 90-day component history for the Hub, Inference Endpoints, Spaces, the CDNs and Jobs, but no component for Inference Providers or the router (10 of 20). With no component, there is no readable incident history for the surface agents call, and the feed's 23 items from 10 June to 7 October 2026 don't name it (5). No rate limits for the router were found; the Hub rate-limits page gives numbers for Hub APIs, resolvers and pages only (0). No 429 or overload guidance for the router was found (0). No SLA found (0). Chat completions on the router is generally available; the Responses API is labelled beta (10). Routing between providers with `:fastest` or `:cheapest` softens a single provider's outage, which this checklist doesn't score.)
- Payments & pricing, Cloudflare AI Gateway +32: Cloudflare AI Gateway 52 (x402 is in beta on `POST /ai/run` since 30 September 2026 for four open models of 241 in the catalogue. It still needs a Cloudflare API token, a United States account and a card on file, and the OpenAI-style and Anthropic-style routes are not covered. We did not call it (12 of 40). The gateway's own prices, the 5 per cent credit fee and per-model token prices are published without a login (20). Core functions are free on all plans, and calls made with the caller's own provider keys carry no Cloudflare charge. We did not sign up to confirm that no card is asked for (20). A person creates the account and the first token in a browser, and the x402 route needs both (0). The Machine Payments page (last updated 30 September, the same four models) and the pricing page (last updated 30 October) were re-read on 1 November. 12 + 20 + 20 + 0 = 52.); Hugging Face Inference Providers 20 (No x402, MPP or L402 (0). Per-token prices for every model and provider published without a login in the router's /v1/models and on model pages (20). No free tier since 7 October 2026, when free users lost their included monthly credits; PRO's $2.00 of credits needs a subscription (0). Sign-up, token creation and credit purchase are browser steps (0).)
- Agent ergonomics, Cloudflare AI Gateway +15: Cloudflare AI Gateway 73 (Router, read on the model lines (tool use, structured output, caching, context, batch, SDKs, errors). Three provider request formats pass through, OpenAI Chat Completions, OpenAI Responses and Anthropic Messages, and provider-native tools such as web search are documented. Tool behaviour depends on the routed model (15 of 20). No gateway page on structured output was found, so it rests on each provider's format (8 of 15). A response cache for identical requests with TTLs up to a month and custom keys, off by default, and cached-input prices on model pages (11 of 15). The catalogue lists models with a context of about one million tokens, a judgement call since a router has no default model (15). Background requests on `/ai/run` post the result to a webhook, best-effort and with no retry, and no batch discount is stated (5 of 10). The OpenAI and Anthropic SDKs work with a changed base URL, and Cloudflare's own SDKs cover TypeScript, Python and Go (10). Status codes are documented page by page (401 with 10000 or 2009, 400, 404, 429, 503) with `cf-aig-step` and routing headers on responses, and no consolidated error reference (9 of 15).); Hugging Face Inference Providers 58 (Router reading of the model checklist (tool use, structured output, caching, context, batch, SDKs, errors), as for openrouter. Tool calling through the OpenAI-compatible API with `tool_choice`, support flagged per provider in /v1/models (15 of 20). Structured output documented, support flagged per provider and false on some (10 of 15). No prompt caching guidance found, though the Enterprise usage API counts cached input tokens (3 of 15). Routes to models with up to 1,048,576 tokens of context per the model list, a judgement call since a router has no default model (15). No batch API (0 of 10). Official clients in Python and JavaScript, plus any OpenAI SDK (10). Errors not documented (5 of 15).)
- Schema & documentation, Cloudflare AI Gateway +13: Cloudflare AI Gateway 75 (Router, scored on the API lines. Cloudflare's public OpenAPI 3.0.3 document, updated 9 October 2026, has 36 paths and 67 operations under `/ai-gateway` and includes `POST /ai/run`. The `/ai/v1/chat/completions`, `/ai/v1/responses` and `/ai/v1/messages` routes and the `gateway.ai.cloudflare.com` endpoints are not in it (20 of 25). An AI Gateway `llms.txt` and a Markdown copy of every page (10). Every management operation has a description, and the usage pages say which endpoint to use for new work and which are deprecated (15 of 20). Gateway settings are typed with enums and required fields, while the `input` object of `/ai/run` is free-form and depends on the model (10 of 15). Curl, SDK and Worker examples on most pages. No table of gateway error codes was found. The troubleshooting page still tells callers to keep the Cloudflare token out of `Authorization`, which the authentication page contradicts for the REST API, and the changelog of 6 October links a BYOK address that differs from the docs index (9 of 15). A dated changelog with RSS. The API has no version of its own beyond `/client/v4`, and the move of new customers to Workers Logs on 24 September 2026 has no changelog entry (11 of 15).); Hugging Face Inference Providers 62 (No OpenAPI document for the router (openapi.json paths answer 404). The task reference pages are generated from typed JSON Schema specs in huggingface.js, and the router's /v1/models gives a machine-readable catalogue, so 12 of 25. llms.txt for the Inference Providers docs and a Markdown twin of every page via `.md` (10). Guides say what each task and policy is for, with a quick setup page for coding agents (14 of 20). Parameter tables with types for chat completion, though `response_format` and `tool_choice` show as unknown types (9 of 15). Examples in Python, JavaScript and curl on every task page, but no documented error responses for the router (9 of 15). No changelog of its own; the Hub changelog doesn't cover it and dated changes are only in the hub-docs history (8 of 15).)
- Maintenance & community, Hugging Face Inference Providers +5: Cloudflare AI Gateway 75 (Router, read on the model lines. The newest changelog entry is 21 October 2026 (`createAI` in the Agents SDK replaces `ai-gateway-provider` and `workers-ai-provider`, which are feature frozen and deprecated), after UUIDv7 log IDs on 8 October and the error-code change on 6 October (30). No minimum notice for API changes was found. The Universal Endpoint and the compat route are marked deprecated with a promise to keep working and no end date, and the error-code change of 6 October and the log ID format change of 8 October took effect on the day each was announced (5 of 12). No gateway endpoint was shut down in the last 90 days that we found. Thirteen dataset, evaluation and spending-limit operations are marked deprecated in the OpenAPI document with no changelog entry, per the 9 October check (5 of 8). A dated changelog with RSS and thirteen entries between 5 August and 21 October 2026. The Discord community was not sampled (11 of 15). Replies on the SDK repositories were not examined (3 of 10). `cloudflare` for TypeScript 7.3.0 and Python 5.9.0 are the newest tags on 1 November, per the other Cloudflare re-checks' clones that day, and `ai-gateway-provider` is deprecated in favour of `createAI` in the `agents` package, an official successor (14 of 15). The OpenAPI repository was updated on 9 October 2026, per the 9 October check, not re-read on 1 November (7 of 10). 30 + 5 + 5 + 11 + 3 + 14 + 7 = 75.); Hugging Face Inference Providers 80 (Model reading. huggingface_hub 2.4.0 tagged on 29 October 2026 and the Inference Providers docs updated daily by an automated job, last on 6 November (30). huggingface_hub 2.2.0, 2.3.0 and 2.4.0 and @huggingface/inference 4.13.28 to 4.13.32 in the 90 days (20). No dedicated changelog; the Hub has a forum and Discord, and GitHub issue replies were not read (8 of 15). Current official SDKs in Python and JavaScript (15). The Python client supports Python 3.10 and later, per the Inference Endpoints check; CI not read (7 of 10).)