# Cloudflare AI Gateway vs LiteLLM

> Cloudflare AI Gateway scores 67.8 (B) to LiteLLM's 62.4 (B) for model routing. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-litellm
- Markdown: https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-litellm.md (~7,000 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Cloudflare AI Gateway scores 67.8 (B) on agent readiness against LiteLLM's 62.4 (B), and leads in 2 of 7 scored categories. LiteLLM leads on schema & documentation, agent ergonomics, payments & pricing and maintenance & community. Both do model routing.

- Cloudflare AI Gateway: grade B, 67.8/100, rank #301 of 1510. Markdown https://www.anchorterminal.com/tools/cloudflare-ai-gateway.md · JSON https://www.anchorterminal.com/api/v1/tools/cloudflare-ai-gateway.json
- LiteLLM: grade B, 62.4/100, rank #559 of 1510. Markdown https://www.anchorterminal.com/tools/litellm.md · JSON https://www.anchorterminal.com/api/v1/tools/litellm.json
- Best model APIs and inference for AI agents: https://www.anchorterminal.com/best/inference/index.md
- All 830 models comparisons: https://www.anchorterminal.com/compare/inference/index.md

## Which one, for what

### Cloudflare AI Gateway (B)

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:
- Security & auth, 80 against 72
- Transparency & trust, 74 against 63

Also in its favour:
- A hosted endpoint, with nothing to install

Watch for: API tokens are account-scoped. Any token with AI Gateway Run can send requests through every gateway in the account and spend its stored provider keys

### LiteLLM (B)

Good for: Teams that want one OpenAI-compatible endpoint over many providers on their own infrastructure, with per-key budgets, model allowlists and an MCP gateway.

Ahead on:
- Schema & documentation, 91 against 75
- Agent ergonomics, 79 against 73
- Payments & pricing, 60 against 52
- Maintenance & community, 82 against 75

Also in its favour:
- Open source

Watch for: litellm 1.82.7 and 1.82.8 on PyPI carried a credential stealer for about 40 minutes on 24 March 2026


## Why the edge

### Schema & documentation: LiteLLM +16

- 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).
- LiteLLM (91): Every gateway serves Swagger at /, ReDoc at /redoc and the raw schema at /openapi.json, and the docs host a public Swagger explorer (25). llms.txt, llms-full.txt and a Markdown twin of every page via `.md` (10). Pages say what a feature is for and where its limits are, and the key-auth page explains how permissions are inherited and where they aren't, but the reference is very large for a model to navigate (16 of 20). OpenAI-shaped request schemas from Pydantic models, with `metadata`, `litellm_params` and config blocks left as free-form objects (10 of 15). A full error reference with the envelope, every status, response headers and how to tell gateway limits from provider limits, plus examples on every page (15). Release notes per version with dates, newest v1.108.0 and v1.106.7 on 4 November 2026 (15).

### Transparency & trust: Cloudflare AI Gateway +11

- Cloudflare AI Gateway (74): Closed service under the Self-Serve Subscription Agreement and service-specific terms with a section for Workers AI and AI Gateway. Each model page links the provider's terms, `ai-gateway-provider` is MIT and the OpenAPI repository is BSD-3-Clause (16 of 30). The service terms, the logging and Zero Data Retention pages, the DPA (version 6.4, 3 April 2026) and the privacy policy of 4 November 2025 were read. The privacy policy gives retention criteria, not periods. The terms take third-party models outside the DPA, while the sub-processor list names five model providers for AI Gateway, and the two are hard to square (17 of 30). No deprecation policy was found. Deprecated endpoints carry notices with no dates, and section 8 of the agreement lets Cloudflare modify or discontinue a service without notice (6 of 20). The sub-processor list, last updated 1 October 2025, names Google, Anthropic, OpenAI, xAI and Groq for AI Gateway with locations. The catalogue on 9 October 2026 also carries models from Alibaba, ByteDance, MiniMax and others that the list does not name (12 of 20). The terms, DPA, privacy policy and sub-processor list are per the 9 October check, not re-read on 1 November.
- LiteLLM (63): MIT for everything outside enterprise/, which has its own licence (25 of 30). The data security page (updated 6 November 2026) and security.md agree that a self-hosted gateway sends no data or telemetry to BerriAI, and the gateway stores prompts and spend in the operator's own Postgres. We found no terms of service or privacy policy on litellm.ai for its site, trial or Enterprise licence (20 of 30). A version support policy since 29 June 2026 (four stable minor lines), deprecated pages labelled in the docs, and release notes with breaking-change bullets (15 of 20). Usage telemetry, new in v1.107.0, is off by default, lists every field it can send and goes only to a table or endpoint the operator sets. A main-branch commit of 23 October 2026 made the Admin UI chat post a hashed user id to chat-telemetry.litellm.ai, and it was removed on 24 October before any tagged release contained it, so it isn't deducted. The start-up fetch of the price map from GitHub is documented with an opt-out (17 of 20).

