| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| API management | Developer platform | 0% | 48 of 61 | 41% | 27 | criticized challenger | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| API gateways | Developer platform | 0% | 46 of 66 | 33% | 3 | 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. |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| API management | 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 39 → 48 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 35 → 46 of 66 |
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 | 0 | 0 | 1 | 1 | 2 |
| GPT-5.4 mini | 0 | 1 | 0 | 0 | 1 |
| Gemini 3.5 Flash | 0 | 1 | 0 | 1 | 2 |
| Perplexity Sonar | 0 | 0 | 0 | 1 | 1 |
| Grok 4.20 | 0 | 1 | 1 | 2 | 4 |
| Mistral Small | 0 | 0 | 1 | 1 | 2 |
| DeepSeek V4 Flash | 0 | 1 | 0 | 1 | 2 |
| Llama 4 Maverick | 0 | 0 | 1 | 0 | 1 |
| Qwen 3.7 Flash | 0 | 1 | 1 | 2 | 4 |
| Kimi K2 | 0 | 1 | 0 | 0 | 1 |
| GLM 4.7 FlashX | 0 | 1 | 1 | 2 | 4 |
| MiniMax M2.5 | 0 | 1 | 1 | 1 | 3 |
| GPT-6 Luna | 0 | 0 | 1 | 0 | 1 |
| Muse Glimmer 30B | 0 | 0 | 2 | 0 | 2 |
Verbatim evidence the judge attached to positive labels.
“Lite plan - 50,000 calls free per month... Cons: Limited calls in free tier” MiniMax M2.5 · API management · budget prompt · alternative
“If you need a solid on‑prem or hybrid enterprise gateway → IBM API Connect” GLM 4.7 FlashX · API management · comparative prompt · alternative
“Best for: regulated industries and security-heavy environments.” GPT-5.4 mini · API management · comparative prompt · alternative
“Best for: Hybrid integration & legacy/mainframe connectivity” Kimi K2 · API management · comparative 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.
“Avoid this platform if you expect massive traffic spikes or need to deploy frequently across hybrid environments.” GLM 4.7 FlashX · API management · negative prompt · hard negative
“often criticized for being complex, expensive, and less developer-friendly compared to modern alternatives” Mistral Small · API management · negative prompt · hard negative
“These are "significantly overbuilt" for early-stage API management and will cost time and money you don't need to spend.” Claude Haiku 4.5 · API management · negative prompt · soft negative
“rarely the heavy, enterprise-grade legacy suites (like Google Apigee, MuleSoft, or IBM API Connect)” Gemini 3.5 Flash · API management · 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 89 of the 93 answers that named IBM API Connect and are not a share of its labels.
283 of the 307 domain citations in answers naming IBM API Connect 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 IBM API Connect's own pages state, read September 28, 2026: ibm.com/products/api-connect, ibm.com/products/api-connect/demo, ibm.com/products/api-connect/manage, ibm.com/products/api-connect/secure, ibm.com/products/api-connect/create. 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 IBM API Connect'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 IBM API Connect, 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 IBM API Connect by email, built from the raw record of the edition. It shows: