Cloudflare AI Gateway vs Kong AI Gateway

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Kong AI Gateway
   Cloudflare AI Gateway~partialprobed5/10

   Cloudflare's developer docs (which cover AI Gateway) expose a working llms.txt at developers.cloudflare.com/llms.txt, letting an agent discover agent-oriented documentation; an OpenAPI spec is also available. However, the AI Gateway-specific docs page itself returns 404 for the .md variant, so agent-native markdown access is inconsistent at the product-specific level. Missing for 10: a dedicated llms.txt or .md endpoint scoped to AI Gateway docs specifically, and confirmation the top-level llms.txt indexes AI Gateway pages.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.cloudflare.com/llms.txt # Cloudflare Developer Documentation Explore guides and tutorials to…”
   • [probe] “PROBE docs-md: HTTP 404 at https://developers.cloudflare.com/ai-gateway/.md”
   • [probe] “PROBE openapi: HTTP 200 at https://developers.cloudflare.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   Kong AI Gateway✓fullprobed8/10

   A probe confirms developer.konghq.com/llms.txt returns HTTP 200 with a valid llms.txt manifest listing Kong's docs (including AI Gateway), and individual doc pages are also served as .md files (e.g. ai-providers.md, a2a.md), making the docs directly agent-consumable. missing for 10: no explicit vendor statement instructing agents to use llms.txt, and the generic /.md probe for the ai-gateway index returned 404, showing coverage is per-page rather than fully uniform.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.konghq.com/llms.txt # developer.konghq.com > Kong's developer documentation for Kong Gateway,…”
   • [claimed-docs] “The core of AI Gateway is the ability to serve AI Models from various AI Model Providers via a provider-agnostic API.”
   • [probe] “PROBE docs-md: HTTP 404 at https://developer.konghq.com/ai-gateway/.md”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round drawn
   Cloudflare AI Gateway~partialclaimed6/10

   AI Gateway is API/header-driven by design (OpenAI-compatible endpoint, JSON-based dynamic routing config, header-based controls like cf-aig-cache-status and cf-aig-collect-log), which naturally supports headless/programmatic use in scripts or CI pipelines. However, there is no explicit documentation of CI/CD integration, automation examples, or a CLI for pipeline use. Missing for 10: explicit CI/CD workflow examples, dedicated CLI/SDK for automation, documented non-interactive auth/setup flow for pipelines.

   • [claimed-docs] “Cloudflare's AI Gateway offers an OpenAI-compatible `/chat/completions` endpoint, enabling integration with multiple AI providers using a si…”
   • [claimed-docs] “Dynamic routing enables you to create request routing flows through a **visual interface** or a **JSON-based configuration**.”
   • [claimed-docs] “Switch providers by changing the \`model\` and \`apiKey\` parameters.”
   • [claimed-docs] “The \`cf-aig-collect-log\` header allows you to bypass the default log setting for the gateway.”
   • [claimed-docs] “To check whether a response comes from cache or not, **cf-aig-cache-status** will be designated as `HIT` or `MISS`.”

   proof ↗⚑ flag

   Kong AI Gateway~partialprobed6/10

   Kong AI Gateway exposes a CLI (kongctl) and Konnect APIs (list-ai-gateways, config conversion) plus a quickstart script, implying it can be driven headlessly and scripted rather than only via UI. However there is no explicit CI or CD pipeline example, declarative config-as-code workflow, or GitOps documentation demonstrating automated headless operation in CI. Missing for 10: explicit CI or CD pipeline documentation, dedicated headless-mode guide, independent CI usage report.

   • [claimed-docs] “list-ai-gateways summary: List AI Gateways description: Returns a list of AI Gateways in the organization.”
   • [claimed-docs] “walks you through migrating an existing configuration using the kongctl AI Gateway conversion extension”
   • [claimed-docs] “You can use the quickstart script to get a demo instance of AI Gateway running almost instantly.”
   • [probe] “official CLI documented at https://developer.konghq.com/kongctl/”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Kong AI Gateway
   Cloudflare AI Gateway—none0/10

   Cloudflare AI Gateway is a proxy/gateway for routing and observing LLM API calls; the evidence pack contains no mention of an MCP server, MCP protocol, or agent connectivity via MCP. This is an applicable axis (a gateway product could plausibly ship an MCP server for agentic access) but no evidence supports it.

   ⚑ flag

   Kong AI Gateway✓fullclaimed8/10

   Kong AI Gateway ships an official 'AI MCP Server' entity and 'AI MCP Proxy' that converts REST APIs into MCP tools or fronts upstream MCP servers, letting agents connect via a first-party MCP interface, plus governance of MCP traffic (auth, OTel metrics, rate limiting) alongside it. Missing for 10: independent/hands-on verification of an agent successfully connecting through the MCP server and no example configuration walkthrough shown in the pack.

   • [claimed-docs] “AI MCP Proxy bridges Kong-managed Services to the Model Context Protocol, converting REST APIs into MCP tools or fronting upstream MCP serve…”
   • [claimed-docs] “Turn any API into an MCP server using the AI MCP Server entity. This approach does not require an LLM and provides full control over product…”
   • [claimed-docs] “Govern LLM, MCP, and agent-to-agent (A2A) traffic with the same Kong AI Gateway.”
   • [claimed-docs] “AI Gateway can export OpenTelemetry (OTLP) metrics for generative AI, MCP, and A2A traffic through an OpenTelemetry AI Policy.”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Kong AI Gateway
   Cloudflare AI Gateway—none0/10

   No evidence in the pack mentions an official CLI for AI Gateway (e.g., Wrangler or a dedicated AI Gateway CLI); all evidence covers dashboard, API headers, and configuration features. missing for 10: any mention of a CLI tool, command-line usage, or CLI-based configuration for AI Gateway.

   ⚑ flag

   Kong AI Gateway✓fullprobed7/10

   Kong ships an official CLI, kongctl, documented at a dedicated docs URL and explicitly used for AI Gateway tasks (e.g., the 'kongctl AI Gateway conversion extension' for migrating configurations). This confirms a real, first-party CLI exists for AI Gateway workflows. Missing for 10: deeper documentation of kongctl's full command surface for AI-native tasks (agents, MCP, A2A) and independent/hands-on corroboration beyond the docs probe.

   • [claimed-docs] “walks you through migrating an existing configuration using the kongctl AI Gateway conversion extension”
   • [probe] “official CLI documented at https://developer.konghq.com/kongctl/”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Cloudflare AI Gateway
   Cloudflare AI Gateway✓fullprobed7/10

   Cloudflare AI Gateway exposes a documented public API surface: an OpenAI-compatible /chat/completions endpoint, native provider passthroughs, a Universal endpoint for fallbacks, control headers (cf-aig-*), and a patchLog method for feedback/metadata, all described in first-party docs, and Cloudflare's platform-wide openapi.json confirms a machine-readable API schema exists. missing for 10: independent/hands-on third-party corroboration of API usage and a dedicated AI-Gateway-specific OpenAPI reference beyond the platform-wide one.

   • [claimed-docs] “Cloudflare's AI Gateway offers an OpenAI-compatible `/chat/completions` endpoint, enabling integration with multiple AI providers using a si…”
   • [claimed-docs] “Switch providers by changing the \`model\` and \`apiKey\` parameters.”
   • [claimed-docs] “Connect to AI providers using their native API formats through AI Gateway.”
   • [claimed-docs] “Manage all your costs with one simple bill and access every provider through a single API.”
   • [claimed-docs] “The patchLog method allows you to send feedback, score, and metadata for a specific log ID.”
   • [probe] “PROBE openapi: HTTP 200 at https://developers.cloudflare.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   Kong AI Gateway~partialprobed6/10

   Kong documents a Konnect API for managing AI Gateway resources (e.g., list-ai-gateways endpoint) and a dedicated kongctl CLI, showing programmatic control exists and is documented. However, probes for a discoverable OpenAPI/swagger spec at standard locations all returned 404, so the breadth/openness of the API surface is not independently confirmed. Missing for 10: a publicly discoverable OpenAPI/swagger spec, broader endpoint coverage beyond the single example, and independent/hands-on confirmation of API usage.

   • [claimed-docs] “list-ai-gateways summary: List AI Gateways description: Returns a list of AI Gateways in the organization.”
   • [probe] “official CLI documented at https://developer.konghq.com/kongctl/”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.konghq.com/openapi.json, https://developer.konghq.com/swagger.json, https://develo…”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Kong AI Gateway
   Cloudflare AI Gateway—none0/10

   The evidence pack covers AI Gateway's routing, caching, rate limiting, logging, and fallback features, but there is no mention of issuing scoped or least-privilege API credentials/tokens for agents (e.g., per-agent API keys with restricted permissions). Rate limiting and per-user/project quotas are traffic controls, not credential scoping mechanisms.

   ⚑ flag

   Kong AI Gateway~partialclaimed5/10

   Kong AI Gateway provides building blocks relevant to credential control for agents — AI Auth Strategy entities can authenticate via enterprise IdPs (Okta/Azure AD/OIDC) 'without managing keys manually,' and AI Vault lets model providers, auth strategies, agents, and MCP servers reference secrets from external backends instead of storing literal keys, plus Azure Managed Identity support for scoped cloud authentication. However, none of this evidence explicitly describes issuing scoped/least-privilege credentials per agent (e.g., fine-grained permission scopes, per-agent token minting) — it's centralized secret referencing and IdP auth rather than a dedicated least-privilege credential-issuance mechanism. missing for 10: explicit documentation of scoped/least-privilege credential issuance per agent, granular permission/scope controls tied to individual agent identities, and independent/hands-on verification of this behavior.

   • [claimed-docs] “An AI Vault entity lets you register an external secret backend (AWS Secrets Manager, HashiCorp Vault, environment variables, or others) so …”
   • [claimed-docs] “Authenticate enterprise users through an existing identity provider (Okta, Azure AD, Google, or any OIDC-compliant IdP) without managing key…”
   • [claimed-docs] “Yes, if AI Gateway is running on Azure, you can configure an AI Model Provider to detect the designated Managed Identity or User-Assigned Id…”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Cloudflare AI Gateway
   Cloudflare AI Gateway~partialclaimed5/10

   AI Gateway is compatible with OpenAI-style SDKs and providers' native APIs (via the OpenAI-compatible /chat/completions endpoint and native API pass-through), and Workers AI bindings imply SDK-like integration, but the evidence pack never explicitly names or documents an official Cloudflare AI Gateway SDK for major languages (e.g., a dedicated 'cloudflare-ai-gateway' npm/python package) with API references. missing for 10: explicit official SDK documentation/package listing, multi-language SDK examples, independent confirmation of SDK reliability/maintenance.

   • [claimed-docs] “Cloudflare's AI Gateway offers an OpenAI-compatible `/chat/completions` endpoint, enabling integration with multiple AI providers using a si…”
   • [claimed-docs] “Switch providers by changing the \`model\` and \`apiKey\` parameters.”
   • [claimed-docs] “Connect to AI providers using their native API formats through AI Gateway.”
   • [claimed-docs] “This feature simplifies the integration process, allowing for seamless switching between different models without significant code modificat…”
   • [claimed-docs] “gateway: { id: "my-gateway", },”

   proof ↗⚑ flag

   Kong AI Gateway—none0/10

   The evidence pack contains no mention of official SDKs for building against Kong AI Gateway (only a CLI 'kongctl' and REST API references), and probes explicitly show no OpenAPI/SDK artifacts (404s for openapi.json, swagger.json, etc.). While an API gateway could plausibly offer official client SDKs, none are documented here.

   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.konghq.com/openapi.json, https://developer.konghq.com/swagger.json, https://develo…”
   • [probe] “official CLI documented at https://developer.konghq.com/kongctl/”
   • [claimed-docs] “list-ai-gateways summary: List AI Gateways description: Returns a list of AI Gateways in the organization.”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Cloudflare AI Gateway—none0/10

   Evidence shows only static documentation pages with code snippets and an openapi.json file, but no interactive API reference, playground, or runnable-example explorer is described anywhere in the pack.

   • [probe] “PROBE openapi: HTTP 200 at https://developers.cloudflare.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “Better yet - it only takes one line of code to get started.”
   • [claimed-docs] “This feature simplifies the integration process, allowing for seamless switching between different models without significant code modificat…”

   proof ↗⚑ flag

   Kong AI Gateway—none0/10

   Evidence shows Kong publishes API reference content (e.g., list-ai-gateways endpoint docs) but there is no indication of an interactive reference with runnable/try-it-out examples; probes for OpenAPI/swagger specs on the docs site all returned 404, suggesting no such interactive tooling is exposed.

   • [claimed-docs] “list-ai-gateways summary: List AI Gateways description: Returns a list of AI Gateways in the organization.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.konghq.com/openapi.json, https://developer.konghq.com/swagger.json, https://develo…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Cloudflare AI Gateway
   Cloudflare AI Gateway✓fullprobed8/10

   Cloudflare publishes a machine-readable OpenAPI spec at a public, verifiable endpoint (openapi.json containing an 'openapi' key), covering the Cloudflare API including AI Gateway configuration/management endpoints, plus an llms.txt for AI-native discovery. missing for 10: no dedicated AI-Gateway-specific OpenAPI file (it's part of the broader Cloudflare API spec) and no independent/community confirmation of completeness.

   • [probe] “PROBE openapi: HTTP 200 at https://developers.cloudflare.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.cloudflare.com/llms.txt # Cloudflare Developer Documentation Explore guides and tutorials to…”

   proof ↗⚑ flag

   Kong AI Gateway—none0/10

   Evidence includes API reference pages (e.g. Konnect AI Gateway API docs) but no downloadable OpenAPI/Swagger spec file is evidenced; a direct probe for standard OpenAPI/swagger.json locations returned 404 at all candidate paths, indicating no machine-readable spec is exposed there.

   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.konghq.com/openapi.json, https://developer.konghq.com/swagger.json, https://develo…”
   • [claimed-docs] “list-ai-gateways summary: List AI Gateways description: Returns a list of AI Gateways in the organization.”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round drawn
   Cloudflare AI Gateway—none0/10

   No evidence of a sandbox/test environment feature separate from production; AI Gateway docs focus on routing, caching, rate limiting, logging, and fallbacks, with no mention of a sandbox mode or test-data isolation from production.

   ⚑ flag

   Kong AI Gateway—none0/10

   The evidence pack only shows a quickstart script for spinning up a demo instance and general AI Gateway features (proxying, observability, policies) but no dedicated sandbox/staging environment or test-mode capability that isolates from production data. No mention of environment separation, mock upstreams, or a documented sandbox mode.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Cloudflare AI Gateway—none0/10

   Evidence covers AI Gateway's features (caching, rate limiting, fallbacks, logging) but nowhere mentions API versioning schemes or a documented deprecation policy for the AI Gateway API itself; the openapi.json probe confirms an API spec exists but says nothing about version lifecycle or deprecation commitments. Missing for 10: explicit versioning scheme documentation, deprecation policy/timeline, changelog or migration guides for breaking changes.

   • [probe] “PROBE openapi: HTTP 200 at https://developers.cloudflare.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   Kong AI Gateway—none0/10

   The evidence shows an API reference exists (e.g., 'v1' Konnect AI Gateway API) but there is no documentation of a versioning scheme or deprecation policy for the AI Gateway APIs, and OpenAPI spec probes returned 404s.

   • [claimed-docs] “list-ai-gateways summary: List AI Gateways description: Returns a list of AI Gateways in the organization.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.konghq.com/openapi.json, https://developer.konghq.com/swagger.json, https://develo…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Cloudflare AI Gateway—none0/10

   The evidence pack covers per-request features (rate limiting, caching, fallbacks, logging, dynamic routing) but contains no mention of bulk or batch operations across multiple items (e.g., batch API calls, bulk config management, or multi-item processing).

   ⚑ flag

   Kong AI Gateway—none0/10

   The evidence covers proxying, observability, security, and MCP/A2A support but never describes any bulk or batch operation capability (e.g., batch creating/updating routes, plugins, or AI entities across many items at once). The kongctl CLI and Konnect API are mentioned but only for single-entity or config migration tasks, not bulk item processing.

   • [claimed-docs] “list-ai-gateways summary: List AI Gateways description: Returns a list of AI Gateways in the organization.”
   • [claimed-docs] “walks you through migrating an existing configuration using the kongctl AI Gateway conversion extension”
   • [probe] “official CLI documented at https://developer.konghq.com/kongctl/”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Cloudflare AI Gateway
   Cloudflare AI Gateway~partialclaimed6/10

   AI Gateway supports rule-based automation like dynamic routing that evaluates conditions and triggers fallback/model-switching actions, rate limiting, and cache overrides via headers, which are event-triggered automated behaviors. However, this is narrowly scoped to request routing/traffic control rather than a general-purpose 'define custom rules that trigger arbitrary actions on events' system (e.g., no evidence of user-defined triggers for alerts, webhooks, or custom workflows beyond routing/fallback/caching/rate-limits). missing for 10: evidence of arbitrary custom event-action rule definitions (e.g., webhook/alert triggers on thresholds), independent/hands-on corroboration of dynamic routing behavior, and confirmation of a general automation/rules engine beyond routing, caching, and rate limiting.

   • [claimed-docs] “Dynamic routing enables you to create request routing flows through a **visual interface** or a **JSON-based configuration**.”
   • [claimed-docs] “Directing different segments (paid/not-paid user) to different models”
   • [claimed-docs] “Restricting each user/project/team with budget/rate limits”
   • [claimed-docs] “you compose a small flow that evaluates conditions, enforces quotas, and chooses models with fallbacks. You can iterate without touching app…”
   • [claimed-docs] “Improve resilience by defining request retry and model fallbacks in case of an error.”
   • [claimed-docs] “Sends a request to Workers AI Inference API. 2. If that request fails, proceeds to OpenAI.”
   • [claimed-docs] “Cloudflare can trigger your fallback provider in response to request errors or predetermined request timeouts.”
   • [claimed-docs] “Rate limiting controls the traffic that reaches your application, which prevents expensive bills and suspicious activity.”
   • [claimed-docs] “You can define rate limits as the number of requests that get sent in a specific time frame. For example, you can limit your application to …”

   proof ↗⚑ flag

   Kong AI Gateway~partialclaimed5/10

   Kong AI Gateway supports policy-based automatic actions triggered by request/response events—e.g., Prompt Guards and content-safety policies acting on chat/completion requests, AI Rate Limiting Advanced enforcing limits automatically, AWS Guardrails validating requests/responses before forwarding, and semantic caching/routing acting on similarity triggers—which functions as rule-based automation on traffic events. However, this is scoped to gateway traffic policies rather than a general-purpose event/trigger automation framework for arbitrary conditions and actions. Missing for 10: evidence of a generic conditional rule engine (if-this-then-that style), user-defined custom triggers beyond built-in policies, and any workflow/orchestration automation beyond request-level policy enforcement.

   • [claimed-docs] “AI Gateway supports content safety features across providers and also includes our Prompt Guards that act on any llm/v1/chat or llm/v1/compl…”
   • [claimed-docs] “AI Rate Limiting Advanced - Plugin | Kong Docs”
   • [claimed-docs] “Apply safety and DLP policies to prevent toxic content and remove personally identifiable information.”
   • [claimed-docs] “AI Gateway can perform intelligent request routing, caching, and content filtering using semantic similarity queries.”
   • [claimed-docs] “Use AWS Guardrails to validate requests and/or responses before forwarding them between clients and upstream LLMs.”

   proof ↗⚑ flag

3. ai-native userVersion, review, and roll back my automations

   weight 1 · round to Cloudflare AI Gateway
   Cloudflare AI Gateway~partialclaimed3/10

   Docs mention that dynamic routing lets you 'publish a new route version' without touching application code, implying some versioning of routing configs, but there is no documented review/diff interface or explicit rollback mechanism for automations. missing for 10: explicit rollback/undo functionality, change-review or diff UI, versioning of prompts/logic beyond routing config.

   • [claimed-docs] “you compose a small flow that evaluates conditions, enforces quotas, and chooses models with fallbacks. You can iterate without touching app…”
   • [claimed-docs] “Dynamic routing enables you to create request routing flows through a **visual interface** or a **JSON-based configuration**.”
   • [claimed-docs] “A/B and gradual rollouts while making it accessible to both developers and non-technical team members.”

   proof ↗⚑ flag

   Kong AI Gateway—none0/10

   The evidence pack covers AI Gateway's traffic proxying, observability, security, and provider-agnostic API features, but contains no mention of versioning, reviewing, or rolling back gateway configurations or 'automations' (e.g., no changelog, approval workflow, or rollback mechanism is documented). The only tangential item is a config migration extension (kongctl conversion tool), which addresses format conversion, not version control or rollback. missing for 10: version history/changelog for AI Gateway configs, review/approval workflow for changes, rollback mechanism for policies or entities.

   • [claimed-docs] “walks you through migrating an existing configuration using the kongctl AI Gateway conversion extension”

   proof ↗⚑ flag

Caching

1. developerCache responses at the gateway to cut cost and latency on repeated requests

   weight 2 · round to Cloudflare AI Gateway
   Cloudflare AI Gateway✓fullclaimed9/10

   Docs clearly describe gateway-level caching that serves responses from Cloudflare's cache instead of calling the model provider (cost/latency savings), with per-request header overrides and a cf-aig-cache-status HIT/MISS indicator for verification. Missing for 10: independent/hands-on benchmark corroborating actual latency/cost savings.

   • [claimed-docs] “Serve requests directly from Cloudflare's cache instead of the original model provider for faster requests and cost savings.”
   • [claimed-docs] “AI Gateway allows you to override default cache behaviors on a per-request basis using specific HTTP headers.”
   • [claimed-docs] “To check whether a response comes from cache or not, **cf-aig-cache-status** will be designated as `HIT` or `MISS`.”

   proof ↗⚑ flag

   Kong AI Gateway✓fullclaimed8/10

   Kong ships a dedicated AI Semantic Cache plugin explicitly designed to cache LLM responses at the gateway, and separate docs confirm gateway-level semantic caching to reduce redundant calls and improve latency/cost. This is first-party documentation with a named product feature, though no independent benchmark or hands-on cost/latency measurement is provided. Missing for 10: independent/hands-on validation of actual cost/latency savings, and exact-match (non-semantic) cache configuration details.

   • [claimed-docs] “AI Semantic Cache - Plugin | Kong Docs”
   • [claimed-docs] “AI Gateway can perform intelligent request routing, caching, and content filtering using semantic similarity queries.”

   proof ↗⚑ flag

Latency

1. platform engineerRun traffic through gateway infrastructure that adds minimal latency overhead to provider calls

   weight 2 · round to Kong AI Gateway
   Cloudflare AI Gateway—none0/10

   The evidence pack documents caching, rate limiting, fallbacks, and analytics features but contains no benchmarks, latency figures, or explicit claims about the gateway's own processing overhead added to provider calls. Caching (docs-4, docs-31) improves speed only for cache hits and says nothing about baseline pass-through latency. Missing for 10: any latency benchmark, p50/p99 overhead numbers, or first-party/independent claim that the proxy adds minimal delay to non-cached requests.

   • [claimed-docs] “Serve requests directly from Cloudflare's cache instead of the original model provider for faster requests and cost savings.”
   • [claimed-docs] “To check whether a response comes from cache or not, **cf-aig-cache-status** will be designated as `HIT` or `MISS`.”

   proof ↗⚑ flag

   Kong AI Gateway~partialclaimed5/10

   Kong documents latency-related tooling (usage analytics and OTel metrics that track LLM request latency and upstream processing time, semantic caching, load balancing across models) which implies attention to performance, but there is no explicit claim or benchmark quantifying the gateway's own added latency overhead as 'minimal'. missing for 10: quantified latency-overhead benchmarks, independent performance tests, explicit vendor claim of low proxy overhead.

   • [claimed-docs] “You can use these metrics to: Track LLM request latency and upstream provider processing time * Monitor token consumption ... * Calculate AI…”
   • [claimed-docs] “AI Semantic Cache - Plugin | Kong Docs”
   • [claimed-docs] “AI Gateway provides load balancing capabilities to distribute requests across multiple LLM models.”
   • [claimed-docs] “See usage analytics for requests, tokens, errors, and latency”

   proof ↗⚑ flag

Agent guardrails

1. ai-native userGive an autonomous agent its own key with budget and rate guardrails so it cannot run away on spend

   weight 2 · round to Kong AI Gateway
   Cloudflare AI Gateway~partialclaimed5/10

   AI Gateway's dynamic routing explicitly supports 'restricting each user/project/team with budget/rate limits' and its rate-limiting feature lets you cap requests per time window (fixed/sliding), which maps to giving an agent bounded spend/rate guardrails when configured as its own route/project. However, the evidence never describes issuing a distinct API key per agent tied to a dollar-denominated budget cap — the mechanism shown is request-count rate limiting plus routing-level quotas, not a native 'agent key + $ budget' guardrail. missing for 10: explicit per-agent key issuance, dollar-based spend caps (not just request counts), and independent confirmation the budget/rate restriction in dynamic routing enforces hard spend caps.

   • [claimed-docs] “Restricting each user/project/team with budget/rate limits”
   • [claimed-docs] “Rate limiting controls the traffic that reaches your application, which prevents expensive bills and suspicious activity.”
   • [claimed-docs] “You can also select if you would like a **fixed** or **sliding** rate limiting technique.”
   • [claimed-docs] “You can define rate limits as the number of requests that get sent in a specific time frame. For example, you can limit your application to …”
   • [claimed-docs] “Control how your application scales by limiting the number of requests your application receives.”
   • [claimed-docs] “Dynamic routing enables you to create request routing flows through a **visual interface** or a **JSON-based configuration**.”
   • [claimed-docs] “you compose a small flow that evaluates conditions, enforces quotas, and chooses models with fallbacks. You can iterate without touching app…”

   proof ↗⚑ flag

   Kong AI Gateway~partialclaimed6/10

   Kong AI Gateway supports per-consumer/agent authentication (AI Auth Strategy, AI Vault for keys) plus AI Rate Limiting Advanced and model cost calculation/tracking that matches provider billing, which together let an operator scope an agent's key and cap its request rate and see accrued spend. However, evidence shows cost *calculation and observability* (docs-9, docs-10, docs-18) rather than an explicit hard budget cap/kill-switch that automatically cuts off an agent once a spend threshold is reached, so the 'cannot run away on spend' guarantee is only partially evidenced. Missing for 10: explicit documented budget-threshold enforcement/auto-cutoff tied to a specific agent key, and a worked example of issuing a scoped key to an autonomous agent with combined rate+spend limits.

   • [claimed-docs] “AI Rate Limiting Advanced - Plugin | Kong Docs”
   • [claimed-docs] “AI Gateway calculates that figure for every request to a large language model (LLM) provider, matching what the provider actually bills.”
   • [claimed-docs] “An AI Vault entity lets you register an external secret backend (AWS Secrets Manager, HashiCorp Vault, environment variables, or others) so …”
   • [claimed-docs] “Authenticate enterprise users through an existing identity provider (Okta, Azure AD, Google, or any OIDC-compliant IdP) without managing key…”
   • [claimed-docs] “You can use these metrics to: Track LLM request latency and upstream provider processing time * Monitor token consumption ... * Calculate AI…”

   proof ↗⚑ flag

Budgets

1. platform engineerSet hard budgets and spend limits per key, team, or user

   weight 3 · round drawn
   Cloudflare AI Gateway~partialclaimed5/10

   AI Gateway supports rate limiting per app/gateway and dynamic routing docs mention 'restricting each user/project/team with budget/rate limits,' but there's no dedicated documentation on setting a hard dollar spend cap or budget limit per API key, team, or user that blocks requests once exceeded — the budget/rate-limit reference is a single bullet without configuration detail. missing for 10: dedicated budget-limit configuration docs (dollar-amount caps), per-key/per-user budget enforcement examples, and evidence of automatic cutoff/alerting when a hard budget is reached.

   • [claimed-docs] “Restricting each user/project/team with budget/rate limits”
   • [claimed-docs] “You can define rate limits as the number of requests that get sent in a specific time frame. For example, you can limit your application to …”
   • [claimed-docs] “Rate limiting controls the traffic that reaches your application, which prevents expensive bills and suspicious activity.”
   • [claimed-docs] “Control how your application scales by limiting the number of requests your application receives.”

   proof ↗⚑ flag

   Kong AI Gateway~partialclaimed5/10

   Kong AI Gateway provides cost calculation, tracking across teams, and rate limiting plugins (AI Rate Limiting Advanced) which can enforce request/token limits per consumer, but evidence shows rate limiting and cost tracking as separate capabilities rather than a unified hard 'budget/spend limit' enforcement tied directly to cost thresholds per key/team/user. missing for 10: explicit documentation of setting a dollar-based spend cap or budget that auto-blocks requests once exceeded, per-key/team/user budget configuration UI or API, and independent confirmation of budget enforcement in production.

   • [claimed-docs] “AI Rate Limiting Advanced - Plugin | Kong Docs”
   • [claimed-docs] “AI Gateway calculates that figure for every request to a large language model (LLM) provider, matching what the provider actually bills.”
   • [claimed-docs] “AI Gateway can proxy requests from AI command-line tools to LLM providers. This gives you centralized control over AI traffic: log all reque…”
   • [claimed-docs] “You can use these metrics to: Track LLM request latency and upstream provider processing time * Monitor token consumption ... * Calculate AI…”

   proof ↗⚑ flag

Spend tracking

1. platform engineerTrack spend per model, key, team, or user across all providers in one place

   weight 3 · round to Kong AI Gateway
   Cloudflare AI Gateway~partialclaimed6/10

   AI Gateway logs per-request cost, tokens, provider, and model, and supports dynamic routing with per-user/project/team budget and rate limits, giving a foundation for spend tracking across providers in one dashboard. However, there is no explicit evidence of built-in aggregated spend dashboards or reports broken down by 'team' or 'user' as first-class filters/rollups, or per-API-key spend attribution beyond raw logs. missing for 10: dedicated cost-aggregation/reporting UI by team/user/key, evidence of budget alerts tied to spend thresholds, independent/hands-on confirmation of cross-provider spend rollups.

   • [claimed-docs] “View metrics such as the number of requests, tokens, and the cost it takes to run your application.”
   • [claimed-docs] “Restricting each user/project/team with budget/rate limits”
   • [claimed-docs] “Your AI Gateway dashboard shows logs of individual requests, including the user prompt, model response, provider, timestamp, request status,…”
   • [claimed-docs] “Manage all your costs with one simple bill and access every provider through a single API.”

   proof ↗⚑ flag

   Kong AI Gateway~partialclaimed7/10

   Kong AI Gateway computes exact per-request LLM costs matching provider billing, logs cost metrics with token/model details, exports cost-related OTel metrics, and documentation explicitly states cost tracking 'across teams'; since all providers route through the same gateway, aggregation across providers is plausible. However, evidence never shows a consolidated dashboard or breakdown specifically by model, API key, or individual user — only 'teams' is explicitly named as a tracked dimension. Missing for 10: explicit per-user and per-API-key cost attribution/dashboard, and a documented single-pane cross-provider spend view (vs. raw logs/metrics that would need external aggregation).

   • [claimed-docs] “AI Gateway calculates that figure for every request to a large language model (LLM) provider, matching what the provider actually bills.”
   • [claimed-docs] “AI Gateway logs capture detailed information about the request and response payloads, token usage, model details, latency, and cost metrics.”
   • [claimed-docs] “You can use these metrics to: Track LLM request latency and upstream provider processing time * Monitor token consumption ... * Calculate AI…”
   • [claimed-docs] “AI Gateway can proxy requests from AI command-line tools to LLM providers. This gives you centralized control over AI traffic: log all reque…”
   • [claimed-docs] “AI Gateway can export OpenTelemetry (OTLP) metrics for generative AI, MCP, and A2A traffic through an OpenTelemetry AI Policy.”

   proof ↗⚑ flag

Byok

1. developerBring my own provider API keys and have the gateway use them for my traffic

   weight 2 · round to Cloudflare AI Gateway
   Cloudflare AI Gateway✓fullclaimed8/10

   Docs confirm AI Gateway proxies requests to providers using the developer's own API key (e.g. 'Switch providers by changing the model and apiKey parameters' and passthrough pricing with no markup, meaning the developer's own provider account/key is billed directly), and it connects to native provider APIs and OpenAI-compatible endpoints for many providers. missing for 10: no explicit first-party doc section titled 'bring your own key' explaining storage/security of BYO keys, and no independent/hands-on confirmation of this exact flow.

   • [claimed-docs] “Switch providers by changing the \`model\` and \`apiKey\` parameters.”
   • [claimed-docs] “Connect to AI providers using their native API formats through AI Gateway.”
   • [claimed-docs] “Inference pricing from providers is passed through with no markup — you pay the same per-token rates as you would directly with the provider…”
   • [claimed-docs] “Workers AI, Anthropic, Google Gemini, OpenAI, Replicate, and more work with AI Gateway.”
   • [claimed-docs] “Cloudflare's AI Gateway offers an OpenAI-compatible `/chat/completions` endpoint, enabling integration with multiple AI providers using a si…”

   proof ↗⚑ flag

   Kong AI Gateway~partialclaimed6/10

   Docs show AI Model Providers are configured with credentials, and an AI Vault entity lets AI Model Providers reference externally-stored secrets (AWS Secrets Manager, HashiCorp Vault, env vars) rather than storing keys as literal values, and Azure-specific managed identity auth is also supported — implying developers can supply and manage their own provider keys/secrets. However, no explicit doc snippet shows the exact 'paste your own API key per provider' config example or per-request key override behavior. Missing for 10: an explicit example of configuring a provider with a literal/bring-your-own API key, and confirmation of per-consumer or per-request key overrides.

   • [claimed-docs] “The core of AI Gateway is the ability to serve AI Models from various AI Model Providers via a provider-agnostic API.”
   • [claimed-docs] “Yes, if AI Gateway is running on Azure, you can configure an AI Model Provider to detect the designated Managed Identity or User-Assigned Id…”
   • [claimed-docs] “An AI Vault entity lets you register an external secret backend (AWS Secrets Manager, HashiCorp Vault, environment variables, or others) so …”
   • [claimed-docs] “Authenticate enterprise users through an existing identity provider (Okta, Azure AD, Google, or any OIDC-compliant IdP) without managing key…”

   proof ↗⚑ flag

Programmatic admin

1. ai-native userProvision gateways, keys, and budgets programmatically through an admin API

   weight 3 · round to Kong AI Gateway
   Cloudflare AI Gateway~partialprobed4/10

   Docs show gateways can be identified/configured programmatically (e.g., gateway id in code) and budgets/rate limits can be set via JSON-based dynamic routing config, suggesting some programmatic provisioning, and Cloudflare's general openapi.json exists. However there is no explicit documentation of an admin API for creating gateways, issuing/rotating API keys, or setting budgets outside the dashboard/JSON routing config. Missing for 10: explicit AI Gateway REST/GraphQL API endpoints for gateway CRUD, key provisioning, and budget management with request/response examples.

   • [claimed-docs] “Restricting each user/project/team with budget/rate limits”
   • [claimed-docs] “you compose a small flow that evaluates conditions, enforces quotas, and chooses models with fallbacks. You can iterate without touching app…”
   • [claimed-docs] “gateway: { id: "my-gateway", },”
   • [probe] “PROBE openapi: HTTP 200 at https://developers.cloudflare.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   Kong AI Gateway~partialclaimed5/10

   Kong exposes a Konnect API for listing/managing AI Gateways (list-ai-gateways) and entity-based configuration (AI Auth Strategy, AI Vault) that implies programmatic provisioning of gateways and credentials, plus a kongctl CLI for gateway configuration/migration. However, there is no explicit documentation of an API or CLI for creating/managing spend budgets or quotas, and no end-to-end example of provisioning gateway+keys+budget via API. Missing for 10: explicit budget/quota provisioning API, a full API reference for creating AI Auth Strategies/keys programmatically, and independent confirmation of the admin API's completeness for this workflow.

   • [claimed-docs] “list-ai-gateways summary: List AI Gateways description: Returns a list of AI Gateways in the organization.”
   • [claimed-docs] “An AI Vault entity lets you register an external secret backend (AWS Secrets Manager, HashiCorp Vault, environment variables, or others) so …”
   • [claimed-docs] “Authenticate enterprise users through an existing identity provider (Okta, Azure AD, Google, or any OIDC-compliant IdP) without managing key…”
   • [claimed-docs] “walks you through migrating an existing configuration using the kongctl AI Gateway conversion extension”
   • [claimed-docs] “AI Gateway calculates that figure for every request to a large language model (LLM) provider, matching what the provider actually bills.”

   proof ↗⚑ flag

Virtual keys

1. platform engineerMint gateway-managed keys for teams and apps without exposing raw provider keys

   weight 3 · round to Kong AI Gateway
   Cloudflare AI Gateway—none0/10

   The evidence covers rate limiting, dynamic routing, fallbacks, caching, and logging, but nowhere describes a mechanism for minting gateway-managed keys that abstract or hide raw provider API keys for teams/apps.

   ⚑ flag

   Kong AI Gateway~partialclaimed6/10

   Kong AI Gateway's AI Vault lets provider keys be stored in external secret backends and referenced by AI Model Providers/Agents instead of literal values, and AI Auth Strategy lets client apps authenticate via an IdP or Kong-managed auth without handling provider keys directly — both point toward the platform-engineer being able to shield raw provider keys from consumers. However, the evidence never explicitly describes a workflow for minting distinct gateway-managed keys per team/app, rotating them, or a consumer/key-auth flow tied to AI traffic. Missing for 10: explicit documentation of issuing/rotating per-team or per-app gateway-managed API keys, and any admin UI/API walkthrough for that key-minting process.

   • [claimed-docs] “An AI Vault entity lets you register an external secret backend (AWS Secrets Manager, HashiCorp Vault, environment variables, or others) so …”
   • [claimed-docs] “Authenticate enterprise users through an existing identity provider (Okta, Azure AD, Google, or any OIDC-compliant IdP) without managing key…”
   • [claimed-docs] “Reference an AI Auth Strategy on your AI Agent entities to authenticate A2A clients, and attach the Request Size Limiting Policy to limit re…”

   proof ↗⚑ flag

Integrations

1. developerExport gateway logs and traces to my own observability stack

   weight 1 · round to Kong AI Gateway
   Cloudflare AI Gateway—none0/10

   Evidence describes Cloudflare's own dashboard logging, metrics, and header-based controls for log collection (e.g., cf-aig-collect-log, patchLog), but there is no mention of exporting logs/traces to an external observability stack (e.g., via Logpush, webhook, or third-party integration).

   ⚑ flag

   Kong AI Gateway✓fullclaimed8/10

   Kong AI Gateway documents exporting OpenTelemetry (OTLP) metrics for generative AI, MCP, and A2A traffic via an OpenTelemetry AI Policy, plus detailed audit logs capturing request/response payloads, token usage, latency, and cost — enabling integration with a developer's own observability stack. Missing for 10: explicit trace export (spans/tracing) documentation and independent/hands-on confirmation of exporting to third-party backends like Datadog or Grafana.

   • [claimed-docs] “AI Gateway can export OpenTelemetry (OTLP) metrics for generative AI, MCP, and A2A traffic through an OpenTelemetry AI Policy.”
   • [claimed-docs] “You can use these metrics to: Track LLM request latency and upstream provider processing time * Monitor token consumption ... * Calculate AI…”
   • [claimed-docs] “AI Gateway logs capture detailed information about the request and response payloads, token usage, model details, latency, and cost metrics.”

   proof ↗⚑ flag

Logs

1. platform engineerInspect logged requests and responses with latency, token counts, and cost attached

   weight 3 · round to Cloudflare AI Gateway
   Cloudflare AI Gateway✓fullclaimed9/10

   Docs explicitly state the dashboard shows per-request logs including user prompt, model response, provider, timestamp, status, token usage, cost, duration, and user agent, plus aggregate metrics for requests/tokens/cost. This directly matches the story's requirement to inspect logged requests/responses with latency, token counts, and cost. Missing for 10: independent/hands-on corroboration beyond first-party docs.

   • [claimed-docs] “Your AI Gateway dashboard shows logs of individual requests, including the user prompt, model response, provider, timestamp, request status,…”
   • [claimed-docs] “View metrics such as the number of requests, tokens, and the cost it takes to run your application.”
   • [claimed-docs] “Create comprehensive monitoring and alerting systems using AI Gateway's rich logging and metrics data.”

   proof ↗⚑ flag

   Kong AI Gateway✓fullclaimed8/10

   Kong AI Gateway docs explicitly describe audit logs capturing request/response payloads, token usage, model details, latency, and cost metrics, plus usage analytics dashboards and OTel metrics for latency, tokens, and cost. missing for 10: independent/hands-on corroboration of the logging UI in practice and detail on log retention/query interface.

   • [claimed-docs] “See usage analytics for requests, tokens, errors, and latency”
   • [claimed-docs] “You can use these metrics to: Track LLM request latency and upstream provider processing time * Monitor token consumption ... * Calculate AI…”
   • [claimed-docs] “AI Gateway logs capture detailed information about the request and response payloads, token usage, model details, latency, and cost metrics.”
   • [claimed-docs] “AI Gateway calculates that figure for every request to a large language model (LLM) provider, matching what the provider actually bills.”
   • [claimed-docs] “AI Gateway can export OpenTelemetry (OTLP) metrics for generative AI, MCP, and A2A traffic through an OpenTelemetry AI Policy.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Cloudflare AI Gateway
   Cloudflare AI Gateway~partialprobed6/10

   AI Gateway configuration such as caching, rate limiting, fallbacks, and dynamic routing can be set via headers, API/JSON config, and the OpenAI-compatible endpoint, and an OpenAPI spec exists confirming broad API coverage. However, some features like dynamic routing are explicitly described as configurable via a 'visual interface' as an alternative to JSON, and there's no explicit confirmation that every dashboard capability (e.g., A/B rollouts, log feedback via patchLog, full analytics views) is fully API-exposed with parity to the UI. missing for 10: explicit statement of full UI/API parity, evidence that dashboard-only features (analytics visualizations, visual routing builder) have equivalent API endpoints, independent confirmation of complete parity.

   • [claimed-docs] “Dynamic routing enables you to create request routing flows through a **visual interface** or a **JSON-based configuration**.”
   • [claimed-docs] “Cloudflare's AI Gateway offers an OpenAI-compatible `/chat/completions` endpoint, enabling integration with multiple AI providers using a si…”
   • [claimed-docs] “AI Gateway allows you to override default cache behaviors on a per-request basis using specific HTTP headers.”
   • [claimed-docs] “The \`cf-aig-collect-log\` header allows you to bypass the default log setting for the gateway.”
   • [claimed-docs] “The patchLog method allows you to send feedback, score, and metadata for a specific log ID.”
   • [probe] “PROBE openapi: HTTP 200 at https://developers.cloudflare.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   Kong AI Gateway~partialprobed5/10

   Kong exposes AI Gateway configuration via the Konnect API (e.g. list-ai-gateways endpoint) and the kongctl CLI, and docs explicitly note that 'the same capabilities' configurable via plugins can be set on Services/Routes rather than only the UI, implying strong API-driven configuration. However there is no explicit statement of full UI/API parity, and probes for a discoverable OpenAPI spec returned 404s, leaving completeness unverified. Missing for 10: an explicit parity statement or comprehensive OpenAPI spec confirming every UI action (e.g. dashboards, analytics views) is also API-accessible, and independent confirmation of no UI-only features.

   • [claimed-docs] “list-ai-gateways summary: List AI Gateways description: Returns a list of AI Gateways in the organization.”
   • [claimed-docs] “This page shows you how to configure the same capabilities with AI plugins on Services and Routes.”
   • [probe] “official CLI documented at https://developer.konghq.com/kongctl/”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.konghq.com/openapi.json, https://developer.konghq.com/swagger.json, https://develo…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Cloudflare AI Gateway—none0/10

   Evidence pack covers logging, caching, fallback, rate-limiting, and routing features, but nowhere mentions a data export capability or open-format export/data portability for users leaving the platform. No documentation of bulk export, data download, or migration tooling is present.

   ⚑ flag

   Kong AI Gateway—none0/10

   Kong AI Gateway/Konnect is a SaaS-hosted control plane with configuration, logs, and analytics data, so data portability/export-and-leave is a fair axis to ask, but the evidence pack contains no mention of a bulk data export feature, open-format export of configs/logs/analytics, or a documented migration-out path in open standards. Evidence only covers observability (metrics, logs) and a CLI conversion extension for migrating configs between versions, not exporting all user data to leave the platform.

   • [claimed-docs] “walks you through migrating an existing configuration using the kongctl AI Gateway conversion extension”
   • [claimed-docs] “You can use these metrics to: Track LLM request latency and upstream provider processing time * Monitor token consumption ... * Calculate AI…”
   • [claimed-docs] “AI Gateway logs capture detailed information about the request and response payloads, token usage, model details, latency, and cost metrics.”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Cloudflare AI Gateway—none0/10

   Cloudflare AI Gateway is a closed, proprietary hosted service; the evidence pack contains only documentation and probes, with no mention of an open-source license or public source repository for the product itself.

   ⚑ flag

   Kong AI Gateway—none0/10

   Kong AI Gateway is a commercial/enterprise product built on Kong Gateway; the evidence pack contains only product documentation, API references, and probes for docs/CLI—no mention of source code availability or an open-source license for AI Gateway itself. Kong Gateway OSS is a separate product; nothing here confirms AI Gateway's source is published under an open license.

   ⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Kong AI Gateway
   Cloudflare AI Gateway—none0/10

   No evidence in the pack mentions data residency, region selection, or data storage location controls for AI Gateway; only logging opt-out toggles for payload/prompt data are documented. This applicable privacy axis lacks any supporting evidence. missing for 10: region/residency selection settings, data localization guarantees, documentation on where logs/cache/metadata are stored.

   ⚑ flag

   Kong AI Gateway~partialclaimed3/10

   Kong AI Gateway documentation mentions an on-prem/self-hosted configuration option (configure-on-prem.md), which implies some ability to control where the gateway (and thus data in transit) runs, but there is no explicit documentation of region selection, data residency guarantees, or storage location controls for logs/analytics/cost data. missing for 10: explicit region/residency configuration options, documented data storage location controls, compliance statements about data residency.

   • [claimed-docs] “This page shows you how to configure the same capabilities with AI plugins on Services and Routes.”
   • [claimed-docs] “AI Gateway logs capture detailed information about the request and response payloads, token usage, model details, latency, and cost metrics.”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Cloudflare AI Gateway—none0/10

   The evidence shows AI Gateway can control its own logging/storage of prompts (e.g., disabling payload logging) but nothing indicates it can prevent downstream AI providers from using submitted data to train their models — that policy is controlled by the provider (OpenAI, Anthropic, etc.), not by the gateway. No documentation ties Cloudflare's logging controls to opting out of provider-side training use.

   • [claimed-docs] “This is useful when you want to maintain visibility into usage metrics and request metadata without persisting sensitive prompt or completio…”
   • [claimed-docs] “Protect your AI applications from leaking or sending sensitive information.”
   • [claimed-docs] “The `cf-aig-collect-log-payload` header allows you to control whether the raw request and response bodies (payloads) are stored for a given …”

   proof ↗⚑ flag

   Kong AI Gateway—none0/10

   Kong AI Gateway is an enterprise routing/governance layer for LLM traffic, so control over how provider data is used is a fair question, but the evidence pack contains no mention of training-data opt-out, zero-retention guarantees, or contractual terms preventing model providers from using proxied data for training — only general DLP/PII redaction and content-safety features are documented, which don't address this specific claim.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Cloudflare AI Gateway
   Cloudflare AI Gateway~partialclaimed6/10

   AI Gateway offers concrete controls relevant to data retention: per-request headers to bypass logging (cf-aig-collect-log) or exclude storing raw prompt/completion payloads (cf-aig-collect-log-payload), letting users limit what sensitive data is persisted. However, there's no documented data deletion mechanism, retention period/TTL settings, or bulk/account-level data purge capability. missing for 10: explicit data retention duration controls, a documented deletion/purge workflow for stored logs, and independent confirmation that opt-out headers fully prevent persistence.

   • [claimed-docs] “This is useful when you want to maintain visibility into usage metrics and request metadata without persisting sensitive prompt or completio…”
   • [claimed-docs] “The \`cf-aig-collect-log\` header allows you to bypass the default log setting for the gateway.”
   • [claimed-docs] “The `cf-aig-collect-log-payload` header allows you to control whether the raw request and response bodies (payloads) are stored for a given …”
   • [claimed-docs] “Your AI Gateway dashboard shows logs of individual requests, including the user prompt, model response, provider, timestamp, request status,…”

   proof ↗⚑ flag

   Kong AI Gateway—none0/10

   Evidence shows Kong AI Gateway logs request/response payloads, token usage, and costs (docs-10), and offers DLP/PII removal (docs-20) and semantic caching (docs-11), but none of the evidence describes configurable data retention periods or deletion/purge controls for logs, caches, or audit trails. Missing for 10: explicit retention policy settings, log/cache deletion or expiry controls, data subject deletion workflow.

   • [claimed-docs] “AI Gateway logs capture detailed information about the request and response payloads, token usage, model details, latency, and cost metrics.”
   • [claimed-docs] “Apply safety and DLP policies to prevent toxic content and remove personally identifiable information.”
   • [claimed-docs] “AI Semantic Cache - Plugin | Kong Docs”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round to Cloudflare AI Gateway
   Cloudflare AI Gateway~partialclaimed5/10

   AI Gateway exposes per-request headers (cf-aig-collect-log, cf-aig-collect-log-payload) that let a user bypass logging or avoid storing raw prompt/completion payloads, and docs note this is 'useful when you want to maintain visibility into usage metrics... without persisting sensitive prompt or completion data.' However, these are opt-outs for log/payload storage only, not for the underlying usage/metrics tracking (tokens, cost, request counts) that the gateway inherently collects for billing and rate limiting. missing for 10: a global/account-level telemetry opt-out toggle, documentation of disabling usage-metrics tracking entirely, independent confirmation that opting out actually stops Cloudflare-side usage tracking.

   • [claimed-docs] “The \`cf-aig-collect-log\` header allows you to bypass the default log setting for the gateway.”
   • [claimed-docs] “The `cf-aig-collect-log-payload` header allows you to control whether the raw request and response bodies (payloads) are stored for a given …”
   • [claimed-docs] “This is useful when you want to maintain visibility into usage metrics and request metadata without persisting sensitive prompt or completio…”
   • [claimed-docs] “Your AI Gateway dashboard shows logs of individual requests, including the user prompt, model response, provider, timestamp, request status,…”

   proof ↗⚑ flag

   Kong AI Gateway—none0/10

   No evidence pack items mention any telemetry opt-out, privacy settings, or usage-tracking controls for Kong AI Gateway itself; all evidence concerns the product's own traffic logging/analytics features rather than user opt-out of vendor telemetry.

   ⚑ flag

Fallbacks

1. platform engineerConfigure automatic fallback to another model or provider when one fails

   weight 3 · round to Cloudflare AI Gateway
   Cloudflare AI Gateway✓fullclaimed9/10

   Cloudflare AI Gateway explicitly documents automatic fallback to another model or provider on request errors or timeouts via the Universal endpoint, with clear examples (e.g., Workers AI failing over to OpenAI) and a response header (cf-aig-step) to identify which step succeeded. This is a well-documented, first-party feature with configuration details and dynamic routing support for fallbacks. Missing for 10: independent/hands-on verification beyond vendor docs, and no evidence of fallback behavior nuances (e.g., latency impact, partial failure handling) from real-world usage.

   • [claimed-docs] “Improve resilience by defining request retry and model fallbacks in case of an error.”
   • [claimed-docs] “Sends a request to Workers AI Inference API. 2. If that request fails, proceeds to OpenAI.”
   • [claimed-docs] “Cloudflare can trigger your fallback provider in response to request errors or predetermined request timeouts.”
   • [claimed-docs] “Specify model or provider fallbacks with your Universal endpoint to handle request failures and ensure reliability.”
   • [claimed-docs] “the response header `cf-aig-step` indicates which model successfully processed the request by returning the step number.”

   proof ↗⚑ flag

   Kong AI Gateway~partialclaimed5/10

   Kong AI Gateway documents load balancing across multiple LLM models/providers, which implies routing resilience, but the evidence never explicitly describes an automatic fallback mechanism triggered by provider failure (e.g., retry-on-error, circuit breaking, or failover behavior). Missing for 10: explicit fallback-on-failure documentation, failure detection/health-check mechanism, and any hands-on confirmation that fallback actually occurs when a provider errors out.

   • [claimed-docs] “AI Gateway provides load balancing capabilities to distribute requests across multiple LLM models.”
   • [claimed-docs] “The core of AI Gateway is the ability to serve AI Models from various AI Model Providers via a provider-agnostic API.”

   proof ↗⚑ flag

Load balancing

1. platform engineerLoad-balance traffic across providers, deployments, or keys by weight, latency, or cost

   weight 2 · round drawn
   Cloudflare AI Gateway~partialclaimed6/10

   AI Gateway supports dynamic routing (conditions, quotas, A/B/gradual rollouts, segment-based routing) and fallback chains across providers/models with sequential retry-on-error, but the evidence describes rule-based/conditional routing and ordered fallback sequences rather than true weighted, latency-based, or cost-based load balancing across providers/keys. missing for 10: explicit weighted traffic splitting, latency-based routing decisions, cost-based routing logic, and any independent/hands-on verification of these mechanisms.

   • [claimed-docs] “Improve resilience by defining request retry and model fallbacks in case of an error.”
   • [claimed-docs] “Sends a request to Workers AI Inference API. 2. If that request fails, proceeds to OpenAI.”
   • [claimed-docs] “Dynamic routing enables you to create request routing flows through a **visual interface** or a **JSON-based configuration**.”
   • [claimed-docs] “Directing different segments (paid/not-paid user) to different models”
   • [claimed-docs] “Restricting each user/project/team with budget/rate limits”
   • [claimed-docs] “Cloudflare can trigger your fallback provider in response to request errors or predetermined request timeouts.”
   • [claimed-docs] “A/B and gradual rollouts while making it accessible to both developers and non-technical team members.”
   • [claimed-docs] “you compose a small flow that evaluates conditions, enforces quotas, and chooses models with fallbacks. You can iterate without touching app…”
   • [claimed-docs] “Specify model or provider fallbacks with your Universal endpoint to handle request failures and ensure reliability.”

   proof ↗⚑ flag

   Kong AI Gateway~partialclaimed6/10

   Kong AI Gateway explicitly documents load-balancing across multiple LLM models/providers (docs-17), and it also tracks and calculates per-request LLM costs (docs-18) and latency metrics (docs-9), which are the raw signals needed for cost- or latency-aware routing. However, the evidence pack never confirms the specific load-balancing algorithms (e.g., weighted, latency-based, cost-based) are selectable options, so it's unclear whether these criteria can actually be used as balancing strategies. Missing for 10: explicit documentation of weight-based, latency-based, and cost-based load-balancing algorithms/configuration options, and independent confirmation these modes work as described.

   • [claimed-docs] “AI Gateway provides load balancing capabilities to distribute requests across multiple LLM models.”
   • [claimed-docs] “AI Gateway calculates that figure for every request to a large language model (LLM) provider, matching what the provider actually bills.”
   • [claimed-docs] “You can use these metrics to: Track LLM request latency and upstream provider processing time * Monitor token consumption ... * Calculate AI…”

   proof ↗⚑ flag

Policy routing

1. ai-native userMy agent can switch models mid-task by policy — cost, capability, or availability — through gateway routing rules

   weight 3 · round to Cloudflare AI Gateway
   Cloudflare AI Gateway✓fullclaimed8/10

   Cloudflare AI Gateway explicitly supports policy-driven model switching via Dynamic Routing (visual/JSON config for segment-based routing, budget/rate limits, A/B rollouts) and Fallbacks (automatic switch to another model/provider on error or timeout, with cf-aig-step header indicating which model handled the request). These directly satisfy switching by cost, capability, or availability without app code changes. missing for 10: independent/hands-on evidence of this working in production agent workflows, and explicit documentation of capability-based (not just error/availability-based) routing logic.

   • [claimed-docs] “Improve resilience by defining request retry and model fallbacks in case of an error.”
   • [claimed-docs] “Sends a request to Workers AI Inference API. 2. If that request fails, proceeds to OpenAI.”
   • [claimed-docs] “Dynamic routing enables you to create request routing flows through a **visual interface** or a **JSON-based configuration**.”
   • [claimed-docs] “Directing different segments (paid/not-paid user) to different models”
   • [claimed-docs] “Restricting each user/project/team with budget/rate limits”
   • [claimed-docs] “the response header `cf-aig-step` indicates which model successfully processed the request by returning the step number.”
   • [claimed-docs] “Cloudflare can trigger your fallback provider in response to request errors or predetermined request timeouts.”
   • [claimed-docs] “A/B and gradual rollouts while making it accessible to both developers and non-technical team members.”
   • [claimed-docs] “you compose a small flow that evaluates conditions, enforces quotas, and chooses models with fallbacks. You can iterate without touching app…”
   • [claimed-docs] “Specify model or provider fallbacks with your Universal endpoint to handle request failures and ensure reliability.”

   proof ↗⚑ flag

   Kong AI Gateway~partialclaimed5/10

   Kong AI Gateway documents load balancing across multiple LLM models (covering availability-based routing) and per-request cost calculation, which together imply some policy-driven model selection, but there is no explicit documentation of switching models based on capability or triggering mid-task, dynamic policy switches tied to cost or availability thresholds. Missing for 10: explicit cost/capability-based routing policy documentation, mid-task dynamic model switching evidence, and independent/hands-on corroboration of this routing-resilience behavior.

   • [claimed-docs] “AI Gateway provides load balancing capabilities to distribute requests across multiple LLM models.”
   • [claimed-docs] “AI Gateway calculates that figure for every request to a large language model (LLM) provider, matching what the provider actually bills.”
   • [claimed-docs] “AI Gateway can perform intelligent request routing, caching, and content filtering using semantic similarity queries.”

   proof ↗⚑ flag

Rate limits

1. platform engineerSmooth provider rate limits by spreading traffic across keys and queuing or throttling requests

   weight 2 · round drawn
   Cloudflare AI Gateway~partialclaimed6/10

   AI Gateway provides rate limiting (fixed/sliding, request-per-time-window) and fallback/retry to alternate providers/models, which helps smooth provider limits and errors, and dynamic routing can enforce per-user/team quotas. However, there is no explicit documentation of key rotation/spreading traffic across multiple API keys for the same provider, nor of a request queuing mechanism (rate limiting appears to reject/throttle rather than queue). missing for 10: explicit multi-key load balancing/rotation across provider keys, documented request queuing behavior (vs. simple throttling/rejection), independent evidence of this working at scale.

   • [claimed-docs] “Rate limiting controls the traffic that reaches your application, which prevents expensive bills and suspicious activity.”
   • [claimed-docs] “You can also select if you would like a **fixed** or **sliding** rate limiting technique.”
   • [claimed-docs] “You can define rate limits as the number of requests that get sent in a specific time frame. For example, you can limit your application to …”
   • [claimed-docs] “Control how your application scales by limiting the number of requests your application receives.”
   • [claimed-docs] “Improve resilience by defining request retry and model fallbacks in case of an error.”
   • [claimed-docs] “Sends a request to Workers AI Inference API. 2. If that request fails, proceeds to OpenAI.”
   • [claimed-docs] “Cloudflare can trigger your fallback provider in response to request errors or predetermined request timeouts.”
   • [claimed-docs] “Specify model or provider fallbacks with your Universal endpoint to handle request failures and ensure reliability.”
   • [claimed-docs] “Restricting each user/project/team with budget/rate limits”
   • [claimed-docs] “you compose a small flow that evaluates conditions, enforces quotas, and chooses models with fallbacks. You can iterate without touching app…”

   proof ↗⚑ flag

   Kong AI Gateway~partialclaimed6/10

   Kong AI Gateway documents load balancing across multiple LLM models/providers and a dedicated 'AI Rate Limiting Advanced' plugin for enforcing rate limits, which together support spreading traffic and throttling. However, there is no explicit documentation of spreading traffic across multiple API keys for the same provider or of request queuing behavior when limits are hit. Missing for 10: explicit key-rotation/multi-key load balancing, request queuing mechanics, and any hands-on/independent verification of these features working together.

   • [claimed-docs] “AI Gateway provides load balancing capabilities to distribute requests across multiple LLM models.”
   • [claimed-docs] “AI Rate Limiting Advanced - Plugin | Kong Docs”
   • [claimed-docs] “AI Gateway calculates that figure for every request to a large language model (LLM) provider, matching what the provider actually bills.”

   proof ↗⚑ flag

Retries

1. platform engineerSet automatic retry policies for transient provider errors

   weight 2 · round to Cloudflare AI Gateway
   Cloudflare AI Gateway✓fullclaimed8/10

   Cloudflare AI Gateway explicitly supports request retries and fallbacks triggered by errors or timeouts (docs-7, docs-20, docs-33), with response headers indicating which step/model succeeded (docs-17). This directly satisfies automatic retry policies for transient provider errors. missing for 10: no evidence of configurable retry counts/backoff intervals specifically for 'retry' (vs fallback) and no independent/hands-on corroboration beyond first-party docs.

   • [claimed-docs] “Improve resilience by defining request retry and model fallbacks in case of an error.”
   • [claimed-docs] “Sends a request to Workers AI Inference API. 2. If that request fails, proceeds to OpenAI.”
   • [claimed-docs] “the response header `cf-aig-step` indicates which model successfully processed the request by returning the step number.”
   • [claimed-docs] “Cloudflare can trigger your fallback provider in response to request errors or predetermined request timeouts.”
   • [claimed-docs] “Specify model or provider fallbacks with your Universal endpoint to handle request failures and ensure reliability.”

   proof ↗⚑ flag

   Kong AI Gateway~partialclaimed4/10

   Kong AI Gateway documents load balancing across multiple LLM models/providers (docs-17), which implies some failover capability, but the evidence never explicitly describes configurable automatic retry policies for transient provider errors (e.g., retry counts, backoff, error-code triggers). Missing for 10: explicit retry-policy documentation, retry configuration options, and evidence of behavior on transient errors specifically.

   • [claimed-docs] “AI Gateway provides load balancing capabilities to distribute requests across multiple LLM models.”
   • [claimed-docs] “The core of AI Gateway is the ability to serve AI Models from various AI Model Providers via a provider-agnostic API.”

   proof ↗⚑ flag

Streaming

1. developerStream token-by-token responses through the gateway from any provider

   weight 3 · round to Kong AI Gateway
   Cloudflare AI Gateway—none0/10

   The evidence describes AI Gateway as a proxy supporting multiple providers, an OpenAI-compatible /chat/completions endpoint, and native API pass-through, but nowhere explicitly confirms token-by-token streaming support or documents how streaming responses are handled through the gateway. missing for 10: explicit documentation or example of streaming/SSE support, confirmation that streaming works uniformly across all connected providers.

   • [claimed-docs] “Cloudflare's AI Gateway offers an OpenAI-compatible `/chat/completions` endpoint, enabling integration with multiple AI providers using a si…”
   • [claimed-docs] “Connect to AI providers using their native API formats through AI Gateway.”
   • [claimed-docs] “This feature simplifies the integration process, allowing for seamless switching between different models without significant code modificat…”

   proof ↗⚑ flag

   Kong AI Gateway✓fullclaimed8/10

   Kong AI Gateway has a dedicated streaming.md doc confirming token-by-token streaming from models is supported and rendered in real time, layered on top of its provider-agnostic API supporting multiple LLM providers. Missing for 10: independent/hands-on confirmation of streaming behavior across every provider and any details on streaming with proxy-added policies (e.g., guardrails) applied mid-stream.

   • [claimed-docs] “most models can stream each word (or sets of words and tokens) back to the client. This allows the chat response to be rendered in real time…”
   • [claimed-docs] “The core of AI Gateway is the ability to serve AI Models from various AI Model Providers via a provider-agnostic API.”

   proof ↗⚑ flag

Tool calling

1. developerRequest structured JSON-schema outputs across providers

   weight 1 · round drawn
   Cloudflare AI Gateway—none0/10

   Cloudflare AI Gateway is a proxy/observability layer that passes requests through to native or OpenAI-compatible provider APIs; the evidence describes routing, caching, fallbacks, logging, and rate limiting, but nothing about enforcing or normalizing structured JSON-schema output across providers. Missing for 10: any mention of JSON-schema/response_format enforcement, schema validation, or cross-provider structured-output normalization.

   • [claimed-docs] “Cloudflare's AI Gateway offers an OpenAI-compatible `/chat/completions` endpoint, enabling integration with multiple AI providers using a si…”
   • [claimed-docs] “Switch providers by changing the \`model\` and \`apiKey\` parameters.”
   • [claimed-docs] “Connect to AI providers using their native API formats through AI Gateway.”

   proof ↗⚑ flag

   Kong AI Gateway—none0/10

   The evidence pack covers provider-agnostic proxying, streaming, load balancing, cost tracking, and safety policies, but no document mentions structured/JSON-schema output enforcement or normalization across providers. This is a fair capability to expect from an AI gateway, but no evidence supports it.

   ⚑ flag

2. developerMake tool and function calls across different providers with a consistent schema

   weight 3 · round to Kong AI Gateway
   Cloudflare AI Gateway~partialclaimed5/10

   AI Gateway provides an OpenAI-compatible /chat/completions endpoint and unified switching between providers via model/apiKey parameters, plus native API pass-through, which supports a consistent schema for chat-style requests across providers. However, the evidence never explicitly discusses tool/function-calling schema normalization (e.g., translating tool_call formats between Anthropic, Gemini, OpenAI, etc.) — it only covers general chat completion routing, caching, logging, and fallback headers. missing for 10: explicit documentation or examples of function/tool-call schema normalization across providers, evidence of consistent tool-call response parsing, and independent/hands-on confirmation that function calling works uniformly across all supported providers.

   • [claimed-docs] “This feature simplifies the integration process, allowing for seamless switching between different models without significant code modificat…”
   • [claimed-docs] “Cloudflare's AI Gateway offers an OpenAI-compatible `/chat/completions` endpoint, enabling integration with multiple AI providers using a si…”
   • [claimed-docs] “Switch providers by changing the \`model\` and \`apiKey\` parameters.”
   • [claimed-docs] “Connect to AI providers using their native API formats through AI Gateway.”
   • [claimed-docs] “Workers AI, Anthropic, Google Gemini, OpenAI, Replicate, and more work with AI Gateway.”

   proof ↗⚑ flag

   Kong AI Gateway~partialclaimed6/10

   Kong AI Gateway documents a provider-agnostic API for LLM traffic and an AI MCP Proxy/Server that converts REST APIs into MCP tools, suggesting a consistent tool-calling interface across providers and models. However, there is no explicit documentation showing normalization of function/tool-call schemas (e.g., translating OpenAI-style function calls to Anthropic tool-use format) for the same request across different providers. Missing for 10: explicit cross-provider function-call schema translation examples, hands-on/independent verification of consistent tool-call behavior across providers.

   • [claimed-docs] “The core of AI Gateway is the ability to serve AI Models from various AI Model Providers via a provider-agnostic API.”
   • [claimed-docs] “AI MCP Proxy bridges Kong-managed Services to the Model Context Protocol, converting REST APIs into MCP tools or fronting upstream MCP serve…”
   • [claimed-docs] “Turn any API into an MCP server using the AI MCP Server entity. This approach does not require an LLM and provides full control over product…”
   • [claimed-docs] “Govern LLM, MCP, and agent-to-agent (A2A) traffic with the same Kong AI Gateway.”

   proof ↗⚑ flag

Catalog

1. developerBrowse or query a catalog of available models with pricing and context-window metadata

   weight 2 · round drawn
   Cloudflare AI Gateway—none0/10

   The evidence pack shows AI Gateway supports multiple providers, per-token pricing pass-through, logging, caching, and routing, but there is no mention of a browsable/queryable catalog of models with pricing and context-window metadata—developers must know provider/model names themselves and check pricing docs separately (docs-16 only states pricing pass-through policy, not a queryable catalog).

   • [claimed-docs] “Workers AI, Anthropic, Google Gemini, OpenAI, Replicate, and more work with AI Gateway.”
   • [claimed-docs] “Inference pricing from providers is passed through with no markup — you pay the same per-token rates as you would directly with the provider…”

   proof ↗⚑ flag

   Kong AI Gateway—none0/10

   Evidence shows Kong AI Gateway supports multi-provider routing and calculates per-request costs, but there is no documented catalog/endpoint for browsing or querying available models with pricing and context-window metadata — the closest evidence (model-cost-management, list-ai-gateways API) covers cost calculation per request and listing gateway instances, not a model metadata catalog.

   • [claimed-docs] “AI Gateway calculates that figure for every request to a large language model (LLM) provider, matching what the provider actually bills.”
   • [claimed-docs] “list-ai-gateways summary: List AI Gateways description: Returns a list of AI Gateways in the organization.”
   • [claimed-docs] “The core of AI Gateway is the ability to serve AI Models from various AI Model Providers via a provider-agnostic API.”

   proof ↗⚑ flag

Compatibility

1. developerPoint existing OpenAI-compatible code at the gateway by changing only the base URL and key

   weight 3 · round to Cloudflare AI Gateway
   Cloudflare AI Gateway✓fullclaimed8/10

   Docs confirm an OpenAI-compatible /chat/completions endpoint that allows switching providers by only changing model/apiKey parameters against a single URL, directly matching the story. missing for 10: independent/hands-on developer confirmation outside Cloudflare's own docs, and explicit example showing literal drop-in replacement of OpenAI SDK base_url with no other code changes.

   • [claimed-docs] “Cloudflare's AI Gateway offers an OpenAI-compatible `/chat/completions` endpoint, enabling integration with multiple AI providers using a si…”
   • [claimed-docs] “Switch providers by changing the \`model\` and \`apiKey\` parameters.”
   • [claimed-docs] “This feature simplifies the integration process, allowing for seamless switching between different models without significant code modificat…”
   • [claimed-docs] “Manage all your costs with one simple bill and access every provider through a single API.”

   proof ↗⚑ flag

   Kong AI Gateway~partialclaimed6/10

   Kong AI Gateway is documented as a provider-agnostic API layer that proxies LLM requests (chat/completions endpoints) with streaming support, which implies OpenAI-style compatibility, but no evidence explicitly confirms that existing OpenAI SDK code works unmodified by only swapping base URL and API key. missing for 10: explicit doc/example showing an OpenAI SDK client redirected via base_url with no code changes, and confirmation that request/response schemas exactly mirror OpenAI's format.

   • [claimed-docs] “The core of AI Gateway is the ability to serve AI Models from various AI Model Providers via a provider-agnostic API.”
   • [claimed-docs] “most models can stream each word (or sets of words and tokens) back to the client. This allows the chat response to be rendered in real time…”
   • [claimed-docs] “This page shows you how to configure the same capabilities with AI plugins on Services and Routes.”

   proof ↗⚑ flag

One endpoint

1. developerCall many model providers through one consistent API

   weight 3 · round to Cloudflare AI Gateway
   Cloudflare AI Gateway✓fullclaimed9/10

   Docs clearly show a unified OpenAI-compatible /chat/completions endpoint and a Universal endpoint that route to many providers (Workers AI, Anthropic, Gemini, OpenAI, Replicate, etc.) via consistent APIs, with model/provider switching via simple parameter changes and pass-through pricing. Missing for 10: independent/hands-on developer corroboration beyond first-party docs.

   • [claimed-docs] “Cloudflare's AI Gateway offers an OpenAI-compatible `/chat/completions` endpoint, enabling integration with multiple AI providers using a si…”
   • [claimed-docs] “Workers AI, Anthropic, Google Gemini, OpenAI, Replicate, and more work with AI Gateway.”
   • [claimed-docs] “This feature simplifies the integration process, allowing for seamless switching between different models without significant code modificat…”
   • [claimed-docs] “Switch providers by changing the \`model\` and \`apiKey\` parameters.”
   • [claimed-docs] “Connect to AI providers using their native API formats through AI Gateway.”
   • [claimed-docs] “Manage all your costs with one simple bill and access every provider through a single API.”

   proof ↗⚑ flag

   Kong AI Gateway✓fullclaimed8/10

   Kong AI Gateway explicitly provides a provider-agnostic API to route to many LLM providers, with load balancing and unified logging/observability across providers, matching the core unified-API story. Missing for 10: independent/hands-on developer corroboration of consistent request/response schema across providers, and no explicit list of exact supported providers in evidence.

   • [claimed-docs] “The core of AI Gateway is the ability to serve AI Models from various AI Model Providers via a provider-agnostic API.”
   • [claimed-docs] “AI Gateway provides load balancing capabilities to distribute requests across multiple LLM models.”
   • [claimed-docs] “You can use these metrics to: Track LLM request latency and upstream provider processing time * Monitor token consumption ... * Calculate AI…”
   • [claimed-docs] “AI Gateway calculates that figure for every request to a large language model (LLM) provider, matching what the provider actually bills.”

   proof ↗⚑ flag