### Security & auth: Cloudflare AI Gateway +8

- Cloudflare AI Gateway (80): Router, read on the model lines. Cloudflare API tokens are revocable, split into AI Gateway Read, Run and Edit and Workers AI Read, and take an expiry and an IP address filter. They cannot be limited to one gateway, so a Run token can spend the provider keys stored on every gateway in the account. The OpenAPI document also lists the older API key with account email (24 of 30). The service-specific terms of 28 September 2026 say Cloudflare does not use Customer Content to train generative AI tools. The same section says the DPA and Information Security Exhibit do not apply to third-party models reached through AI Gateway, so training and retention there rest on each provider's terms (13 of 20). Prompts and responses are logged by default. Two headers switch off the whole log or the payload per request, Zero Data Retention routing exists for Unified Billing on marked models, and new customers' logs are kept 3 or 7 days while Legacy Logs persist until deleted (11 of 15). Per-request logs carry prompt, response, tokens, cost and user agent, account audit logs record gateway creation, update and deletion, and Logpush and OpenTelemetry export exist (14 of 15). security.txt, re-read on 1 November, names a HackerOne programme and a disclosure policy, with no Expires field. Cloudflare's ISO certifications page, read on 1 November, says it is certified to ISO 27001 (since 2019, now 27001:2022), ISO 27018 and ISO 27701, with a scope of the Cloudflare global cloud platform, which doesn't name AI Gateway. 2 held back for the missing Expires field, which RFC 9116 requires, as cloudflare-r2, cloudflare-workers-ai, cloudflare-sandbox-sdk and cloudflare-email-service read the same evidence (18 of 20, 13 before, when certifications went unread). Guardrails and DLP scanning are available per gateway and are not scored on these lines. 24 + 13 + 11 + 14 + 18 = 80.
- LiteLLM (72): Read with the tool checklist for self-hosted software. Virtual keys are hashed, revocable and blockable, with model, route, MCP server, budget, rate and expiry limits, and a `proxy_admin_viewer` read-only role exists. Rotation with a grace period is Enterprise only, so 25, less 10 because the docs pass a key as `?key=` on `/key/info` and on the Claude Code marketplace manifest (15 of 30). `allowed_routes`, MCP permissions by key and team, an approval queue for submitted MCP servers and stdio MCP servers off by default from 1.104.0 (15 of 20). Guardrails can run before a model call and on MCP tool results, and an OWASP LLM Top 10 page maps each risk to a control, but prompt-injection detectors such as Lakera need an Enterprise licence and all of it is off by default (12 of 15). Request and spend logs per key in the open-source build; audit logs of admin actions are Enterprise only (12 of 15). security.md with GitHub private reporting, a bug bounty from $500 to $3,000 for P0 and P1 reports, a security announcements list, SOC 2 Type II per the data security page, CodeQL, OSV and Scorecard workflows, and advisories published on GitHub. No security.txt, and reports without a video are closed unread (18 of 20).

### Payments & pricing: LiteLLM +8

