This section is the type-level truth. If you want to know what aDocumentation Index
Fetch the complete documentation index at: https://docs.getbindu.com/llms.txt
Use this file to discover all available pages before exploring further.
Task looks like on the wire, what states it can be in, or what an AgentCard actually contains, the answer is on one of the pages below.
What Bindu speaks
Bindu follows two open protocols and adds a handful of its own extensions.| Protocol | Version | What it covers |
|---|---|---|
| A2A (Agent-to-Agent) | v0.3.0 | The base layer — messages, tasks, agent cards, push notifications. Everything you need for one agent to call another. |
| AP2 (Agent Protocol 2) | v0.1.0 | Payment mandates and the trust framework that lets agents transact without a human in the loop. |
| Bindu extensions | — | Negotiation, credit accounting, trust levels. Marked <NotPartOfA2A> everywhere they appear. |
Pages
Types and enums
TaskState, TrustLevel, NegotiationStatus, IdentityProvider. The vocabulary.
Messages and parts
TextPart, FilePart, DataPart, Message vs Artifact — the shapes content can take.
Tasks and lifecycle
The Task object, its status, and how it moves between states.
Context management
ContextId, history sessions, multi-turn conversations.
Agent negotiation
Price, latency, SLA agreed up front. Bindu-specific.
Security and authentication
Auth schemes and how agents prove they’re allowed.
Push notifications
Webhook on task state change. Stop polling.
Payment and mandates
AP2 payment models and the mandate trust framework.
Credit system
Bindu’s credit accounting layer next to x402.
Trust and identity
TrustLevel, IdentityProvider, DID verification.
Agent card and discovery
AgentCard, AgentCapabilities, AgentInterface. How clients find you.
This is a reference, not a tutorial. If you’re trying to build an agent for the first time, go to Your first agent instead — you won’t need most of this until you’re three steps deeper.