Bindu Agent Infrastructure

What does this agent do, and when should you use it?

Bindu is a development and runtime layer that combines A2A JSON-RPC communication, DID identity, OAuth2 authorization, mTLS transport, and x402 payments for AI agents. Developers pass an existing handler to bindufy(), which exposes operations such as message/send, tasks/get, and message/stream on port 3773 while preserving a simple (messages) -> response application boundary. Python, TypeScript, and Kotlin SDKs share the same gRPC core so that protocol behavior, identity, and authentication remain consistent across languages. Bindu can wrap implementations built with Agno, LangChain, CrewAI, LangGraph, AG2, Hermes Agent, or custom code, and it supports model providers that expose OpenAI- or Anthropic-compatible APIs. Its deployment boundary spans a local server, an optional FRP public tunnel, and a bindu deploy agent.py --runtime=boxd path to a microVM. The repository also includes a Gateway for fleet orchestration, an operator inbox, storage and scheduling components, notifications, and observability integrations.

A developer registers the agent's author, name, description, deployment URL, and skills through bindufy(config, handler). Bindu receives A2A JSON-RPC requests before the application handler and can apply three checks: mTLS with certificates issued by step-ca, OAuth2 authorization through Ory Hydra introspection, and an Ed25519 DID signature over the canonical JSON body. After validation, it invokes the supplied Agno, LangChain, CrewAI, custom, or other supported handler and returns the result through the A2A task model; callers can poll tasks/get, use streaming messages, or receive push notifications. With x402 enabled, Bindu can require USDC payment before the handler runs, with five EVM networks preconfigured. Its Gateway uses a planner model to coordinate a fleet over A2A and stream the combined result, while Postgres stores tasks and messages and Redis supports retries, timeouts, and recurring work. expose: true creates an FRP tunnel, and bindu deploy can ship an agent script to a boxd microVM and return an HTTPS endpoint.

1. A team with an existing Agno, LangChain, CrewAI, or custom handler that needs A2A endpoints, identity, and authorization without rewriting its core agent.
2. A multi-agent system builder that needs agents to delegate work and negotiate price, latency, and SLA before execution.
3. An operator selling analysis, advisory, or processing services who wants to require an x402 USDC payment before the handler consumes resources.
4. A commercial team that wants public callers to see a generic capability while exposing detailed private skill descriptions only to allowlisted partner DIDs.
5. A developer demonstrating an agent from a laptop who needs a public endpoint without configuring router port forwarding.
6. A polyglot organization running Python, TypeScript, and Kotlin agents that should share the same DID, authentication rules, and A2A protocol.

How do you install or deploy this agent?

The Python package requires Python 3.12+ and uv:

uv add bindu

To work on Bindu itself:

git clone https://github.com/getbindu/Bindu.git
cd Bindu
uv sync --dev

Repository examples require at least one model-provider credential: OPENROUTER_API_KEY, OPENAI_API_KEY, or MINIMAX_API_KEY. The documented contributor setup uses:

git clone https://github.com/getbindu/Bindu.git
cd Bindu
uv venv --python 3.12.9 && source .venv/bin/activate
uv sync --dev
pre-commit run --all-files

How do you use this agent?

This is the documented first Python agent. Set OPENAI_API_KEY and run the file; it serves on http://localhost:3773, while expose: True opens an FRP tunnel.

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)

Send the first A2A JSON-RPC request with:

curl -X POST http://localhost:3773/ \
  -H 'Content-Type: application/json' \
  -d '{
    "jsonrpc": "2.0",
    "method": "message/send",
    "id": "<uuid>",
    "params": {
      "message": {
        "role": "user",
        "kind": "message",
        "parts": [{"kind": "text", "text": "Hello"}],
        "messageId": "<uuid>",
        "contextId": "<uuid>",
        "taskId": "<uuid>"
      }
    }
  }'

Poll tasks/get with the same taskId until its state is completed. For a hosted deployment, the documented command is:

bindu deploy agent.py --runtime=boxd

What are this agent's strengths and limitations?

How does this agent compare with similar options?

Key facts side by side with the most closely related agents.

How does FollowAgents rate this agent?

Recent releases

Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.

1. 2026.22.4 2026.22.4: x402 settle-first + scenario hardening 2026-05-28
   Release notes excerpt

   Release: 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 …

   View on GitHub ↗
2. 2026.20.7 2026.20.7: bindu-communication Inbox and Secured Outbound A2A 2026-05-17
   Release notes excerpt

   Release: bindu-communication Inbox and Secured Outbound A2A Version: 2026.20.7 Date: May 17, 2026 OVERVIEW -------- This release ships bindu-communication, an operator inbox for watching agent-to-agent traffic, together with the authentication and observability work that lets it talk to Hydra-protected peers end-to-end. The inbox is a three-pane Gmail-shape surface backed by SQLite that stitches outbound sends, agent webhooks, and gateway plan traces into one conversation per A2A context_id. Outbound calls are now JWT-bearer plus DID-signed using the operator's personal agent as …

   View on GitHub ↗
3. v2026.12.5 v2026.12.5: Document Analyzer & Reliability Improvements 2026-03-19
   Release notes excerpt

   Release: Document Analyzer & Reliability Improvements Version: 2026.12.5 Date: March 19, 2026 OVERVIEW -------- Maintenance and feature release focused on document analysis, payment robustness, scheduler and storage reliability, and usability improvements across the UI and configuration. This release also introduces a DSPy agent example, structured LangGraph workflow integration, and multiple accessibility and documentation enhancements contributed by the community. PROBLEM SOLVED -------------- Before this release: …

   View on GitHub ↗

FAQ