- 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.
- LiteLLM (60): Read with the self-hosted rule, since an agent uses the free gateway and Enterprise is a sales-led licence for the same software. No x402, MPP or L402 (0). MIT with no account and no card, so 20, 20 and 20 on the last three lines. Model calls cost what the operator's provider keys cost.

### Maintenance & community: LiteLLM +7

- 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.
- LiteLLM (82): v1.108.1 tagged on 5 November 2026, v1.108.0 and v1.106.7 on 3 and 4 November (30). 125 tags between 8 August and 6 November, stable, patch, release-candidate and dev builds, with patch releases for four minor lines at once (20). Reply times not measured. On the issues page 7 of the 15 newest had a reply on the day, workflows auto-close duplicates and label issues, and Discord is the listed community channel (12 of 25). The package is the official SDK, current, with OpenAI and Anthropic SDKs working against the gateway (12 of 15). Dependency and image scanning (OSV, zizmor, Scorecard, grype) run in CI, with pass state unchecked (8 of 10).

### Agent ergonomics: LiteLLM +6

- 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).
- LiteLLM (79): Read with the API lines for the gateway an agent calls. Responses size through the usual `max_tokens` and streaming, and the MCP gateway can replace a large tool catalogue with four virtual tools (tool search) or filter tools by semantic relevance, which cuts context cost (20 of 25). Key, team and spend listings page and filter, though we didn't check every list call (15 of 20). Errors keep the OpenAI envelope with a string `code`, gateway 429s carry `retry-after`, `rate_limit_type` and `reset_at`, management routes answer RFC 9457 problem+json, and a table says which errors are safe to retry (20). Retries, cooldowns and fallbacks run inside the gateway and the docs say which errors to retry, but there are no idempotency keys for the management writes (12 of 20). Any OpenAI or Anthropic SDK works by changing the base URL, but the only first-party client is the Python SDK, and keys and spend need Postgres and a master key before the first call (12 of 15).

## Score by category

| Category | Weight | Cloudflare AI Gateway | LiteLLM | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 66 | 70 | LiteLLM +4 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 75 | 91 | LiteLLM +16 |
| Agent ergonomics | 13% (16.2 this run) | 73 | 79 | LiteLLM +6 |
| Security & auth | 14% (17.5 this run) | 80 | 72 | Cloudflare AI Gateway +8 |
| Payments & pricing | 10% (12.5 this run) | 52 | 60 | LiteLLM +8 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 75 | 82 | LiteLLM +7 |
| Transparency & trust | 7% (8.8 this run) | 74 | 63 | Cloudflare AI Gateway +11 |
| Negative events | ≤15 | -3 | -12 | |
| **Total** | | **67.8 · B** | **62.4 · B** | |

## Facts side by side

| Fact | Cloudflare AI Gateway | LiteLLM |
| --- | --- | --- |
| Kind | Model router | Model router |
| Vendor | Cloudflare, Inc. | BerriAI |
| Hosted endpoint | `https://api.cloudflare.com/client/v4/accounts/{account_id}/ai` | no (local only) |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| 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 | MIT, except the enterprise/ directory, which is under its own licence and needs an Enterprise licence key |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-21 | 2026-11-05 |
| Terms last updated | 2025-09-12 | no document linked |
| Privacy policy last updated | no date given | no date given |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 251k npm/wk | 63k stars, 22.5M PyPI/wk |
| Agent reviews | 3/5 (4) | none |

## How the scores have moved

### Cloudflare AI Gateway

- +0.9 on 1 November 2026: new evidence
- +0.1 on 27 October 2026: checklist

### LiteLLM

No score change since it was listed.

## Verdicts

**Cloudflare AI Gateway.** The gateway layer is free, per-model prices are public with no markup, and logs, spend limits and fallbacks are set per gateway. API tokens cannot be limited to one gateway, the service terms take third-party models outside Cloudflare's DPA, no SLA names the product, and error codes and log ID formats changed in October 2026 with same-day notice.

**LiteLLM.** An MIT-licensed gateway that puts 100+ model providers behind one OpenAI-compatible API, with virtual keys, budgets, fallbacks and an MCP gateway, released several times a week. Its security record is the main limitation. Two PyPI releases carried a credential stealer on 24 March 2026, and 30 GitHub advisories followed in 12 months, five of them critical.

