Vercel AI Gateway vs Cloudflare AI Gateway

Agent access

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

   weight 2 · round to Vercel AI Gateway
   Vercel AI Gateway✓fullprobed9/10

   Vercel confirms a live llms.txt (probe-1) plus per-page .md documentation endpoints (probe-2) and an OpenAPI spec (probe-3), all machine-readable for agent consumption, and docs explicitly mention coding-agent setup guidance (docs-8, docs-24). Missing for 10: no independent/community confirmation that agents actually use these llms.txt/docs successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://vercel.com/llms.txt # Vercel > Vercel is a cloud platform for building, deploying, and scaling web appl…”
   • [probe] “PROBE docs-md: HTTP 200 at https://vercel.com/docs/ai-gateway.md --- title: AI Gateway product: vercel url: /docs/ai-gateway canonical_url: …”
   • [probe] “PROBE openapi: HTTP 200 at https://vercel.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “vercel ai-gateway coding-agents setup”
   • [claimed-docs] “AI Gateway routes requests, manages fallbacks and budgets, monitors usage, and connects supported coding agents.”

   proof ↗⚑ flag

   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

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

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

   AI Gateway is an API/HTTP gateway with OpenAI-compatible endpoints, unauthenticated model listing, OIDC token auth for deployed apps, and a keyless models endpoint verified live — all of which support pure headless/CI/automation use without any UI dependency. missing for 10: no explicit CI pipeline example (e.g., GitHub Actions) or independent third-party report of CI usage.

   • [claimed-docs] “You can use existing OpenAI client libraries, switch to AI Gateway with a URL change, and keep your current tools and workflows without code…”
   • [claimed-docs] “For applications deployed on Vercel, OIDC tokens are automatically available as `VERCEL_OIDC_TOKEN`. No secrets to manage, no keys to rotate…”
   • [claimed-docs] “This endpoint requires no authentication and returns detailed information including model IDs, context windows, and pricing.”
   • [claimed-docs] “For applications deployed on Vercel, OIDC tokens are automatically available as VERCEL_OIDC_TOKEN. No secrets to manage, no keys to rotate. …”
   • [claimed-docs] “You can use the AI Gateway's Chat Completions API with existing tools and libraries like the OpenAI client libraries and AI SDK. Point your …”
   • [probe] “PROBE openapi: HTTP 200 at https://vercel.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE keyless-endpoint: GET https://ai-gateway.vercel.sh/v1/models returned HTTP 200 application/json with an OpenAI-compatible {"object":"l…”

   proof ↗⚑ flag

   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

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

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

   The docs mention connecting 'supported coding agents' and generic gateway integration, but there is no evidence of an official MCP (Model Context Protocol) server or endpoint that agents can connect to. Missing for 10: explicit MCP server documentation, MCP endpoint URL, and demonstration of an agent connecting via MCP.

   • [claimed-docs] “vercel ai-gateway coding-agents setup”
   • [claimed-docs] “AI Gateway routes requests, manages fallbacks and budgets, monitors usage, and connects supported coding agents.”

   proof ↗⚑ flag

   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

4. ai-native userUse an official CLI

   weight 2 · round to Vercel AI Gateway
   Vercel AI Gateway~partialclaimed3/10

   The only evidence of a CLI is the fragment 'vercel ai-gateway coding-agents setup', implying an official `vercel` CLI subcommand for configuring the AI Gateway with coding agents, but there is no detailed command reference, install instructions, or broader CLI documentation for AI-native workflows beyond this single mention. Missing for 10: full CLI command reference/docs, examples of CLI usage for model routing/config, independent confirmation of CLI functionality.

   • [claimed-docs] “vercel ai-gateway coding-agents setup”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Vercel AI Gateway
   Vercel AI Gateway✓fullprobed9/10

   AI Gateway exposes a documented, OpenAI-compatible public API (Chat Completions, models endpoint) with a verified OpenAPI spec, unauthenticated models endpoint, and probe confirming a live JSON API response, enabling programmatic/agentic control via standard SDKs or raw HTTP. missing for 10: independent third-party developer writeups explicitly praising the API's completeness/stability beyond Vercel's own docs and probes.

   • [claimed-docs] “You can use existing OpenAI client libraries, switch to AI Gateway with a URL change, and keep your current tools and workflows without code…”
   • [claimed-docs] “This endpoint requires no authentication and returns detailed information including model IDs, context windows, and pricing.”
   • [claimed-docs] “Query the models endpoint directly to get a JSON list of all available models with pricing and capabilities”
   • [claimed-docs] “You can use the AI Gateway's Chat Completions API with existing tools and libraries like the OpenAI client libraries and AI SDK. Point your …”
   • [probe] “PROBE openapi: HTTP 200 at https://vercel.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE keyless-endpoint: GET https://ai-gateway.vercel.sh/v1/models returned HTTP 200 application/json with an OpenAI-compatible {"object":"l…”

   proof ↗⚑ flag

   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

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

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

   Docs show budget caps that can be set per API key, per project, or per team member (docs-16), and per-key usage breakdown in Requests logs (docs-12), plus short-lived OIDC tokens for Vercel-deployed apps that avoid static secrets (docs-14/22). This supports issuing distinct, budget-limited keys for an agent, but there is no documentation of fine-grained permission scoping (e.g. restricting a key to specific models/providers/actions) beyond spend limits. missing for 10: explicit least-privilege scoping controls (model/provider/action restrictions per key), role-based permission model, first-party or independent confirmation of true least-privilege agent credentials

   • [claimed-docs] “To cap how much your team, a project, an API key, or a team member can spend, set [budgets]”
   • [claimed-docs] “The Requests section displays summaries by project, API key, and a detailed log of all requests.”
   • [claimed-docs] “For applications deployed on Vercel, OIDC tokens are automatically available as `VERCEL_OIDC_TOKEN`. No secrets to manage, no keys to rotate…”
   • [claimed-docs] “For applications deployed on Vercel, OIDC tokens are automatically available as VERCEL_OIDC_TOKEN. No secrets to manage, no keys to rotate. …”

   proof ↗⚑ flag

   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

7. ai-native userBuild against official SDKs

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

   AI Gateway is designed to be used via existing official SDKs (OpenAI client libraries, Anthropic SDK, Vercel AI SDK) with just a base URL/model-string change, documented in openai-compat and getting-started guides, and confirmed by a live OpenAI-compatible endpoint probe. It also supports agent-building primitives like ToolLoopAgent for agentic workflows. missing for 10: no independent/hands-on developer confirmation beyond vendor docs and one API probe.

   • [claimed-docs] “You can use existing OpenAI client libraries, switch to AI Gateway with a URL change, and keep your current tools and workflows without code…”
   • [claimed-docs] “Point your existing OpenAI or Anthropic SDK at AI Gateway. Same calls, no rewrites.”
   • [claimed-docs] “You can use the AI Gateway's Chat Completions API with existing tools and libraries like the OpenAI client libraries and AI SDK. Point your …”
   • [claimed-docs] “Move existing OpenAI, Anthropic, and AI SDK integrations to AI Gateway with a base URL swap.”
   • [claimed-docs] “const agent = new ToolLoopAgent({ model: 'anthropic/claude-sonnet-5', tools: { getWeather: tool({”
   • [probe] “PROBE keyless-endpoint: GET https://ai-gateway.vercel.sh/v1/models returned HTTP 200 application/json with an OpenAI-compatible {"object":"l…”

   proof ↗⚑ flag

   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

8. ai-native userSubscribe to events via webhooks

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

   No evidence anywhere in the pack of webhook subscriptions or event-driven notifications from AI Gateway; the product exposes REST APIs, logs, and observability dashboards, but nothing about webhooks for events like request completion, budget alerts, or failures.

   ⚑ flag

   Cloudflare AI Gateway—none0/10

   No evidence in the pack mentions webhooks or any event-subscription mechanism; AI Gateway's documented features are logging, caching, rate limiting, fallbacks, and dynamic routing, none of which describe outbound webhook notifications for events. This is a plausible axis for a gateway product (it could offer webhook callbacks on events like errors or budget thresholds), so absence of evidence yields 'none' rather than 'na'.

   ⚑ flag

Api quality

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

   weight 2 · round to Vercel AI Gateway
   Vercel AI Gateway~partialprobed5/10

   There's a documented OpenAPI spec and a live, keyless models endpoint that returns JSON model data, showing some interactive/runnable API surface, but there's no evidence of an interactive API reference UI (like Swagger/Redoc) with embedded runnable examples or a try-it-now console. missing for 10: an actual interactive API explorer/playground page, runnable code snippets embedded in docs, independent confirmation of a docs UI with live request execution.

   • [probe] “PROBE openapi: HTTP 200 at https://vercel.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE keyless-endpoint: GET https://ai-gateway.vercel.sh/v1/models returned HTTP 200 application/json with an OpenAI-compatible {"object":"l…”
   • [claimed-docs] “This endpoint requires no authentication and returns detailed information including model IDs, context windows, and pricing.”
   • [claimed-docs] “Query the models endpoint directly to get a JSON list of all available models with pricing and capabilities”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Cloudflare AI Gateway
   Vercel AI Gateway✓fullprobed7/10

   A probe confirms a live OpenAPI JSON spec at vercel.com/openapi.json (contains the 'openapi' key) and the docs also expose a keyless models JSON endpoint and OpenAI-compatible API, all of which are machine-readable and programmatically consumable. Missing for 10: explicit confirmation the openapi.json spec covers AI Gateway endpoints specifically (vs. general Vercel API) and independent third-party validation of the spec's completeness.

   • [probe] “PROBE openapi: HTTP 200 at https://vercel.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE keyless-endpoint: GET https://ai-gateway.vercel.sh/v1/models returned HTTP 200 application/json with an OpenAI-compatible {"object":"l…”
   • [claimed-docs] “This endpoint requires no authentication and returns detailed information including model IDs, context windows, and pricing.”
   • [claimed-docs] “Query the models endpoint directly to get a JSON list of all available models with pricing and capabilities”

   proof ↗⚑ flag

   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

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

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

   Evidence shows an OpenAI-compatible endpoint with a 'v1' path and an openapi.json spec, but nowhere does the pack document an explicit API versioning scheme or a deprecation policy for endpoints/models. Missing for 10: explicit versioning strategy documentation, deprecation/sunset timelines, migration guidance for breaking changes.

   • [probe] “PROBE openapi: HTTP 200 at https://vercel.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE keyless-endpoint: GET https://ai-gateway.vercel.sh/v1/models returned HTTP 200 application/json with an OpenAI-compatible {"object":"l…”
   • [claimed-docs] “Query the models endpoint directly to get a JSON list of all available models with pricing and capabilities”

   proof ↗⚑ flag

   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

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

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

   The evidence pack covers routing, failover, BYOK, observability, and embeddings, but there is no mention of any batch/bulk request API or capability to process many items in a single operation. Since a gateway product could plausibly offer batch endpoints (e.g., batch inference or bulk embeddings), the axis applies, but no evidence supports it being delivered.

   ⚑ flag

   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

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

   weight 3 · round to Cloudflare AI Gateway
   Vercel AI Gateway~partialclaimed4/10

   The Gateway supports narrow built-in automation triggers — failover/retry on provider failure, per-provider timeouts triggering fast failover, and budget caps that block spend once a threshold is hit — which are rule-like actions triggered by events (docs-3, docs-10, docs-13, docs-16). However, there's no general-purpose, user-defined rules/event system (e.g., custom conditions, webhooks, arbitrary trigger-action pairs) for AI-native users to configure; the 'rules' are limited to routing, caching, and spend-cap logic. Missing for 10: a configurable rules engine for arbitrary events/actions, webhook or external-trigger support, and evidence of user-defined conditional automation beyond routing/budget defaults.

   • [claimed-docs] “High reliability. Automatically retries requests to other providers if one fails”
   • [claimed-docs] “You can set per-provider timeouts to trigger fast failover when a provider is slow to respond.”
   • [claimed-docs] “If a query using your credentials fails, AI Gateway will retry the query with its system credentials to improve service availability.”
   • [claimed-docs] “To cap how much your team, a project, an API key, or a team member can spend, set [budgets]”
   • [claimed-docs] “You can use order, only, and sort in providerOptions.gateway to control which providers handle your requests, in what order, and how they ar…”

   proof ↗⚑ flag

   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

Caching

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

   weight 2 · round to Cloudflare AI Gateway
   Vercel AI Gateway~partialcommunity6/10

   Docs explicitly describe a `caching: 'auto'` option in providerOptions.gateway that lets the gateway apply provider-appropriate caching automatically, directly supporting cost/latency reduction on repeated requests, and community pricing discussion confirms cache-read pricing exists for at least one model. However, details on cache hit-rate guarantees, TTL, scope, or independent benchmarks of latency/cost savings are absent. Missing for 10: independent hands-on benchmarks showing latency/cost reduction, documentation on cache TTL/invalidation/scope, confirmation caching works uniformly across all providers rather than being provider-dependent.

   • [claimed-docs] “You can use `caching: 'auto'` in `providerOptions.gateway` to let AI Gateway automatically apply the appropriate caching strategy based on t…”
   • [claimed-docs] “You can use caching: 'auto' in providerOptions.gateway to let AI Gateway automatically apply the appropriate caching strategy based on the p…”
   • [community] “Vercel cache read pricing for DeepSeek-v4: $0.01/M for flash, $0.14/M for pro — a 64% discount vs DeepSeek/OpenRouter on flash caching, prom…”

   proof ↗⚑ flag

   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

Latency

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

   weight 2 · round to Vercel AI Gateway
   Vercel AI Gateway~partialclaimed4/10

   Docs show performance-related controls (per-provider timeouts for fast failover, sort-by-performance metric, automatic caching) that imply attention to latency, but there is no direct benchmark or explicit claim quantifying the gateway's own added latency overhead. Missing for 10: published latency benchmarks or first-party/independent measurements showing the gateway adds minimal overhead versus direct provider calls, and no community corroboration of low added latency.

   • [claimed-docs] “You can set per-provider timeouts to trigger fast failover when a provider is slow to respond.”
   • [claimed-docs] “You can also use `sort` to rank providers by a performance or cost metric. The gateway sorts providers by the chosen metric and tries them i…”
   • [claimed-docs] “You can use `caching: 'auto'` in `providerOptions.gateway` to let AI Gateway automatically apply the appropriate caching strategy based on t…”
   • [claimed-docs] “You can use caching: 'auto' in providerOptions.gateway to let AI Gateway automatically apply the appropriate caching strategy based on the p…”

   proof ↗⚑ flag

   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

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 Vercel AI Gateway
   Vercel AI Gateway~partialcommunity6/10

   Docs confirm you can create per-API-key budgets and view spend/usage broken out by API key (docs-16, docs-12, docs-5), which supports giving an agent its own key with a spend cap. However, there is no explicit documentation of rate-limit guardrails (only spend budgets), and community evidence shows real friction around balance-based enforcement even with BYOK keys, so the 'cannot run away on spend' guarantee is only partially evidenced. Missing for 10: explicit per-key rate-limiting controls, clear docs on key-level rate guardrails (not just budget caps), and independent confirmation that budget enforcement reliably halts an autonomous agent before overspend.

   • [claimed-docs] “To cap how much your team, a project, an API key, or a team member can spend, set [budgets]”
   • [claimed-docs] “The Requests section displays summaries by project, API key, and a detailed log of all requests.”
   • [claimed-docs] “Spend monitoring. Monitor your spending across different providers”
   • [community] “If I bring my own Anthropic/OpenAI key and have usage available, why does Vercel's account balance determine whether my request executes? (V…”

   proof ↗⚑ flag

   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

Budgets

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

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

   Docs explicitly state budgets can be set to cap spend for a team, project, API key, or team member, directly matching the story, and spend monitoring/usage dashboards support enforcement. missing for 10: independent/hands-on confirmation that hard budgets actually block spend at the limit (community evidence only discusses BYOK balance blocking, not per-key/team/user budget enforcement specifics) and more detail on granularity/configuration UI.

   • [claimed-docs] “To cap how much your team, a project, an API key, or a team member can spend, set [budgets]”
   • [claimed-docs] “Spend monitoring. Monitor your spending across different providers”
   • [claimed-docs] “The Requests section displays summaries by project, API key, and a detailed log of all requests.”
   • [claimed-docs] “The Usage section displays four metrics to help you monitor your AI Gateway activity.”

   proof ↗⚑ flag

   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

Spend tracking

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

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

   Docs show request/usage summaries broken down by project and API key, budgets settable per team/project/API key/team member, and detailed logs filterable by model/provider/status with CSV/JSON export, directly matching the story's cost-tracking dimensions. Missing for 10: explicit per-user (not just per-team-member/API key) breakdowns and independent third-party confirmation of the dashboard's granularity in practice.

   • [claimed-docs] “Spend monitoring. Monitor your spending across different providers”
   • [claimed-docs] “The Requests section displays summaries by project, API key, and a detailed log of all requests.”
   • [claimed-docs] “To cap how much your team, a project, an API key, or a team member can spend, set [budgets]”
   • [claimed-docs] “open the Logs page, where you can search by request ID, filter by model, provider, or status code, follow requests live, and open one reques…”
   • [claimed-docs] “The Usage section displays four metrics to help you monitor your AI Gateway activity.”

   proof ↗⚑ flag

   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

Byok

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

   weight 2 · round to Cloudflare AI Gateway
   Vercel AI Gateway!disputedcontradicted5/10

   Vercel's docs clearly describe BYOK support — pass provider credentials per-request via providerOptions.gateway.byok, with no markup on tokens, and even fallback to system credentials on failure — suggesting bring-your-own-key traffic should run on the developer's own credentials (docs-6, docs-13, docs-19, docs-27). However, a concrete community report describes BYOK requests being blocked by Vercel's account balance reaching $0 even when the user's own provider key has available usage, directly contradicting the expectation that BYOK traffic is unaffected by platform account balance (comm-1). missing for 10: independent confirmation resolving the balance-dependency complaint, clearer documentation on how billing/balance interacts with BYOK requests.

   • [claimed-docs] “No markup on tokens. Tokens cost the same as they would from the provider directly, with zero markup, including with [Bring Your Own Key (BY…”
   • [claimed-docs] “If a query using your credentials fails, AI Gateway will retry the query with its system credentials to improve service availability.”
   • [claimed-docs] “No markup on tokens. Tokens cost the same as they would from the provider directly, with zero markup, including with Bring Your Own Key (BYO…”
   • [claimed-docs] “you can pass provider credentials on a per-request basis using the byok option in providerOptions.gateway. This is useful when you need to u…”
   • [community] “If I bring my own Anthropic/OpenAI key and have usage available, why does Vercel's account balance determine whether my request executes? (V…”

   proof ↗⚑ flag

   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

Programmatic admin

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

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

   Docs describe setting budgets, API keys, and monitoring spend through the Vercel dashboard/CLI, and a general Vercel OpenAPI spec exists, but there is no evidence of a documented admin API specifically for programmatically provisioning AI Gateway resources, keys, or budgets. Missing for 10: explicit admin/API endpoints for creating gateways, generating keys, or setting budgets programmatically, and any docs or examples showing this workflow.

   • [claimed-docs] “To cap how much your team, a project, an API key, or a team member can spend, set [budgets]”
   • [claimed-docs] “The Requests section displays summaries by project, API key, and a detailed log of all requests.”
   • [probe] “PROBE openapi: HTTP 200 at https://vercel.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   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

Virtual keys

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

   weight 3 · round to Vercel AI Gateway
   Vercel AI Gateway✓fullclaimed7/10

   Docs show a single Gateway-managed API key (or OIDC token) replaces direct provider keys, with per-API-key usage tracking and budget caps that imply teams/apps can have distinct managed keys, and BYOK/system-credential fallback keeps raw provider secrets out of app code. Missing for 10: explicit dashboard walkthrough for creating/rotating multiple named keys per team or app, and documentation of per-key role/permission scoping.

   • [claimed-docs] “One key, hundreds of models. Access models from multiple providers with a single API key”
   • [claimed-docs] “The Requests section displays summaries by project, API key, and a detailed log of all requests.”
   • [claimed-docs] “To cap how much your team, a project, an API key, or a team member can spend, set [budgets]”
   • [claimed-docs] “If a query using your credentials fails, AI Gateway will retry the query with its system credentials to improve service availability.”
   • [claimed-docs] “For applications deployed on Vercel, OIDC tokens are automatically available as `VERCEL_OIDC_TOKEN`. No secrets to manage, no keys to rotate…”
   • [claimed-docs] “you can pass provider credentials on a per-request basis using the byok option in providerOptions.gateway. This is useful when you need to u…”

   proof ↗⚑ flag

   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

Integrations

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

   weight 1 · round to Vercel AI Gateway
   Vercel AI Gateway~partialclaimed5/10

   The gateway provides a Logs UI with filtering and CSV/JSON export of request logs, which supports manual export of logs, but there's no evidence of native integration with external observability stacks (e.g., OpenTelemetry export, webhook/streaming to Datadog/Grafana, or trace export in standard formats like OTLP). missing for 10: OpenTelemetry/OTLP trace export, native integrations with third-party observability platforms, automated/streaming log export (vs manual CSV/JSON download), independent confirmation of export usability.

   • [claimed-docs] “open the Logs page, where you can search by request ID, filter by model, provider, or status code, follow requests live, and open one reques…”
   • [claimed-docs] “The Requests section displays summaries by project, API key, and a detailed log of all requests.”
   • [claimed-docs] “The Usage section displays four metrics to help you monitor your AI Gateway activity.”

   proof ↗⚑ flag

   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

Logs

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

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

   Docs describe a Logs page with per-request detail, search by request ID, filtering by model/provider/status, and export as CSV/JSON, plus a Requests section with summaries by project/API key and a Usage section with metrics — covering latency, tokens, cost, and routing detail. Missing for 10: independent/hands-on confirmation that latency and cost are explicitly visible per logged request (only vendor docs cited), and no third-party corroboration of the observability UI.

   • [claimed-docs] “The Requests section displays summaries by project, API key, and a detailed log of all requests.”
   • [claimed-docs] “open the Logs page, where you can search by request ID, filter by model, provider, or status code, follow requests live, and open one reques…”
   • [claimed-docs] “The Usage section displays four metrics to help you monitor your AI Gateway activity.”
   • [claimed-docs] “Spend monitoring. Monitor your spending across different providers”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Vercel AI Gateway~partialprobed6/10

   The gateway is largely API-first: model access, provider routing, caching, BYOK, and even a keyless public models endpoint are confirmed to work programmatically (docs-1,2,9,15,25,27; probe-4). However, budgets, spend caps, and the detailed Requests/Logs dashboard are described only as UI features (docs-5,12,16,23,30) without documented API endpoints to set budgets or pull logs programmatically. Missing for 10: budgets/spend-cap management API, log/usage export API parity, team/key management API parity.

   • [claimed-docs] “One key, hundreds of models. Access models from multiple providers with a single API key”
   • [claimed-docs] “Unified API. Switch between providers and models with minimal code changes”
   • [claimed-docs] “You can use `order`, `only`, and `sort` in `providerOptions.gateway` to control which providers handle your requests, in what order, and how…”
   • [claimed-docs] “This endpoint requires no authentication and returns detailed information including model IDs, context windows, and pricing.”
   • [claimed-docs] “Query the models endpoint directly to get a JSON list of all available models with pricing and capabilities”
   • [claimed-docs] “you can pass provider credentials on a per-request basis using the byok option in providerOptions.gateway. This is useful when you need to u…”
   • [claimed-docs] “Spend monitoring. Monitor your spending across different providers”
   • [claimed-docs] “To cap how much your team, a project, an API key, or a team member can spend, set [budgets]”
   • [claimed-docs] “open the Logs page, where you can search by request ID, filter by model, provider, or status code, follow requests live, and open one reques…”
   • [probe] “PROBE keyless-endpoint: GET https://ai-gateway.vercel.sh/v1/models returned HTTP 200 application/json with an OpenAI-compatible {"object":"l…”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Vercel AI Gateway
   Vercel AI Gateway~partialcommunity5/10

   Vercel documents that the Logs page lets users export request/usage data as CSV or JSON, and its OpenAI-compatible API means you can point clients elsewhere with minimal rewrite, reducing lock-in. However, there's no evidence of a comprehensive account/data export (billing history, configs, keys) beyond request logs, and BYOK behavior tied to Vercel balance (comm-1) suggests some platform dependency remains. Missing for 10: full account/config data export, evidence of exporting all historical usage/billing data, and confirmation that BYOK/API keys are fully portable without gateway dependency.

   • [claimed-docs] “open the Logs page, where you can search by request ID, filter by model, provider, or status code, follow requests live, and open one reques…”
   • [claimed-docs] “You can use existing OpenAI client libraries, switch to AI Gateway with a URL change, and keep your current tools and workflows without code…”
   • [claimed-docs] “Point your existing OpenAI or Anthropic SDK at AI Gateway. Same calls, no rewrites.”
   • [claimed-docs] “You can use the AI Gateway's Chat Completions API with existing tools and libraries like the OpenAI client libraries and AI SDK. Point your …”
   • [community] “If I bring my own Anthropic/OpenAI key and have usage available, why does Vercel's account balance determine whether my request executes? (V…”

   proof ↗⚑ flag

   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

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

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

   Vercel AI Gateway is a closed, proprietary hosted service; no evidence in the pack points to any open-source repository or open license for its source code — all evidence is documentation and API endpoints, not source availability.

   ⚑ flag

   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

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

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

   No evidence of region/data-residency controls or storage location choices in the AI Gateway docs; the pack covers routing, failover, pricing, and observability but nothing about where data is stored or processed. Missing for 10: any mention of regional data residency options, storage location controls, or compliance certifications addressing data locality.

   ⚑ flag

   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

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

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

   No evidence in the pack addresses data-training opt-out policies, zero-retention agreements, or any explicit statement that prompts/outputs are excluded from model training; the docs focus on routing, pricing, and observability instead. Missing for 10: any privacy policy or training-opt-out statement, zero-data-retention terms, provider-level data-use guarantees.

   ⚑ flag

   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

3. ai-native userControl data retention and deletion

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

   No evidence in the pack addresses data retention policies, log/data deletion controls, or retention configuration for requests/prompts processed through AI Gateway; observability docs mention logging/exporting requests but nothing about retention duration or deletion mechanisms.

   ⚑ flag

   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

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

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

   No evidence of any telemetry opt-out or privacy/data-collection controls; the gateway's observability features are about logging usage for the account owner, not about disabling tracking. Missing for 10: any documented telemetry opt-out setting, privacy policy on data retention/training use, or way to disable request logging.

   ⚑ flag

   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

Fallbacks

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

   weight 3 · round drawn
   Vercel AI Gateway✓fullclaimed9/10

   Docs explicitly describe automatic retries to other providers on failure, plus fine-grained control via `order`, `only`, and `sort` in providerOptions.gateway, per-provider timeouts for fast failover, and even BYOK-to-system-credential fallback — directly matching the fallback/routing-resilience story. This is well-documented first-party capability with concrete configuration options, though missing for 10: independent hands-on verification that fallback behaves correctly in production scenarios.

   • [claimed-docs] “High reliability. Automatically retries requests to other providers if one fails”
   • [claimed-docs] “You can use `order`, `only`, and `sort` in `providerOptions.gateway` to control which providers handle your requests, in what order, and how…”
   • [claimed-docs] “You can set per-provider timeouts to trigger fast failover when a provider is slow to respond.”
   • [claimed-docs] “If a query using your credentials fails, AI Gateway will retry the query with its system credentials to improve service availability.”
   • [claimed-docs] “You can use order, only, and sort in providerOptions.gateway to control which providers handle your requests, in what order, and how they ar…”
   • [claimed-docs] “AI Gateway routes requests, manages fallbacks and budgets, monitors usage, and connects supported coding agents.”

   proof ↗⚑ flag

   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

Load balancing

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

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

   Docs confirm ordering/sorting by performance or cost metric (`order`, `only`, `sort`), per-provider timeouts for fast failover, and automatic retries/fallbacks to other providers — covering latency- and cost-based routing and failover. However, explicit weight-based load balancing across providers/deployments/keys is not documented, and there's no evidence of key-level load balancing beyond BYOK fallback to system credentials. missing for 10: explicit weighted load-balancing configuration, per-key routing/balancing control, independent verification of routing behavior under load.

   • [claimed-docs] “You can use `order`, `only`, and `sort` in `providerOptions.gateway` to control which providers handle your requests, in what order, and how…”
   • [claimed-docs] “You can set per-provider timeouts to trigger fast failover when a provider is slow to respond.”
   • [claimed-docs] “You can also use `sort` to rank providers by a performance or cost metric. The gateway sorts providers by the chosen metric and tries them i…”
   • [claimed-docs] “High reliability. Automatically retries requests to other providers if one fails”
   • [claimed-docs] “If a query using your credentials fails, AI Gateway will retry the query with its system credentials to improve service availability.”

   proof ↗⚑ flag

   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

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
   Vercel AI Gateway~partialcommunity7/10

   Docs show routing rules via providerOptions.gateway (order, only, sort, timeouts) that let requests fail over across providers by availability/latency, plus cost/spend visibility and budgets, which supports policy-driven switching. However, there's no explicit evidence of dynamic mid-task capability-based switching or agent-driven runtime policy changes beyond static config, and community evidence flags BYOK requests being blocked once account balance hits $0, undermining pure availability-based routing in some cases. missing for 10: explicit support for capability-based (not just cost/availability) routing rules, evidence of an agent dynamically changing models mid-task at runtime, and independent confirmation that failover/ordering works reliably in production.

   • [claimed-docs] “You can use `order`, `only`, and `sort` in `providerOptions.gateway` to control which providers handle your requests, in what order, and how…”
   • [claimed-docs] “You can set per-provider timeouts to trigger fast failover when a provider is slow to respond.”
   • [claimed-docs] “You can also use `sort` to rank providers by a performance or cost metric. The gateway sorts providers by the chosen metric and tries them i…”
   • [claimed-docs] “High reliability. Automatically retries requests to other providers if one fails”
   • [claimed-docs] “To cap how much your team, a project, an API key, or a team member can spend, set [budgets]”
   • [community] “If I bring my own Anthropic/OpenAI key and have usage available, why does Vercel's account balance determine whether my request executes? (V…”

   proof ↗⚑ flag

   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

Rate limits

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

   weight 2 · round to Cloudflare AI Gateway
   Vercel AI Gateway~partialclaimed4/10

   The gateway supports failover/retry across providers, per-provider timeouts for fast failover, and ordering/sorting of providers (docs-3, docs-9, docs-10, docs-13, docs-20, docs-29), which can mitigate a single provider's rate limits by shifting traffic elsewhere. However, there's no documented mechanism for spreading load across multiple API keys for the same provider, nor any explicit request queuing/throttling feature to smooth bursts against rate limits. Missing for 10: multi-key load balancing, explicit request queuing/throttling controls, and any rate-limit-specific documentation or independent verification.

   • [claimed-docs] “High reliability. Automatically retries requests to other providers if one fails”
   • [claimed-docs] “You can use `order`, `only`, and `sort` in `providerOptions.gateway` to control which providers handle your requests, in what order, and how…”
   • [claimed-docs] “You can set per-provider timeouts to trigger fast failover when a provider is slow to respond.”
   • [claimed-docs] “If a query using your credentials fails, AI Gateway will retry the query with its system credentials to improve service availability.”
   • [claimed-docs] “You can also use `sort` to rank providers by a performance or cost metric. The gateway sorts providers by the chosen metric and tries them i…”

   proof ↗⚑ flag

   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

Retries

1. platform engineerSet automatic retry policies for transient provider errors

   weight 2 · round drawn
   Vercel AI Gateway✓fullclaimed8/10

   Docs explicitly describe automatic failover/retry to other providers on failure (docs-3), configurable provider ordering/fallback with `order`, `only`, `sort` (docs-9, docs-29), per-provider timeouts to trigger fast failover (docs-10), and even automatic retry with system credentials when BYOK fails (docs-13). This directly covers automatic retry policies for transient provider errors. Missing for 10: no independent/hands-on confirmation of retry behavior in production, and no explicit documentation of configurable retry counts/backoff intervals distinct from provider ordering.

   • [claimed-docs] “High reliability. Automatically retries requests to other providers if one fails”
   • [claimed-docs] “You can use `order`, `only`, and `sort` in `providerOptions.gateway` to control which providers handle your requests, in what order, and how…”
   • [claimed-docs] “You can set per-provider timeouts to trigger fast failover when a provider is slow to respond.”
   • [claimed-docs] “If a query using your credentials fails, AI Gateway will retry the query with its system credentials to improve service availability.”
   • [claimed-docs] “You can also use `sort` to rank providers by a performance or cost metric. The gateway sorts providers by the chosen metric and tries them i…”

   proof ↗⚑ flag

   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

Streaming

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

   weight 3 · round to Vercel AI Gateway
   Vercel AI Gateway~partialclaimed5/10

   The gateway advertises full OpenAI/Anthropic SDK compatibility and AI SDK integration (docs-7, docs-18, docs-28, docs-31), and since streaming is a standard capability of those client libraries, it is implicitly supported when pointing existing clients at the gateway's base URL. However, no evidence explicitly documents streaming/token-by-token responses, SSE support, or shows this working across all providers. Missing for 10: explicit docs on streaming endpoints/parameters, hands-on confirmation of token-by-token streaming across multiple providers, and any independent verification.

   • [claimed-docs] “You can use existing OpenAI client libraries, switch to AI Gateway with a URL change, and keep your current tools and workflows without code…”
   • [claimed-docs] “Point your existing OpenAI or Anthropic SDK at AI Gateway. Same calls, no rewrites.”
   • [claimed-docs] “You can use the AI Gateway's Chat Completions API with existing tools and libraries like the OpenAI client libraries and AI SDK. Point your …”
   • [claimed-docs] “Move existing OpenAI, Anthropic, and AI SDK integrations to AI Gateway with a base URL swap.”

   proof ↗⚑ flag

   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

Tool calling

1. developerRequest structured JSON-schema outputs across providers

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

   The evidence describes unified APIs, OpenAI-compatibility, provider routing, embeddings, and observability, but nowhere mentions structured JSON-schema/response_format output support or how it is normalized across different providers. Missing for 10: any documentation of JSON-schema/structured-output support, cross-provider schema normalization, or examples using response_format/json_schema.

   ⚑ flag

   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

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

   weight 3 · round to Vercel AI Gateway
   Vercel AI Gateway✓fullprobed8/10

   Vercel AI Gateway supports a unified API/schema (OpenAI-compatible and AI SDK) that lets developers call tools/functions across many providers with consistent code, including an explicit ToolLoopAgent example with tool calling, provider routing/fallback, and no-rewrite compatibility with existing OpenAI/Anthropic clients. missing for 10: independent hands-on verification of cross-provider tool-call schema consistency (e.g., confirming tool-calling behaves identically across Anthropic/OpenAI/other models) and any documented edge cases or limitations in function-calling parity across providers.

   • [claimed-docs] “Unified API. Switch between providers and models with minimal code changes”
   • [claimed-docs] “You can use existing OpenAI client libraries, switch to AI Gateway with a URL change, and keep your current tools and workflows without code…”
   • [claimed-docs] “Point your existing OpenAI or Anthropic SDK at AI Gateway. Same calls, no rewrites.”
   • [claimed-docs] “const agent = new ToolLoopAgent({ model: 'anthropic/claude-sonnet-5', tools: { getWeather: tool({”
   • [claimed-docs] “You can use the AI Gateway's Chat Completions API with existing tools and libraries like the OpenAI client libraries and AI SDK. Point your …”
   • [probe] “PROBE keyless-endpoint: GET https://ai-gateway.vercel.sh/v1/models returned HTTP 200 application/json with an OpenAI-compatible {"object":"l…”

   proof ↗⚑ flag

   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

Catalog

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

   weight 2 · round to Vercel AI Gateway
   Vercel AI Gateway✓fullprobed9/10

   Docs explicitly describe a models endpoint returning model IDs, context windows, and pricing with no authentication required, and a probe independently confirms the live unauthenticated /v1/models endpoint returns a full JSON model catalog. This directly satisfies browsing/querying a model catalog with pricing and context-window metadata. Missing for 10: no evidence of a dedicated visual browsing UI/dashboard for the catalog beyond the API and docs page.

   • [claimed-docs] “This endpoint requires no authentication and returns detailed information including model IDs, context windows, and pricing.”
   • [claimed-docs] “Query the models endpoint directly to get a JSON list of all available models with pricing and capabilities”
   • [probe] “PROBE keyless-endpoint: GET https://ai-gateway.vercel.sh/v1/models returned HTTP 200 application/json with an OpenAI-compatible {"object":"l…”

   proof ↗⚑ flag

   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

Compatibility

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

   weight 3 · round to Vercel AI Gateway
   Vercel AI Gateway✓fullprobed9/10

   Vercel explicitly documents OpenAI-compatible Chat Completions API where developers just swap the base URL and key with existing OpenAI SDKs, with no code rewrites, and a probe confirms the gateway serves an OpenAI-compatible /v1/models JSON response. Community evidence around BYOK balance behavior is unrelated to base-URL compatibility, so it doesn't dispute this. Missing for 10: independent third-party hands-on confirmation of a full migration beyond Vercel's own docs/probes.

   • [claimed-docs] “You can use existing OpenAI client libraries, switch to AI Gateway with a URL change, and keep your current tools and workflows without code…”
   • [claimed-docs] “Point your existing OpenAI or Anthropic SDK at AI Gateway. Same calls, no rewrites.”
   • [claimed-docs] “You can use the AI Gateway's Chat Completions API with existing tools and libraries like the OpenAI client libraries and AI SDK. Point your …”
   • [claimed-docs] “Move existing OpenAI, Anthropic, and AI SDK integrations to AI Gateway with a base URL swap.”
   • [probe] “PROBE keyless-endpoint: GET https://ai-gateway.vercel.sh/v1/models returned HTTP 200 application/json with an OpenAI-compatible {"object":"l…”

   proof ↗⚑ flag

   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

One endpoint

1. developerCall many model providers through one consistent API

   weight 3 · round drawn
   Vercel AI Gateway✓fullprobed9/10

   Extensive first-party docs describe a single unified API/key across hundreds of providers, OpenAI-compatible client support, and provider routing/fallback controls, and a live probe confirms the OpenAI-compatible /v1/models endpoint works unauthenticated. There is a minor community-reported caveat about BYOK requests being blocked when Vercel balance hits $0, which slightly limits the 'bring your own key' flow but doesn't contradict the core unified-API story. Missing for 10: independent hands-on developer confirmation of multi-provider switching in production beyond docs and one probe.

   • [claimed-docs] “One key, hundreds of models. Access models from multiple providers with a single API key”
   • [claimed-docs] “Unified API. Switch between providers and models with minimal code changes”
   • [claimed-docs] “You can use existing OpenAI client libraries, switch to AI Gateway with a URL change, and keep your current tools and workflows without code…”
   • [claimed-docs] “Point your existing OpenAI or Anthropic SDK at AI Gateway. Same calls, no rewrites.”
   • [claimed-docs] “You can use the AI Gateway's Chat Completions API with existing tools and libraries like the OpenAI client libraries and AI SDK. Point your …”
   • [probe] “PROBE keyless-endpoint: GET https://ai-gateway.vercel.sh/v1/models returned HTTP 200 application/json with an OpenAI-compatible {"object":"l…”
   • [community] “If I bring my own Anthropic/OpenAI key and have usage available, why does Vercel's account balance determine whether my request executes? (V…”

   proof ↗⚑ flag

   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