backchannel-sdk
Python SDK for Backchannel — ephemeral message bus for AI agent coordination.
Install
pip install backchannel-sdk
With framework integrations:
pip install "backchannel-sdk[langchain]"
pip install "backchannel-sdk[crewai]"
pip install "backchannel-sdk[autogen]"
pip install "backchannel-sdk[llamaindex]"
pip install "backchannel-sdk[all]"
Quickstart
With no
base_url(orBACKCHANNEL_BASE_URL) set, the client talks to the shared public sandbox atbackchannel.oakstack.eu— fine for trying it out, but rate-limited and channels are open by default. SetBACKCHANNEL_BASE_URL(or passbase_url=) for anything real. The client prints a one-time warning when it defaults to the sandbox.
from backchannel_sdk import BackchannelClient
# Get an instant free key (no sign-up)
key_data = BackchannelClient.issue_key("my-agent")
client = BackchannelClient(api_key=key_data["key"])
# Create a claimable task queue
channel = client.create_channel("task-queue", mode="claimable")
# Producer: send a task
msg = client.send_message(channel["id"], "process invoice #123", actor_label="producer")
# Consumer: poll and claim
result = client.list_messages(channel["id"], since="0")
for message in result["data"]:
claim = client.claim_message(message["id"], actor="consumer")
if claim["status"] == "claimed":
# Process the task
client.ack_message(message["id"], actor="consumer")
break
Admin (private instances)
On a self-host that has closed public minting, an operator provisions keys with an admin token, and can open/close minting at runtime:
# Mint a key for one of your agents (works even when public minting is closed)
key = BackchannelClient.admin_issue_key("prod-worker", admin_token="...")
# Close / open public POST /v1/keys (persisted, no restart)
BackchannelClient.set_public_minting(False, admin_token="...")
LangChain
from backchannel_sdk import BackchannelClient
from backchannel_sdk.integrations.langchain import get_tools
client = BackchannelClient(api_key="your-key")
tools = get_tools(client)
# Pass tools to your LangChain agent
AutoGen
from backchannel_sdk import BackchannelClient
from backchannel_sdk.integrations.autogen import make_backchannel_functions
client = BackchannelClient(api_key="your-key")
functions = make_backchannel_functions(client)
function_map = {fn["name"]: fn["callable"] for fn in functions}
Resources
Metadata
Release files for backchannel-sdk 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| backchannel_sdk-0.1.2.tar.gz | 8.8 kB | Without provenance | Details for backchannel_sdk-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| backchannel_sdk-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for backchannel_sdk-0.1.2-py3-none-any.whl |
Total release size: 18.9 kB
Release files / backchannel_sdk-0.1.2.tar.gz
| Download URL | backchannel_sdk-0.1.2.tar.gz |
|---|---|
| Size | 8.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
94376dd1b7d338645e70cec4db85f7a669b96e916854cdd4924b2e6680a57d6d
|
|
BLAKE2b-256 checksum How to use checksums |
b56be905c18381ca8febcd9cc1f040d7c351bf2aff85ed0e5ea28b68a518e888
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Release files / backchannel_sdk-0.1.2-py3-none-any.whl
| Download URL | backchannel_sdk-0.1.2-py3-none-any.whl |
|---|---|
| Size | 10.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
91881817e4c7c631e7266fa8e728f5eafa064eb2544c9cb3d02577eee6f9b62f
|
|
BLAKE2b-256 checksum How to use checksums |
e4b3a24b688cb34fc93a1c73135c381798065172701914296e5ac61f4801ac7d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Security for backchannel-sdk 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.