Discover
List providers, list endpoints, read the sections an endpoint can return — the agent explores the catalogue by calling it, not by reading docs.
list_providers · list_endpoints · get_sections
Ecosystem / Orchestration
One toolset. The whole catalogue.
An agent does not learn 53 different APIs. It learns 14 typed
tools that reach the whole catalogue — 454 live endpoints — and drive discovery,
fetching, bulk fan-out and scheduling from inside its own workflow and workspace. The
surface stays the same whether the data behind it is a public provider or your own connector.
tools: 14 · providers: 53 · endpoints: 454 Swarm phase Delivery — the agent's hands: a small, typed toolset that steers sourcing, fan-out and scheduling across the catalogue.
The surface
Fourteen tools, not fifty-three integrations.
Every source in the catalogue answers to the same small toolset. Five tools discover and fetch — list the providers, list an endpoint's sections, pull a projected section, run a typed query. Nine more are the workbench: bulk fan-out, scheduled batches, and their lifecycle. An agent learns the surface once and reaches everything behind it, so adding a provider never means teaching the agent a new API.
The 53-provider, 454-endpoint catalogue is what these tools can reach — a surface, not a promise that every endpoint is equally battle-tested. Your own MCP connectors join it as first-class citizens on the same tools.
Fetch
Pull a projected section of an endpoint, or run a typed query. Only the fields the agent asked for cross the wire, already shaped.
get_section_data · query_data
Orchestrate
Fan one call out across many parameter sets, put it on a schedule, and manage the results — the workbench, so the agent drives sourcing from inside its own workspace.
create_bulk_request · create_batch · run_batch_now · …
Interoperability
Sourcing that lives in the agent's workflow.
The orchestration tools are not a separate console the agent has to leave for. A bulk request, a scheduled batch, a webhook subscription — all are created and managed through the same tools, bound to the agent's workspace, so data sourcing becomes a step in the loop rather than an integration project beside it.
Stated precisely: 14 tools is the count on the deployed gateway — five discovery and fetch tools always on, nine workbench tools behind a flag. Together they are the whole surface an agent needs to orchestrate its own data sourcing across the catalogue.
More in this area
Not a framework, a swarmWhy swarmsDB is an ecosystem — three swarm phases, phase for phase.Auger — curationThe framework that turns any API into a shape-typed, canary-guarded source.The data-network commonsA shared cache the swarm warms — and everyone rides. Warm it, pay less.Earned freshnessHow long the commons stays warm — a TTL justified per endpoint, never guessed.RAPI — routing intelA shared performance index your agent reads to steer its next call. In beta.
Point one agent at it.
Connect over MCP or REST. If your agents read more than one source, the context bill is the first thing you will see move.