Bindu
Bindu: The identity, communication, and payments layer for AI agents.
Giving an existing agent handler a cryptographic identity, A2A messaging and payment collection by wrapping it, whichever framework runs inside.
You do not want crypto payment rails; charging for work is built around requesting USDC on an EVM chain through x402.
About Bindu
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.
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.
Bindu is an open-source project written primarily in Python, with 9.8k stars on GitHub. It was last updated in September 2026.
uv add bindu
