Add bindu to AI and Agents > Orchestration

[raahulrahl]

Entry

- [bindu](https://github.com/getbindu/Bindu) - A framework that wraps any agent handler with DID-based cryptographic identity, A2A JSON-RPC over HTTP, OAuth2 auth, x402 (USDC) payments, and a built-in operator inbox.

Justification

Acceptance criterion: Rising Star.

Bindu is a Python framework that gives autonomous AI agents the boring-plumbing layer they all reinvent — cryptographic identity (DIDs over Ed25519), the A2A protocol other agents already speak, OAuth2 via Ory Hydra, and pay-per-call billing using Coinbase's x402 standard on EVM chains. You wrap a handler with bindufy() and the agent comes online as a self-contained HTTP service with its own identity.

It belongs in AI and Agents > Orchestration alongside crewai, langchain, pydantic-ai, ag2, and openai-agents — but unlike those, Bindu is framework-agnostic at the handler layer (Agno, LangChain, CrewAI, custom code all work) and adds the inter-agent transport + identity + payment layer they don't ship.

Quality requirements

• Python-first: 67% Python, 33% TypeScript (SDK + inbox UI). Core runtime is Python.
• Active: last push today, 2026.20.7 release shipped 2026-05-17.
• Stable: production releases since v0.1.0 (May 2025); on PyPI as bindu.
• Documented: full docs at https://docs.getbindu.com plus an inbox walkthrough.
• Unique: only Python agent framework I know of that ships DID identity + A2A protocol + x402 payments in one piece; the existing orchestration entries don't cover identity or payment.
• Established: repo created 2025-03, first release 2025-05.

Rising Star evidence

• 6,200+ GitHub stars
• First release v0.1.0 in May 2025 — under 12 months ago
• 377 forks
• Active community on Discord, daily commits