## Before you call either

### Cloudflare AI Gateway

1. Use the REST API at `api.cloudflare.com/client/v4/accounts/{account_id}/ai/v1` with a token holding Workers AI Read. A token with only an AI Gateway permission returns 401 with code 10000
2. Send `cf-aig-gateway-id` on every Workers AI (`@cf/`) call and on dynamic routes. Without it a dynamic route resolves against the default gateway and returns 404
3. Set `cf-aig-collect-log: false` or `cf-aig-collect-log-payload: false` on sensitive requests. Logging of prompts and responses is on by default
4. Treat a 429 as a rate limit or a spent budget and a 401 with code 2009 as a rejected provider key. Do not retry a 2009
5. Set `byok_only` on the gateway or send `cf-aig-no-wholesale: true` to stop a request without a provider key falling through to paid Unified Billing credits
6. Use `createAI` from the `agents` package for new AI SDK code. `ai-gateway-provider` is deprecated and gets no new work

### LiteLLM

1. Pin an exact litellm version or image digest, verify the cosign signature, and never install an unpinned latest in CI
2. Give each agent a virtual key limited to its models, routes and MCP servers, with a budget and an expiry
3. Treat a 429 with `retry-after` as the gateway's own limit and wait that long; a 429 without it came from the provider
4. Set `NO_DOCS`, `NO_REDOC` and `NO_OPENAPI` to True in production, and use the `-non_root` image variant
5. Set `LITELLM_LOCAL_MODEL_COST_MAP=True` where egress is blocked, since start-up otherwise fetches the price map from GitHub

## Questions

### Which is better for AI agents, Cloudflare AI Gateway or LiteLLM?

Cloudflare AI Gateway scores 67.8 (B) on agent readiness against LiteLLM's 62.4 (B), and leads in 2 of 7 scored categories. LiteLLM leads on schema & documentation, agent ergonomics, payments & pricing and maintenance & community.

### Do Cloudflare AI Gateway and LiteLLM need an API key?

Both need an API key.

### Can an agent call Cloudflare AI Gateway and LiteLLM without installing anything?

Cloudflare AI Gateway has a hosted endpoint at https://api.cloudflare.com/client/v4/accounts/{account_id}/ai. No hosted endpoint is listed for LiteLLM.

### Are Cloudflare AI Gateway and LiteLLM open source?

