---
id: "action-use-integration-middleware"
type: "action-item"
source_timestamps: ["00:11:35", "00:12:29"]
tags: ["engineering", "integrations"]
related: ["concept-layer-4-tools", "concept-n-x-m-integration-problem", "entity-composio"]
action: "Use managed middleware (like Composio) instead of hand-rolling custom API connectors for agents."
outcome: "Bypass the N x M integration nightmare, saving massive amounts of time on OAuth, rate limits, and schema maintenance."
sources: ["s52-orchestration-layer"]
sourceVaultSlug: "s52-orchestration-layer"
originDay: 52
---
# Action: Adopt Integration Middleware

## Action
Use managed middleware (such as [[entity-composio]]) instead of hand-rolling custom API connectors for agents.

## Why
Without middleware you walk straight into the [[concept-n-x-m-integration-problem]]: every builder independently manages OAuth, credentials, rate limits, error parsing, and schema-change maintenance for every tool. At enterprise scale this is unsustainable.

Managed middleware reduces complexity from **N × M to N + M** (see [[concept-layer-4-tools]]).

## Expected outcome
Bypass the N × M integration nightmare, saving massive amounts of time on OAuth, rate limits, and schema maintenance. Engineering effort moves from glue code to core agent logic.

## Caveat
If [[entity-model-context-protocol]] (MCP) achieves universal adoption, proprietary middleware value diminishes — but enterprise fragmentation makes managed middleware durable for years.