Skip to main content
Layer researchIntegration fabric

Vendor landscape

As of 2026-08-19. All vendor capability claims are vendor-published unless a third-party source appears in sources.md. Maturity states carry dates; this layer converges fast, re-verify quarterly.

Categories at this layer

  1. Dedicated MCP gateways: purpose-built proxies for agent tool traffic (allowlisting, credential injection, tool-description integrity, elicitation mediation, audit).
  2. API management incumbents with MCP capability: existing gateways extended to route, authorize, and auto-generate MCP tools from managed APIs.
  3. iPaaS platforms pivoting agentic: connector estates repositioned as agent tool catalogs.
  4. RPA platforms pivoting agentic: bot estates gaining reasoning layers.
  5. Event streaming platforms: the trigger fabric for ambient agents.
  6. Inter-agent protocol infrastructure: A2A implementations and agent discovery/identity projects.

Vendor map

Agent-washing watch

  • "MCP support" without an authentication story (no OAuth resource-server behavior, no token exchange): treat as a demo, not a capability.
  • Connector catalogs relabeled as "agent tools" with no per-tool authorization or audit.
  • Orchestration products marketed as agents; Gartner estimates only ~130 of thousands of self-described agentic vendors are real (Jun 2025).

What rolls up to Phase 7

This layer contributes the clearest convergence story for the vendor-by-layer matrix: incumbents absorbed the new protocol within a year, so the buy decision is mostly "extend what you govern" vs "add a specialized enforcement point", not a new platform bet. Lock-in surfaces to track: private tool catalogs and their metadata, gateway policy configuration, and per-vendor auth extensions ahead of the standards.


Source: research/R03-integration-fabric/vendors.md in the evidence repository behind this site.

On this page