Skip to main content

Swarms

Swarms — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Swarms — an AI/Agents | Infra project (API + marketplace) with tokenization on Solana, token (symbol: SWARMS).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: a platform and library for building and orchestrating autonomous “agents”, plus a marketplace of agents/prompts/tools.
  • Who it’s for: developers and teams that build and deploy agent systems.
  • Why onchain/token: the marketplace claims tokenization of agents/prompts on Solana (creation of tradable tokens); a separate SWARMS token exists, but its necessity for the product is not disclosed per Tier‑1.
  • What you can actually touch (Tier‑1): public product/marketplace pages (see links_* → App / Demo) and the SDK/framework repository (see links_* → GitHub).

How it works (very briefly)

  1. The user does: writes/assembles agent(s) via the SDK or API and runs a scenario.
  2. The system does: orchestrates execution (sequential/parallel/hierarchical workflows), calls LLM providers and tools, manages the runtime.
  3. The user gets: the finished result of a task/process (research, content generation, automation).
  4. Where the blockchain is: the marketplace claims optional tokenization of agents/prompts on Solana (minting a product token + bonding curve).
  5. Token role (if any): tokenization uses a fee in SOL; the role of the SWARMS token as a “mandatory” element of the product is not confirmed per Tier‑1.

Quick links: AI thesis fit

Project passport

Field Value
Project name Swarms
Also known as (aliases) The Swarm Corporation; SWARMS
Logo (logo) ../assets/120_swarms_logo.svg
Token symbol (ticker) SWARMS
Category AI/Agents | Infra
Primary chain (chain) Solana
Type non-EVM
Network status mainnet
Consensus (consensus) PoS (Solana)
Launch date (launch_date) —
Project status (status) active
Token (standard) SPL
Token contract 74SBV4zDXxTRgv1pEMoECskKBkZHc2yGPnc7GYVepump
Token model (token_type) unknown
Max supply 1,000,000,000 SWARMS (Tier‑3: CoinGecko)
Issuance — (no Tier‑1 found)
Tokenomics (tokenomics, brief) tokenization of agents/prompts in the marketplace is paid in SOL (fee 0.04 SOL)
Governance company (The Swarm Corporation)
Admins/keys —
Audit —
Bug bounty — (there are Security Advisories on GitHub)
Team (team) Kye Gomez + contributors (per GitHub)
Funding (investors/funding) —
AI component (ai_component) multi-agent orchestration (LLM + tools)
Use‑case (use_case) build, deploy + monetize agents
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 3 / 2 / 0 / 1
Last verified 2026-02-11

General project overview

Swarms is positioned as “production‑grade” infrastructure for the agent economy: an SDK/framework and API for building and running autonomous AI agents, as well as a marketplace where agents, prompts and tools can be published, discovered and monetized. Per Tier‑1 sources, the focus is on orchestrating multi‑agent workflows (parallel, sequential, hierarchical schemes), integrations with model providers, and the “economic” wrapper around agents (marketplace, monetization).

Features/modules

  • SDK/framework: agents, workflow structures (sequential/concurrent/hierarchical and others), integrations, examples.
  • Swarms API: API access to agents/runs (per the docs).
  • Swarms Marketplace: publishing/discovering agents, prompts and tools.
  • Tokenization (optional): issuing a token on Solana for an agent/prompt and trading via a bonding curve (per the marketplace docs).

Typical scenarios

  • Scenario 1: a developer assembles 1 agent → gets a runnable agent for a specific task (research, text generation, etc.).
  • Scenario 2: a team builds a multi‑agent pipeline (researcher → writer → reviewer) → gets an automated process with separation of roles.
  • Scenario 3: a creator publishes an agent/prompt to the marketplace → gets distribution/monetization; optionally, tokenizes the product on Solana.

Getting started (wallet/network)

  • What you need: an account/API key (for platform features) and/or installation of the swarms Python package.
  • Network/chain: a blockchain is required only for optional tokenization in the marketplace (Solana).
  • Fees: for tokenization — a fee of 0.04 SOL (Tier‑1: docs).

