One

One is agent infrastructure: a control plane that connects AI agents to third-party applications without a bespoke integration for each one. It provides managed OAuth across hundreds of apps, reached through a universal CLI or an MCP server, plus multi-step flows, scheduling and a large open-source skills library. It was previously called Pica. The problem it targets is the unglamorous half of agent work — tokens, refresh, scopes, per-vendor quirks — which is where most agent projects stall.

We track it rather than run it. It sits on our list as the answer for when an agent must act across many accounts we do not own and we would rather not carry the authorisation plumbing.

Composio occupies almost the same ground — pick whichever tool catalogue covers your targets better. Zapier has the widest app coverage in the category and an MCP surface, so choose it when reach matters more than control. n8n if you want to self-host the orchestration and own the runtime. Nango if all you actually need is OAuth token management rather than a whole agent layer, and Merge or Paragon if the integrations are for your customers rather than your own agents. One is the wrong call for a project with three integrations — write those yourself. It earns its place when integration count is the bottleneck.