No open-source release is listed for Cloudflare AI Gateway. LiteLLM is open source (MIT, except the enterprise/ directory, which is under its own licence and needs an Enterprise licence key).


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-litellm.json, and with the fewest tokens: https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-litellm.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "cloudflare-ai-gateway", "b": "litellm"}`. From a terminal: `anchor compare cloudflare-ai-gateway litellm`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/cloudflare-ai-gateway.json and https://www.anchorterminal.com/api/v1/tools/litellm.json

## Other comparisons with Cloudflare AI Gateway or LiteLLM

- [Amazon Bedrock vs Cloudflare AI Gateway](https://www.anchorterminal.com/compare/amazon-bedrock-vs-cloudflare-ai-gateway.md)
- [Claude API vs Cloudflare AI Gateway](https://www.anchorterminal.com/compare/anthropic-api-vs-cloudflare-ai-gateway.md)
- [Azure OpenAI in Foundry Models vs Cloudflare AI Gateway](https://www.anchorterminal.com/compare/azure-openai-vs-cloudflare-ai-gateway.md)
- [BlockRun.AI vs Cloudflare AI Gateway](https://www.anchorterminal.com/compare/blockrun-ai-vs-cloudflare-ai-gateway.md)
- [Cerebras Inference vs Cloudflare AI Gateway](https://www.anchorterminal.com/compare/cerebras-inference-vs-cloudflare-ai-gateway.md)
- [Cloudflare AI Gateway vs Cloudflare Workers AI](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-cloudflare-workers-ai.md)
- [Cloudflare AI Gateway vs Cohere Chat API (Command models)](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-cohere-chat.md)
- [Cloudflare AI Gateway vs DeepInfra](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-deepinfra.md)
- [Cloudflare AI Gateway vs DeepSeek API](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-deepseek-api.md)
- [Cloudflare AI Gateway vs Eden AI](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-eden-ai.md)
- [Cloudflare AI Gateway vs Glimpse](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-elorian-glimpse.md)
- [Cloudflare AI Gateway vs Fireworks AI Inference](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-fireworks-inference.md)
- [Cloudflare AI Gateway vs Gemini Developer API](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-gemini-api.md)
- [Cloudflare AI Gateway vs GroqCloud](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-groq.md)
- [Cloudflare AI Gateway vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-hugging-face-inference-providers.md)
- [Cloudflare AI Gateway vs Inkling 2 Small](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-inkling-2-small.md)
- [Cloudflare AI Gateway vs Jais 3](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-jais-3.md)
- [Cloudflare AI Gateway vs Meta Model API](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-meta-model-api.md)
- [Cloudflare AI Gateway vs MiniMax API](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-minimax-api.md)
- [Cloudflare AI Gateway vs Mistral AI API](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-mistral-api.md)
- [Cloudflare AI Gateway vs Muse Spark Open](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-muse-spark-open.md)
- [Cloudflare AI Gateway vs Nemotron 3.5 Super VL](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-nemotron-3-5-super-vl.md)
- [Cloudflare AI Gateway vs Novita AI](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-novita-ai.md)
- [Cloudflare AI Gateway vs OpenAI API](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-openai-api.md)
- [Cloudflare AI Gateway vs OpenRouter](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-openrouter.md)
- [Cloudflare AI Gateway vs Prism Inference](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-prism-inference.md)
- [Cloudflare AI Gateway vs Router.com (Ramp Router)](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-ramp-router.md)
- [Cloudflare AI Gateway vs Beam 1.0](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-reflection-beam.md)
- [Cloudflare AI Gateway vs RouterPlus](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-routerplus.md)
- [Cloudflare AI Gateway vs SambaCloud](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-sambanova.md)
- [Cloudflare AI Gateway vs SiliconFlow](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-siliconflow.md)
- [Cloudflare AI Gateway vs Simplismart](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-simplismart.md)
- [Cloudflare AI Gateway vs StepFun API](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-stepfun-api.md)
- [Cloudflare AI Gateway vs SWE-2 Flash](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-swe-2-flash.md)
- [Cloudflare AI Gateway vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-tencent-tokenhub.md)
- [Cloudflare AI Gateway vs Together AI Inference](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-together-inference.md)
- [Cloudflare AI Gateway vs Vercel AI Gateway](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-vercel-ai-gateway.md)
- [Cloudflare AI Gateway vs Vertex AI (Gemini Enterprise Agent Platform)](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-vertex-ai.md)
- [Cloudflare AI Gateway vs xAI API (Grok)](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-xai-api.md)
- [Antseed vs Cloudflare AI Gateway](https://www.anchorterminal.com/compare/antseed-vs-cloudflare-ai-gateway.md)
- [Antseed vs LiteLLM](https://www.anchorterminal.com/compare/antseed-vs-litellm.md)
- [Eden AI vs LiteLLM](https://www.anchorterminal.com/compare/eden-ai-vs-litellm.md)
- [Hugging Face Inference Providers vs LiteLLM](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-litellm.md)
- [LiteLLM vs OpenRouter](https://www.anchorterminal.com/compare/litellm-vs-openrouter.md)
- [LiteLLM vs Router.com (Ramp Router)](https://www.anchorterminal.com/compare/litellm-vs-ramp-router.md)
- [LiteLLM vs RouterPlus](https://www.anchorterminal.com/compare/litellm-vs-routerplus.md)
- [LiteLLM vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/litellm-vs-tencent-tokenhub.md)
- [LiteLLM vs Vercel AI Gateway](https://www.anchorterminal.com/compare/litellm-vs-vercel-ai-gateway.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp