Loading 1,300+ connectors on demand.

Giving an agent "internet access" is the wrong abstraction. What an agent needs is the right data and the right actions, scoped and governed. The connector layer is how Open Swarm gives a bot exactly that — and no more.

One runtime, one contract

Every connector implements the same contract through a shared client. Auth, retries, and conformance are handled once, so applications integrate against a stable interface instead of bespoke glue per vendor. A connector either passes the conformance spec or it does not ship.

A marketplace, not a monolith

Over thirteen hundred public API specifications are staged for import into that runtime. They are not all loaded at boot — that would be enormous and pointless. Instead, dynamic tool loading brings a connector's tools into a bot's reach only when a task calls for it, then they go away again.

An honest number. "1,300+" counts public API specs staged for import. It does not mean 1,300 integrations are wired, tested, and live. The live, signed connectors — the ones behind trading, shopping, travel, and media — are a smaller, curated set. The catalog is the potential; the signed connectors are the proven.

Credentials stay with their owner

A token broker holds credentials per user and hands out scoped access. A connector reads or acts only on data its owner approved, and the access is attributable. This is what keeps "the swarm can reach 1,300 services" from being a liability instead of a feature.

Governed per agent

Every tool a connector exposes is governed per agent in auto, ask, or off modes, and every call records its cost in the central ledger. The result: broad reach, narrow blast radius, and a bill you can read.