Skip to main content

​
Welcome to Swarmd

Swarmd is a multi-agent orchestration platform. You bring the agent; Swarmd gives it an identity, decides who it may talk to, brokers those calls, and records them. Your agent never reaches a sub-agent, an MCP server, or an LLM provider directly. It talks to Swarmd, which checks the grant, forwards the call, and writes the audit row.

​
Where do you want to run it?

Same platform, same tiers, same licence. The only question is who operates it — and everything else in these docs reads the same either way.

Swarmd Cloud

We operate it. Uptime, patching and upgrades are ours. Sign up, register an agent, start building — nothing to deploy.

Self-hosted

You operate it, in your cluster. One Helm chart, your data, your network. For data residency, regulated workloads, or an existing Kubernetes estate. Talk to us for a licence.
Both are licensed and both are tiered — self-hosting is not a smaller product or a cheaper tier, it’s a decision about where the data sits and who carries the pager. Licences are issued per deployment, so self-hosting starts with a conversation.The SDKs and API reference apply identically to either. A self-hosted install is a complete Swarmd platform: point SWARMD_BASE_URL and SWARMD_TOKEN_URL at your own cluster and nothing else changes.

​
Then build

Build a Python agent

Three packages — the core SDK, a Google ADK wrapper, and a LangChain wrapper. Guided, end to end.

Call agents from an app

The TypeScript channel client, for front ends and backend services.

How it all works

Runtime, token audiences, subscriptions, MCP grants and refresh — the model behind every SDK call.

API reference

Every endpoint across the relay, registry, auth, audit, and payments services.

​
How it fits together

All requests go through the gateway at https://api.dev.swarmd.ai, which handles authentication, routing, and policy across:

Relay

Brokers agent-to-agent calls and MCP traffic. Enforces grants on every request.

Registry

Source of truth for agents, subscriptions, and MCP grants.

Tenant Auth

Tenants, users, identity providers, and the OAuth2 tokens your agent authenticates with.

Audit

Every hop, correlated end to end by a single trace id.

LLM Gateway

Routes model calls so completions are policy-checked and audited — and no provider key lives in your agent.

A2A Payments

Agent-to-agent payments via the x402 protocol.

​
Authentication

Every endpoint takes a bearer token:
Agents get theirs by exchanging their client credentials at the token endpoint — which the SDKs do for you. See two tokens, not one for why there’s more than one kind.