Architecture/tech (non‑AI)

  • Components: SDK/library (GitHub), documentation/API, web marketplace.
  • Participant roles: developers (create agents), users (use them), “vendors” (publish to the marketplace).
  • Where logic runs: orchestration and execution — offchain; tokenization of agents/prompts — onchain (Solana, per the marketplace docs).
  • Dependencies: LLM providers/tools (integrations), Solana (for tokenization).

Token/economics (expanded, no forecasts)

  • Token utility: per Tier‑1, tokenization in the marketplace is paid in SOL; the utility of the SWARMS token specifically (as a mandatory one) is not described in the available Tier‑1 sources.
  • Protocol necessity drivers: tokenization (Solana) is an optional marketplace feature; the SDK/platform can be used without onchain.
  • Who pays fees: the creator of a tokenized agent/prompt pays a fee of 0.04 SOL (Tier‑1).
  • Where fees go: the docs state it is to “cover blockchain transaction costs”; the distribution among beneficiaries is not disclosed.
  • Issuance/burn: for SWARMS — no Tier‑1 parameters; per Tier‑3 (CoinGecko), a supply of 1B is mentioned.
  • Security/incentive mechanisms: no public Tier‑1 mechanisms (staking/slashing) for SWARMS were found.
  • Distribution and token issuance schedule: no Tier‑1 found (for the SWARMS token).
  • Treasury: — (no Tier‑1 found).

Governance

  • Who makes decisions: the company/team (The Swarm Corporation) + the OSS community (per GitHub).
  • How protocol parameters change: via updates of the SDK/platform and documentation (releases/changelog).
  • Where decisions are discussed/made: GitHub issues/PRs, Discord.
  • Keys/multisig: — (not applicable/not disclosed).

Security and incidents

  • Audits: — (no Tier‑1 audits found).
  • Bug bounty: — (there is a Security Advisories section on GitHub).
  • Incidents: — (no public Tier‑1 postmortems found).
  • Threat model: risks of errors in agent orchestration/integrations with model providers, key/API leaks, and the risks of “marketing” tokenization without proven necessity.

Project status and timeline

  • Current status: the product is active (docs/marketplace are available).
  • Key releases/milestones: changes are recorded in the Changelog (date stream).
  • Roadmap: there is no separate Tier‑1 roadmap in the links; there is a changelog and articles/updates.

Ecosystem/integrations

  • Integrations: integrations with LLM providers/tools (per the docs/repository), Solana — for marketplace tokenization.
  • Partners: — (no specific partners are confirmed in the current Tier‑1 sources).
  • Where it’s actually used: as an SDK/framework (code examples and documentation) and as a marketplace (public web interface).

AI component of the project

  • What is real AI here? Orchestration of autonomous agents and multi‑agent workflows on top of LLM models/tools (SDK + API + examples).
  • What is truly onchain? Per the Tier‑1 marketplace docs, an agent/prompt can be tokenized: a token is issued on the Solana network and a bonding curve is used; the SPL token SWARMS (mint on Solana) also exists.
  • Why is a token needed? Tokenization of “products” in the marketplace is paid in SOL; the necessity/utility of SWARMS as an ecosystem token is not proven per Tier‑1.
  • Red flags (based on the information found): token‑washing (the token exists, but its Tier‑1 utility/necessity for the product is not disclosed), onchain‑washing (the onchain part looks like optional monetization rather than critical infrastructure), what to double‑check: official Tier‑1 pages on SWARMS utility/role.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity medium 2
