Providers
Learn how to add, configure, and manage agent providers in BeeAI
Fundamental breaking changes are happening now, affecting protocol, transport, and APIs. Consider this version experimental. Join Alpha discussions to help shape it.
Overview
A provider is a process that exposes one or more agents using the Agent Communication Protocol. This guide explains how to register different types of providers with BeeAI.
Adding providers
You can manage providers by using the CLI:
Parameters
Either SHORT ID
or unique short name such as official/beeai-framework
A path to the provider manifest detailed below. Some examples:
https://github.com/org/repo
(remote location)https://github.com/org/repo@version-tag#path=/sub/directory/custom-provider.yaml
(GitHub location with a specific version-tag and path within the github repository)file:///absolute/path/to/beeai-provider.yaml
(local filesystem)
Provider manifest
The provider manifest (beeai-provider.yaml
) defines how a provider connects to BeeAI. The platform uses it to start a new provider process.
Below is the list of supported providers.
Python provider
Node.js provider
Container provider
This provider requires Docker, Podman or similar runtime installed, we recommend Rancher Desktop.
Unmanaged provider
An unmanaged provider is a special case where the BeeAI platform does not manage the provider’s lifecycle. Instead, you register an already running provider.
This is useful for:
- Local development
- Running agents on a separate infrastructure
For example, if you’re running an agent server locally (e.g., by cloning the provider template and executing uv run beeai-agents
), you can register it using the following manifest: