GetBindu /Bindu
Bindu: The identity, communication, and payments layer for AI agents.
★ 9,982⑂ 665👁 20⑃ 528● 77▤ 19
-4
Daily
9,982
stars
665
forks
20
watchers
528
prs
77
issues
19
releases
README
Bindu
English |
Deutsch |
Español |
Français |
हिंदी |
বাংলা |
中文 |
Nederlands |
Bahasa Indonesia |
தமிழ்
The identity, communication, and payments layer for AI agents.
A Gmail-shaped inbox for the agent internet. Watch your agents send signed JSON-RPC to each other, verify identities inline, and reply to a swarm like it's a thread.
→ Open the inbox walkthrough
Here's the situation. You built an agent. It works. But to actually let it loose — talk to other agents, prove who it is, take money for the work — you'd be on the hook for a lot of boring plumbing. A DID library to integrate. An OAuth flow to set up. Payment middleware. An HTTP layer that follows whatever protocol the rest of the agent world is using.
Bindu is all of that plumbing, behind one function call. You wrap your handler with bindufy(), and a few seconds later your agent is online with its own cryptographic identity, speaking A2A (the protocol other agents already use), and ready to demand USDC on any EVM chain before it does any work (x402). Your handler stays as small as (messages) - response. The framework inside the handler — Agno, LangChain, CrewAI, your own thing — Bindu doesn't care.
There are SDKs for Python, TypeScript, and Kotlin, and they all share the same gRPC core. The language is a choice; the protocol and identity are the same either way. When you're ready to go deeper, the docs are the next stop.
Installation
You'll need Python 3.12+ and uv.
bash
uv add bindu
If you're hacking on Bindu itself rather than using it:
bash
git clone https://github.com/getbindu/Bindu.git
cd Bindu
uv sync --dev
To run the examples you'll need an API key for at least one LLM provider — OPENROUTER_API_KEY, OPENAI_API_KEY, or MINIMAX_API_KEY.
Quickstart
Build the agent you want, hand it to bindufy(), and it's online. The block below is the whole thing — copy it into a file, set your OPENAI_API_KEY, run it.
python
import os
from bindu.penguin.bindufy import bindufy
from agno.agent import Agent
from agno.models.openai import OpenAIChat
from agno.tools.duckduckgo import DuckDuckGoTools
agent = Agent(
instructions="You are a research assistant.",
model=OpenAIChat(id="gpt-4o"),
tools=[DuckDuckGoTools()],
)
config = {
"author": "[email protected]",
"name": "research_agent",
"description": "Research assistant with web search.",
"deployment": {"url": "http://localhost:3773", "expose": True},
"skills": ["skills/question-answering"],
}
def handler(messages: list[dict[str, str]]):
return agent.run(input=messages)
bindufy(config, handler)
The agent is now live at http://localhost:3773. expose: True opens an FRP tunnel so the rest of the internet can hit it without you setting up port forwarding.
TypeScript equivalent
typescripTop issues
#144[Feature]: X402 Payments - Production Mainnet10 comments · 2026-02-12#261Minor code cleanup and small improvements8 comments · 2026-02-25#48[Feature]: DSPY integration7 comments · 2025-12-12#439[Feature]: ScopeBlind Receipt Extension for Verifiable Agent Actions6 comments · 2026-04-04#348[Feature]: Add Integration Tests for Payment Flows5 comments · 2026-03-07#208[Feature]: Add gRPC transport support for Bindu agent runtime5 comments · 2026-02-19#146[Feature]: mTLS Support - Secure Agent Communication5 comments · 2026-02-12#561[Feature]: Add CrewAI example agent4 comments · 2026-05-22
Discussions
#585Integration with custom AI agents0 comments · 2026-06-20#584Verifiable record-of-being-right as a complement to identity + payments (verify-before-pay)0 comments · 2026-06-20#574How does Bindu's communication layer compare to WAMP's RPC + PubSub + Federated Routing model?1 comments · 2026-06-02#420Bindu is featured on Shypd — 80K+ AI tools0 comments · 2026-03-30#118Contribution in an open source project!1 comments · 2026-01-25#117Contribution in an open source project!0 comments · 2026-01-25#27Adding Skills to the package0 comments · 2025-10-23
Latest release
2026.22.4: x402 settle-first + scenario hardening 2026.22.4 2026-05-28Release: x402 settle-first + scenario hardening ==================================================== Version: 2026.22.4 Date: May 28, 2026 Author: Raahul Dutta OVERVIEW -------- This release closes issue 562 — the verify-vs-settle gap in Bindu's x402 payment middleware — in two steps. First (563): a failed settlement no longer delivers the artifact. The worker now gates artifact delivery on settle success, and persists the EIP-3009 nonce, full authorization, and network on every failed-settle path so an operator can reconcile against the chain instead of seeing only str(e) buried in metadat