| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| API management | Developer platform | 11% | 3 of 61 | 17% | 52 | accepted challenger | ▲+6Since September 2026: 7% → 12%, +6 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| API gateways | Developer platform | 2% | 6 of 66 | 3% | 36 | accepted challenger | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| API security platforms | Security operations | 0% | 80 of 93 | 100% | 1 | under 10 labels · led by Aikido Security at 12% |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| API management | 7% | 12% | ▲+6Since September 2026: 7% → 12%, +6 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 5 → 3 of 61 |
| API gateways | 0% | 0% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 8 → 6 of 66 |
| API security | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 80 of 93, unchanged |
Shares here are read over the models both editions asked, so they can differ by a point or two from the standing above, which counts every model in this edition.
The floor is 11 points of share, measured: how far the models move a leader on their own when the same questions are asked twice with nothing changed. A larger change is movement; a smaller one is noise, and both are shown. Movement is read over the twelve models both editions asked; GPT-6 Luna, Muse Glimmer 30B joined this edition and are in the standing but not yet in the comparison. How the floor is measured · The editions
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 1 | 3 | 2 | 0 | 6 |
| GPT-5.4 mini | 0 | 3 | 1 | 1 | 5 |
| Gemini 3.5 Flash | 0 | 3 | 3 | 1 | 7 |
| Perplexity Sonar | 1 | 1 | 1 | 1 | 4 |
| Grok 4.20 | 1 | 4 | 4 | 2 | 11 |
| Mistral Small | 1 | 0 | 4 | 1 | 6 |
| DeepSeek V4 Flash | 1 | 2 | 4 | 1 | 8 |
| Llama 4 Maverick | 0 | 0 | 2 | 0 | 2 |
| Qwen 3.7 Flash | 1 | 4 | 1 | 1 | 7 |
| Kimi K2 | 0 | 7 | 0 | 1 | 8 |
| GLM 4.7 FlashX | 0 | 2 | 2 | 0 | 4 |
| MiniMax M2.5 | 1 | 3 | 3 | 0 | 7 |
| GPT-6 Luna | 1 | 4 | 1 | 0 | 6 |
| Muse Glimmer 30B | 0 | 6 | 0 | 2 | 8 |
Verbatim evidence the judge attached to positive labels.
“I'd recommend Azure API Management if your team wants a strong all-around platform with a built-in developer portal” Perplexity Sonar · API management · paraphrase prompt · first choice
“Candidates like Kong Konnect, Tyk, Azure API Management, or Zuplo are often the right fit at this scale” DeepSeek V4 Flash · API management · scale prompt · first choice
“Choose Azure API Management if you're in the Microsoft ecosystem and want a managed, integrated solution.” Mistral Small · API management · direct prompt · first choice
“Kong and Azure API Management offer strong performance at lower total cost of ownership” Claude Haiku 4.5 · API management · direct prompt · first choice
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.
“Be cautious for scenarios requiring deep, vendor-agnostic governance and lifecycle management outside Microsoft cloud.” Muse Glimmer 30B · API management · negative prompt · soft negative
“Frequent breaking changes and retirements ... which can create upgrade fatigue and operational risk.” DeepSeek V4 Flash · API management · negative prompt · soft negative
“native cloud portals are notoriously difficult to customize and offer poor developer experiences” Gemini 3.5 Flash · API management · paraphrase prompt · soft negative
“be cautious if your primary cloud is AWS or GCP, because the management plane stays on Azure” Perplexity Sonar · API management · negative 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 220 of the 253 answers that named Azure API Management and are not a share of its labels.
607 of the 607 domain citations in answers naming Azure API Management 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.
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 Azure API Management'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 Azure API Management, 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 Azure API Management by email, built from the raw record of the edition. It shows:
Azure API Management is among the products AI models recommend first in API management this edition. Each badge says so in the buyer's words, names the edition, and links to the standing. The next edition issues a new badge; this one stays true as a record of October 2026.
Badges read on light and dark pages. Alt text carries the claim, the category, the edition and the index, so it stays a citation where the image does not load.