| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| API security platforms | Security operations | 2% | 15 of 93 | 0% | 2 | under 10 labels · led by Aikido Security at 12% | |
| API gateways | Developer platform | 0% | 17 of 66 | 14% | 7 | under 10 labels · led by Kong Gateway at 53% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-5.4 mini | 0 | 0 | 0 | 0 | 0 |
| Gemini 3.5 Flash | 1 | 0 | 1 | 0 | 2 |
| Perplexity Sonar | 0 | 0 | 0 | 0 | 0 |
| Grok 4.20 | 0 | 0 | 1 | 0 | 1 |
| Mistral Small | 0 | 0 | 0 | 0 | 0 |
| DeepSeek V4 Flash | 0 | 0 | 2 | 0 | 2 |
| Llama 4 Maverick | 0 | 0 | 1 | 0 | 1 |
| Qwen 3.7 Flash | 0 | 0 | 0 | 0 | 0 |
| Kimi K2 | 0 | 0 | 0 | 1 | 1 |
| GLM 4.7 FlashX | 0 | 0 | 0 | 0 | 0 |
| MiniMax M2.5 | 0 | 1 | 1 | 0 | 2 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 0 | 0 | 0 | 0 |
Verbatim evidence the judge attached to positive labels.
“If you are already on Cloudflare and want immediate, low-cost visibility: Go with Cloudflare API Gateway.” Gemini 3.5 Flash · API security · paraphrase prompt · first choice
“Best if you're cloud-native (AWS/Azure) - Cost-effective for smaller teams” MiniMax M2.5 · API security · paraphrase prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“Less full-featured for complex B2B API management” Kimi K2 · API gateways · direct prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 26 of the 28 answers that named Cloudflare API Gateway and are not a share of its labels.
Ninety-six of the ninety-six domain citations in answers naming Cloudflare API Gateway came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What Cloudflare API Gateway's own pages state, read September 28, 2026: blog.cloudflare.com/api-gateway, developers.cloudflare.com/ai-gateway, blog.cloudflare.com/workers-ai-gateway-unification, blog.cloudflare.com/tag/gateway, blog.cloudflare.com/tag/api-gateway. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Cloudflare API Gateway's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Cloudflare API Gateway, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Cloudflare API Gateway by email, built from the raw record of the edition. It shows: