solace-agent-mesh 0.1.3__tar.gz → 0.2.0__tar.gz

solace_agent_mesh-0.2.0/.dockerignore

@@ -0,0 +1,17 @@
+*.pyc
+*.pyo
+*.pyd
+__pycache__
+.pytest_cache
+.env*
+.env
+.env_template
+docker-compose-local.yaml
+Makefile
+venv
+.venv
+.git*
+*.log
+project_notes.txt
+*.trace
+trace_*

solace_agent_mesh-0.2.0/.github/workflows/ci.yaml

@@ -0,0 +1,33 @@
+name: Continuous Integration
+
+on:
+  pull_request:
+  push:
+    branches:
+      - main
+
+permissions:
+  repository-projects: read
+  contents: write
+  id-token: write
+  packages: write
+  checks: write
+  pull-requests: write
+
+jobs:
+  ci:
+    uses: SolaceDev/solace-public-workflows/.github/workflows/hatch_ci.yml@main
+    with:
+      min-python-version: "3.11"
+      max-python-version: "3.13"
+      whitesource_product_name: "solace-agent-mesh"
+      whitesource_config_file: "wss-unified-agent.config"
+      npm_package_path: web-visualizer
+      node_version: 20
+      npm_lock_file: package-lock.json
+    secrets:
+      SONAR_TOKEN: ${{ secrets.SONARQUBE_TOKEN }}
+      SONAR_HOST_URL: ${{ secrets.SONARQUBE_HOST_URL }}
+      WHITESOURCE_API_KEY: ${{ secrets.WHITESOURCE_API_KEY }}
+      MANIFEST_AWS_ACCESS_KEY_ID: ${{ secrets.MANIFEST_READ_ONLY_AWS_ACCESS_KEY_ID }}
+      MANIFEST_AWS_SECRET_ACCESS_KEY: ${{ secrets.MANIFEST_READ_ONLY_AWS_SECRET_ACCESS_KEY }}

solace_agent_mesh-0.2.0/.github/workflows/release.yml

@@ -0,0 +1,32 @@
+name: Release
+on:
+  workflow_dispatch:
+    inputs:
+      version:
+        type: choice
+        required: true
+        description: "Version bump type"
+        options:
+          - patch
+          - minor
+          - major
+
+permissions:
+  id-token: write
+  checks: write
+  contents: write
+  packages: write
+jobs:
+  release:
+    uses: SolaceDev/solace-public-workflows/.github/workflows/hatch_release_pypi.yml@main
+    with:
+      ENVIRONMENT: pypi
+      version: ${{ github.event.inputs.version }}
+      npm_package_path: web-visualizer
+      node_version: 20
+      npm_lock_file: package-lock.json
+      pypi-project: solace-agent-mesh
+
+    secrets:
+      COMMIT_KEY: ${{ secrets.COMMIT_KEY }}
+      PYPI_TOKEN: ${{ secrets.PYPI_TOKEN }}

solace_agent_mesh-0.2.0/.gitignore

@@ -0,0 +1,177 @@
+.notes
+test_configs/
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+*.trace
+trace_*
+.notes
+.DS_Store
+
+# JS
+solace-agent-mesh-web-visualizer/node_modules/
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+.env*
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+wip/
+.aider*
+solace-agent-mesh.yaml
+playground.py
+tmp

solace_agent_mesh-0.2.0/PKG-INFO

@@ -0,0 +1,209 @@
+Metadata-Version: 2.4
+Name: solace-agent-mesh
+Version: 0.2.0
+Summary: Solace Agent Mesh is an EDA AI-first platform powered by Solace
+Project-URL: homepage, https://github.com/SolaceLabs/solace-agent-mesh
+Project-URL: repository, https://github.com/SolaceLabs/solace-agent-mesh
+Project-URL: documentation, https://github.com/SolaceLabs/solace-agent-mesh/blob/main/docs/docs/index.md
+Author-email: Edward Funnekotter <edward.funnekotter@solace.com>, Greg Meldrum <greg.meldrum@solace.com>, Cyrus Mobini <cyrus.mobini@solace.com>
+License-File: LICENSE
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.11
+Requires-Dist: azure-identity~=1.17.1
+Requires-Dist: beautifulsoup4~=4.12.3
+Requires-Dist: boto3~=1.34.122
+Requires-Dist: build~=1.2.2.post1
+Requires-Dist: click~=8.1.7
+Requires-Dist: duckduckgo-search~=6.3.7
+Requires-Dist: flask-socketio~=5.4.1
+Requires-Dist: flask~=3.0.3
+Requires-Dist: html2text~=2024.2.26
+Requires-Dist: jq~=1.8.0
+Requires-Dist: kaleido~=0.1.0.post1; sys_platform == 'win32'
+Requires-Dist: kaleido~=0.2.1; sys_platform != 'win32'
+Requires-Dist: langchain-core~=0.3.0
+Requires-Dist: langchain~=0.3.0
+Requires-Dist: litellm~=1.51.3
+Requires-Dist: markitdown~=0.0.1a3
+Requires-Dist: microsoft-kiota-abstractions==1.9.0
+Requires-Dist: microsoft-kiota-authentication-azure==1.9.0
+Requires-Dist: microsoft-kiota-http==1.9.0
+Requires-Dist: microsoft-kiota-serialization-form==1.9.0
+Requires-Dist: microsoft-kiota-serialization-json==1.9.0
+Requires-Dist: microsoft-kiota-serialization-multipart==1.9.0
+Requires-Dist: microsoft-kiota-serialization-text==1.9.0
+Requires-Dist: msgraph-core~=1.1.2
+Requires-Dist: msgraph-sdk~=1.5.4
+Requires-Dist: mysql-connector-repackaged==0.3.1
+Requires-Dist: plotly~=5.24.1
+Requires-Dist: pyperclip~=1.9.0
+Requires-Dist: pytest-cov~=5.0.0
+Requires-Dist: pytest~=8.3.1
+Requires-Dist: python-dateutil==2.9.0.post0
+Requires-Dist: pyyaml~=6.0.1
+Requires-Dist: requests~=2.32.3
+Requires-Dist: ruamel-yaml~=0.18.6
+Requires-Dist: solace-ai-connector-rest~=0.0.2
+Requires-Dist: solace-ai-connector-slack~=0.0.1
+Requires-Dist: solace-ai-connector-web~=0.2.1
+Requires-Dist: solace-ai-connector~=1.0.2
+Requires-Dist: solace-pubsubplus~=1.9.0
+Description-Content-Type: text/markdown
+
+# Solace Agent Mesh
+
+[![License](https://img.shields.io/github/license/SolaceLabs/solace-agent-mesh)](https://github.com/SolaceLabs/solace-agent-mesh/blob/main/LICENSE)
+[![GitHub issues](https://img.shields.io/github/issues/SolaceLabs/solace-agent-mesh?color=red)](https://github.com/SolaceLabs/solace-agent-mesh/issues)
+[![GitHub pull requests](https://img.shields.io/github/issues-pr/SolaceLabs/solace-agent-mesh?color=red)](https://github.com/SolaceLabs/solace-agent-mesh/pulls)
+[![GitHub stars](https://img.shields.io/github/stars/SolaceLabs/solace-agent-mesh?style=social)](https://github.com/SolaceLabs/solace-agent-mesh/stargazers)
+[![PyPI - Version](https://img.shields.io/pypi/v/solace-agent-mesh.svg)](https://pypi.org/project/solace-agent-mesh)
+[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/solace-agent-mesh.svg)](https://pypi.org/project/solace-agent-mesh)
+
+- [Solace Agent Mesh](#solace-agent-mesh)
+   * [Installation](#installation)
+   * [Quick Start](#quick-start)
+   * [Why Use Solace Agent Mesh?](#why-use-solace-agent-mesh)
+   * [Next Steps](#next-steps)
+   * [Contributing](#contributing)
+   * [Authors](#authors)
+   * [Release Notes](#release-notes)
+   * [License](#license)
+
+The Solace Agent Mesh (SAM) is an open-source platform that tackles a fundamental challenge in modern AI development: while powerful AI models are readily available, the real complexity lies in connecting them to the data and systems where they can provide value. Data is often siloed across databases, SaaS platforms, APIs, and legacy systems, making it difficult to build AI applications that operate seamlessly across these boundaries. SAM provides a flexible foundation for AI applications where multiple agents can collaborate, each bringing their own specialized capabilities and data access. Whether you're an AI enthusiast experimenting with new models, or an enterprise developer building production systems, SAM gives you the tools to:
+
+- Connect AI agents to real-world data sources and systems.
+- Add SAM Gateways to provide event-based integrations or interactive UI connections.
+- Monitor and debug AI interactions in real-time.
+- Deploy solutions that scale from prototype to production.
+
+Rather than trying to be a monolithic AI platform, SAM focuses on being an excellent integration layer. It brings together specialized agents - whether they're using local databases, accessing cloud APIs, or interfacing with enterprise systems - and helps them collaborate to solve complex problems.
+
+Built on event-driven architecture technology from Solace, SAM provides the robust foundation needed for both experimental and production deployments.
+
+![Solace Agent Mesh Overview](./docs/static/img/Solace_AI_Framework_With_Broker.png)
+
+## Installation
+
+1. [Optional] Set up Python Virtual Environment using `virtualenv` and activate it
+
+```sh
+## Install virtualenv if not already installed
+python3 -m pip install --user virtualenv
+## Setup python virtual environment
+python3 -m venv venv
+## Activate virtual environment:
+### MacOS/Linux:
+source venv/bin/activate
+### Windows:
+venv/Scripts/activate
+```
+
+2. The following command installs the Solace Agent Mesh CLI in your environment:
+
+```sh
+pip install solace-agent-mesh
+```
+
+3. Run the following SAM CLI command (`solace-agent-mesh` or `sam`) to verify your installation:
+
+```sh
+solace-agent-mesh --version
+```
+
+## Quick Start
+
+To get started with Solace Agent Mesh, follow these steps:
+
+1. **Install the CLI**: Ensure `solace-agent-mesh` is installed.
+2. **Create a Project**:  
+    Follow the prompts to create your project.
+
+   ```sh
+   mkdir my-agent-mesh && cd my-agent-mesh
+   solace-agent-mesh init
+   ```
+
+   _Enable the REST API interface when prompted._
+
+3. **Build the Project**:
+
+   ```sh
+   solace-agent-mesh build
+   ```
+
+4. **Run the Project**:
+
+   ```sh
+   solace-agent-mesh run -e
+   ```
+
+   _(Use `-eb` to combine build and run steps.)_
+
+5. **Connect to the Web Interface**:
+
+   Open the web interface at [http://127.0.0.1:5001](http://127.0.0.1:5001) or with the port specified during `init`.
+
+6. **Send a REST Request**:
+
+   Try the system by sending a request to the REST API gateway interface.
+
+   ```sh
+   curl --location 'http://localhost:5050/api/v1/request' \
+   --header 'Authorization: Bearer None' \
+   --form 'prompt="What is the capital of France?"' \
+   --form 'stream="false"'
+   ```
+
+Learn about [Agents](https://solacelabs.github.io/solace-agent-mesh/docs/documentation/concepts/agents) and [Gateways](https://solacelabs.github.io/solace-agent-mesh/docs/documentation/concepts/gateways) to add more functionalities to your project.
+
+For full details, see the [Quick Start Guide](https://solacelabs.github.io/solace-agent-mesh/docs/documentation/getting-started/quick-start).
+
+## Why Use Solace Agent Mesh?
+
+Building production-ready AI applications presents unique challenges. While it's relatively easy to create AI prototypes, deploying them in enterprise environments requires solving complex problems around integration, scalability, and observability. The Solace Agent Mesh addresses these challenges through:
+
+- **Composable Architecture**: Start with a small number of agents and gateways. You can add more over time.
+
+- **Add Agents to Increase Capabilities**: Each new agent adds more capabilities to the system. Adding a new agent isn't additive - it is exponential. With each agent being able to enhance all other agents as they collaborate for more and more complex tasks.
+
+- **Add Gateways to Increase Use Cases**: Each new gateway opens up new use cases for the system. A new gateway can provide a new interface to the system, with a different system purpose and response rules.
+- **Event-Driven Design**: Built on proven event-driven architecture principles, providing complete decoupling of components. This makes the system highly flexible and resilient, while enabling real-time monitoring of every interaction.
+
+- **Enterprise-Ready**: Designed from the ground up for production deployments that incorporates the experience from Solace in building mission-critical distributed systems.
+
+## Next Steps
+
+Check [Solace Agent Mesh Documentation](https://solacelabs.github.io/solace-agent-mesh/docs/documentation/getting-started/introduction) to learn more about the Solace Agent Mesh.
+
+|                                                                                                                                                  |                                                                                    |
+| ------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------- |
+| [Components Overview](https://solacelabs.github.io/solace-agent-mesh/docs/documentation/getting-started/component-overview) | Learn about the components that make up the Solace Agent Mesh.                     |
+| [Gateways](https://solacelabs.github.io/solace-agent-mesh/docs/documentation/concepts/gateways)                             | Understand how gateways provide interfaces to the Solace Agent Mesh.               |
+| [Agents](https://solacelabs.github.io/solace-agent-mesh/docs/documentation/concepts/agents)                                 | Explore the agents that provide specialized capabilities in the Solace Agent Mesh. |
+| [Services](https://solacelabs.github.io/solace-agent-mesh/docs/documentation/concepts/services)                             | Learn about the services that facilitate interaction within the Solace Agent Mesh. |
+| [Plugins](https://solacelabs.github.io/solace-agent-mesh/docs/documentation/concepts/plugins)                               | Discover the plugins that extend the functionality of the Solace Agent Mesh.       |
+
+## Contributing
+
+Contributions are encouraged! Please read [CONTRIBUTING.md](CONTRIBUTING.md) for details on our code of conduct, and the process for submitting pull requests to us.
+
+You can report any issues by opening an issue on the GitHub repository.
+
+## Authors
+
+See the list of [contributors](https://github.com/SolaceLabs/solace-agent-mesh/graphs/contributors) who participated in this project.
+
+## Release Notes
+
+Check out the [CHANGELOG](CHANGELOG.md) for details on changes in each release.
+
+## License
+
+The Solace Agent Mesh is licensed under the Apache-2.0 license.
+
+See the [LICENSE](LICENSE) file for details.

solace_agent_mesh-0.2.0/README.md

@@ -0,0 +1,152 @@
+# Solace Agent Mesh
+
+[![License](https://img.shields.io/github/license/SolaceLabs/solace-agent-mesh)](https://github.com/SolaceLabs/solace-agent-mesh/blob/main/LICENSE)
+[![GitHub issues](https://img.shields.io/github/issues/SolaceLabs/solace-agent-mesh?color=red)](https://github.com/SolaceLabs/solace-agent-mesh/issues)
+[![GitHub pull requests](https://img.shields.io/github/issues-pr/SolaceLabs/solace-agent-mesh?color=red)](https://github.com/SolaceLabs/solace-agent-mesh/pulls)
+[![GitHub stars](https://img.shields.io/github/stars/SolaceLabs/solace-agent-mesh?style=social)](https://github.com/SolaceLabs/solace-agent-mesh/stargazers)
+[![PyPI - Version](https://img.shields.io/pypi/v/solace-agent-mesh.svg)](https://pypi.org/project/solace-agent-mesh)
+[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/solace-agent-mesh.svg)](https://pypi.org/project/solace-agent-mesh)
+
+- [Solace Agent Mesh](#solace-agent-mesh)
+   * [Installation](#installation)
+   * [Quick Start](#quick-start)
+   * [Why Use Solace Agent Mesh?](#why-use-solace-agent-mesh)
+   * [Next Steps](#next-steps)
+   * [Contributing](#contributing)
+   * [Authors](#authors)
+   * [Release Notes](#release-notes)
+   * [License](#license)
+
+The Solace Agent Mesh (SAM) is an open-source platform that tackles a fundamental challenge in modern AI development: while powerful AI models are readily available, the real complexity lies in connecting them to the data and systems where they can provide value. Data is often siloed across databases, SaaS platforms, APIs, and legacy systems, making it difficult to build AI applications that operate seamlessly across these boundaries. SAM provides a flexible foundation for AI applications where multiple agents can collaborate, each bringing their own specialized capabilities and data access. Whether you're an AI enthusiast experimenting with new models, or an enterprise developer building production systems, SAM gives you the tools to:
+
+- Connect AI agents to real-world data sources and systems.
+- Add SAM Gateways to provide event-based integrations or interactive UI connections.
+- Monitor and debug AI interactions in real-time.
+- Deploy solutions that scale from prototype to production.
+
+Rather than trying to be a monolithic AI platform, SAM focuses on being an excellent integration layer. It brings together specialized agents - whether they're using local databases, accessing cloud APIs, or interfacing with enterprise systems - and helps them collaborate to solve complex problems.
+
+Built on event-driven architecture technology from Solace, SAM provides the robust foundation needed for both experimental and production deployments.
+
+![Solace Agent Mesh Overview](./docs/static/img/Solace_AI_Framework_With_Broker.png)
+
+## Installation
+
+1. [Optional] Set up Python Virtual Environment using `virtualenv` and activate it
+
+```sh
+## Install virtualenv if not already installed
+python3 -m pip install --user virtualenv
+## Setup python virtual environment
+python3 -m venv venv
+## Activate virtual environment:
+### MacOS/Linux:
+source venv/bin/activate
+### Windows:
+venv/Scripts/activate
+```
+
+2. The following command installs the Solace Agent Mesh CLI in your environment:
+
+```sh
+pip install solace-agent-mesh
+```
+
+3. Run the following SAM CLI command (`solace-agent-mesh` or `sam`) to verify your installation:
+
+```sh
+solace-agent-mesh --version
+```
+
+## Quick Start
+
+To get started with Solace Agent Mesh, follow these steps:
+
+1. **Install the CLI**: Ensure `solace-agent-mesh` is installed.
+2. **Create a Project**:  
+    Follow the prompts to create your project.
+
+   ```sh
+   mkdir my-agent-mesh && cd my-agent-mesh
+   solace-agent-mesh init
+   ```
+
+   _Enable the REST API interface when prompted._
+
+3. **Build the Project**:
+
+   ```sh
+   solace-agent-mesh build
+   ```
+
+4. **Run the Project**:
+
+   ```sh
+   solace-agent-mesh run -e
+   ```
+
+   _(Use `-eb` to combine build and run steps.)_
+
+5. **Connect to the Web Interface**:
+
+   Open the web interface at [http://127.0.0.1:5001](http://127.0.0.1:5001) or with the port specified during `init`.
+
+6. **Send a REST Request**:
+
+   Try the system by sending a request to the REST API gateway interface.
+
+   ```sh
+   curl --location 'http://localhost:5050/api/v1/request' \
+   --header 'Authorization: Bearer None' \
+   --form 'prompt="What is the capital of France?"' \
+   --form 'stream="false"'
+   ```
+
+Learn about [Agents](https://solacelabs.github.io/solace-agent-mesh/docs/documentation/concepts/agents) and [Gateways](https://solacelabs.github.io/solace-agent-mesh/docs/documentation/concepts/gateways) to add more functionalities to your project.
+
+For full details, see the [Quick Start Guide](https://solacelabs.github.io/solace-agent-mesh/docs/documentation/getting-started/quick-start).
+
+## Why Use Solace Agent Mesh?
+
+Building production-ready AI applications presents unique challenges. While it's relatively easy to create AI prototypes, deploying them in enterprise environments requires solving complex problems around integration, scalability, and observability. The Solace Agent Mesh addresses these challenges through:
+
+- **Composable Architecture**: Start with a small number of agents and gateways. You can add more over time.
+
+- **Add Agents to Increase Capabilities**: Each new agent adds more capabilities to the system. Adding a new agent isn't additive - it is exponential. With each agent being able to enhance all other agents as they collaborate for more and more complex tasks.
+
+- **Add Gateways to Increase Use Cases**: Each new gateway opens up new use cases for the system. A new gateway can provide a new interface to the system, with a different system purpose and response rules.
+- **Event-Driven Design**: Built on proven event-driven architecture principles, providing complete decoupling of components. This makes the system highly flexible and resilient, while enabling real-time monitoring of every interaction.
+
+- **Enterprise-Ready**: Designed from the ground up for production deployments that incorporates the experience from Solace in building mission-critical distributed systems.
+
+## Next Steps
+
+Check [Solace Agent Mesh Documentation](https://solacelabs.github.io/solace-agent-mesh/docs/documentation/getting-started/introduction) to learn more about the Solace Agent Mesh.
+
+|                                                                                                                                                  |                                                                                    |
+| ------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------- |
+| [Components Overview](https://solacelabs.github.io/solace-agent-mesh/docs/documentation/getting-started/component-overview) | Learn about the components that make up the Solace Agent Mesh.                     |
+| [Gateways](https://solacelabs.github.io/solace-agent-mesh/docs/documentation/concepts/gateways)                             | Understand how gateways provide interfaces to the Solace Agent Mesh.               |
+| [Agents](https://solacelabs.github.io/solace-agent-mesh/docs/documentation/concepts/agents)                                 | Explore the agents that provide specialized capabilities in the Solace Agent Mesh. |
+| [Services](https://solacelabs.github.io/solace-agent-mesh/docs/documentation/concepts/services)                             | Learn about the services that facilitate interaction within the Solace Agent Mesh. |
+| [Plugins](https://solacelabs.github.io/solace-agent-mesh/docs/documentation/concepts/plugins)                               | Discover the plugins that extend the functionality of the Solace Agent Mesh.       |
+
+## Contributing
+
+Contributions are encouraged! Please read [CONTRIBUTING.md](CONTRIBUTING.md) for details on our code of conduct, and the process for submitting pull requests to us.
+
+You can report any issues by opening an issue on the GitHub repository.
+
+## Authors
+
+See the list of [contributors](https://github.com/SolaceLabs/solace-agent-mesh/graphs/contributors) who participated in this project.
+
+## Release Notes
+
+Check out the [CHANGELOG](CHANGELOG.md) for details on changes in each release.
+
+## License
+
+The Solace Agent Mesh is licensed under the Apache-2.0 license.
+
+See the [LICENSE](LICENSE) file for details.

solace_agent_mesh-0.2.0/cli/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.2.0"