Token necessity low 0
Evidence Tier‑1 partial 1
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): AI is described as an already working part of the product (see AI_1/AI_2), so AI_0 as “intent only” does not apply
  • Evidence: Tier‑1 — https://docs.swarms.ai/ , https://github.com/kyegomez/swarms
  • Why sufficient / why not (one line): there is a Tier‑1 product description and runnable SDK/framework examples
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the platform/SDK orchestrates autonomous agents and multi‑agent workflows on top of LLM models and tools
  • Evidence: Tier‑1 — https://docs.swarms.ai/ , https://github.com/kyegomez/swarms
  • Why sufficient / why not (one line): Tier‑1 contains a product description and the purpose of the components (“multi‑agent orchestration framework”, API docs)
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): the repository contains runnable agent/“swarm” examples and describes how to run them; the marketplace is publicly available
  • Evidence: Tier‑1 — https://github.com/kyegomez/swarms , https://swarms.world/
  • Why sufficient / why not (one line): there are concrete code examples and a public product interface (demo/app)
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there are no quantitative quality metrics/benchmarks in the available Tier‑1 sources
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 1
  • Claim (one line): there is public documentation and a codebase for the SDK/workflow structures (agents, sequential/concurrent/hierarchical and others)
  • Evidence: Tier‑1 — https://docs.swarms.ai/ , https://github.com/kyegomez/swarms
  • Why sufficient / why not (one line): documentation on the components and open code are available
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: SPL mint SWARMS: 74SBV4zDXxTRgv1pEMoECskKBkZHc2yGPnc7GYVepump
  • Evidence: Tier‑1 — https://docs.swarms.ai/docs/marketplace/tokenization_details ; Tier‑2 — https://solscan.io/token/74SBV4zDXxTRgv1pEMoECskKBkZHc2yGPnc7GYVepump
  • Why sufficient / why not (one line): Tier‑1 directly records Solana as the tokenization network; the token address is given in the explorer link
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 1
  • What useful logic is onchain: tokenization of agents/prompts on Solana + bonding curve/“graduation” mechanics for trading
  • Evidence: Tier‑1 — https://docs.swarms.ai/docs/marketplace/tokenization_details
  • Why sufficient / why not (one line): Tier‑1 describes the onchain process of issuance and market dynamics of tokenized products
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the product core (SDK/API) works offchain; without Solana, only the optional marketplace tokenization breaks down
  • Evidence: Tier‑1 — https://docs.swarms.ai/
  • Why sufficient / why not (one line): Tier‑1 positions the platform as a developer/API stack; onchain is described as a separate tokenization option
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, SWARMS (SPL)
  • Evidence: Tier‑2 — https://solscan.io/token/74SBV4zDXxTRgv1pEMoECskKBkZHc2yGPnc7GYVepump
  • Why sufficient / why not (one line): the token exists onchain (per the explorer link)
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): payment for services with the SWARMS token is not described in Tier‑1 (tokenization is paid in SOL)
  • Evidence: Tier‑1 — https://docs.swarms.ai/docs/marketplace/tokenization_details
  • Why sufficient / why not (one line): Tier‑1 explicitly specifies a fee in SOL, not a need for SWARMS
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 0
  • Claim (one line): no description of incentives/collateral via SWARMS was found in the available Tier‑1 sources
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there are no confirmed token incentive mechanics in Tier‑1
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance via SWARMS is not described in Tier‑1
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there are no Tier‑1 mentions of voting/a DAO for SWARMS
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): per Tier‑1, tokenization payments are made in SOL, and the product core (SDK/API) does not require SWARMS → the SWARMS token looks replaceable/optional
  • Evidence: Tier‑1 — https://docs.swarms.ai/docs/marketplace/tokenization_details , https://docs.swarms.ai/
  • Why sufficient / why not (one line): Tier‑1 describes tokenization as a SOL fee and does not record a critical role for SWARMS
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.swarms.ai/ product description (agent economy infrastructure), navigation across API/marketplace/examples
Tier‑1 https://docs.swarms.ai/docs/marketplace/tokenization_details tokenization of agents/prompts on Solana, fee in SOL, bonding curve mechanics
Tier‑1 https://github.com/kyegomez/swarms public code and runnable examples (Agent/Swarm), description of the framework
Tier‑2 https://solscan.io/token/74SBV4zDXxTRgv1pEMoECskKBkZHc2yGPnc7GYVepump SPL mint of the SWARMS token (address, onchain existence)
Tier‑3 https://www.coingecko.com/en/coins/swarms for reference: supply/market (not proof of utility)

No comments to display

Back to top