OpenViSTAI · Agents · Blockchain · Crypto
Menu
Agent Frameworks

Swarmauri SDK

Swarmauri SDK is an Apache-2.0 modular Python SDK and monorepo for composing typed AI-agent systems from interface contracts, reusable implementations, provider integrations and independently installable plugins. It includes package families for agents, chains, conversations, documents, LLMs, prompts, tools, parsers, embeddings, vector stores, signing, key providers, transports, middleware and storage.

Independent OpenViST project profile, based on linked sources.

Swarmauri SDK — OpenViST project profile in Agent Frameworks.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Swarmauri when an AI-agent project benefits from interface-first composition and separable Python packages, especially when it needs to combine models, tools, parsing, retrieval or workflow components without tying every part to one provider package.

Who it is for

  • Python developers building composable AI-agent applications
  • Teams integrating multiple LLM, tool, parser or retrieval components
  • Component authors creating reusable Swarmauri extensions
  • Self-hosted or server-side projects that need an extensible package architecture

Documented uses

  • Assemble typed agent applications from reusable contracts and implementations
  • Connect LLMs with tools, parsers and workflow components
  • Add retrieval capabilities through embeddings and vector stores
  • Create independently installable provider or component extensions
  • Keep imports and dependencies focused through namespace, foundational and package-specific distributions
Before you choose

Requirements & limits

The repository is public, active and licensed under Apache-2.0. Package metadata and repository badges target Python 3.10 through 3.14. Installation is documented through uv and pip.

  • Choose swarmauri for the public namespace, plugin discovery and curated optional dependency groups.
  • Choose swarmauri_core for interface contracts and add swarmauri_base when serialization, registration and reusable base behavior are needed.
  • Choose swarmauri_standard for first-party standard components.
  • Use focused packages when only a particular component family or provider integration is required.
  • The framework's modularity distributes functionality across packages, so the selected application components determine which dependencies must be installed.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Install the Swarmauri namespace and focused components

Set up the SDK with either the namespace package, curated bundle, foundational packages or selected component families.

Before you start

  • Python 3.10, 3.11, 3.12, 3.13 or 3.14
  • uv or pip
  • A Python project environment

Steps

  1. Install the namespace package with the command below or the command below.

    Documented command
    uv add swarmauri
    Documented command
    pip install swarmauri
  2. Install swarmauri[full] when the broader curated component bundle is needed.

  3. For component development, install swarmauri_core swarmauri_base.

  4. For a focused use case, install a package such as swarmauri_vectorstore_pinecone, swarmauri_tool_jupyterexportlatex or swarmauri_signing_ed25519.

Expected outcome

The selected Swarmauri packages are available for namespace discovery, component use or component development.

Guide limitations

  • The installation instructions identify package choices but do not document a complete agent deployment or provider configuration.
  • Focused packages provide only the component families they contain.
Source-based practical guide

Use direct and namespace imports

Access installed components through Swarmauri namespace discovery or narrow direct package imports.

Before you start

  • Installed Swarmauri packages
  • A Python interpreter

Steps

  1. Import swarmauri to activate namespace discovery for installed components.

  2. Use the public registry modules to inspect registered namespaces or plugin mappings.

  3. Use direct imports such as swarmauri_standard.documents and swarmauri_standard.tools when a narrow dependency surface is preferred.

  4. Use swarmauri_base component registration and dynamic serialization when defining extensible component types.

Expected outcome

Installed components can be accessed through the namespace or through direct package paths, and registered component mappings can be inspected.

Guide limitations

  • The examples demonstrate imports, registry inspection and component serialization rather than a complete production workflow.
  • Available components depend on the packages installed.
Evidence and transparency

Sources & review

Source record details
Source availability
Active
Sources checked
3 October 2026
Original website title
swarmauri/swarmauri-sdk · Official homepage title · retained in its source language