Platform / Core

One call. Many parameter sets.

An agent that needs the same query across fifty parameter sets should not run fifty calls and reconcile them by hand. swarmsDB fans a single request out across the whole set, runs it on a schedule if you want one, and delivers the results back to you as signed webhooks.

schedule: "0 6 * * *" → webhook: hmac-signed

Swarm phase Delivery — streaking flight: one gathered cloud fanned out to many destinations, looping back on a schedule.

01

One call, many parameter sets

Submit a single request that fans out across a list of parameter sets — every province, every indicator, every symbol — instead of orchestrating a loop of calls yourself. The fan-out happens server-side.
02

Put it on a schedule

Attach a cron schedule and the fan-out runs on its own cadence. This is not a promise on paper: a scheduled batch has run overnight and fired on time, on schedule, without anyone watching it.
03

Results by signed webhook

When a run completes, its events are delivered to your endpoint as HMAC-signed webhooks — so you verify the payload came from us and react to results as they land, rather than polling for them.

# claude_desktop_config.json — no API key changes hands
{ "mcpServers": {
    "swarmsdb": { "url": "https://app.swarmsdb.ai/mcp" }
} }

grant

{ "key_material": null,
  "grant": "workspace-bound",
  "revocable": true }

curl https://app.swarmsdb.ai/data/openalex/works \
  -H "Authorization: Bearer $SWARMSDB_KEY" \
  -G --data 'search=graph neural networks' \
     --data 'select=id,doi,title,cited_by_count'

typed section

{ "shape": "table", "rows": 25,
  "fields": ["id", "doi", "title", "cited_by_count"] }

# one call, many parameter sets — results by signed webhook
POST /bulk/requests
{ "endpoint": "eurostat/data",
  "params": ["nrg_bal_c", "demo_gind", "prc_hicp"],
  "schedule": "0 6 * * *" }

queued

{ "bulk_request_id": "brq_9f2c…",
  "webhook": "hmac-signed" }

upstream 8,457,367 → 1,508 chars

More in this area

Built for agentsWhy an autonomous agent runs leaner here — less context, typed data, a brake.Typed sectionsProject the fields you need — only those cross the wire.MCP & RESTConnect an agent over MCP, or call the REST surface directly.Keyless OAuth connectorsA third party connects by grant. No API key changes hands.Org controls chainThe enforced chain — org → workspace → api_key — members configure it, the backend holds it on the serving path.Members & workspacesTwo levels of role — org and workspace — enforced on the write path.Keys & restrictionsScope a key to the providers, rate, origins and region it may use.Data residencyPin data to a region — validated, immutable, expand-only.

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.

Connect now See how it works

One call, many parameter sets

Put it on a schedule

Results by signed webhook

Point one agent at it.