Agent-to-agent negotiation enables autonomous agents to coordinate, negotiate terms, and reach agreements for collaborative task execution. This protocol extension allows agents to propose, counter-propose, accept, or reject collaboration terms in a structured manner.Documentation Index
Fetch the complete documentation index at: https://docs.getbindu.com/llms.txt
Use this file to discover all available pages before exploring further.
Implementation status (2026-05): types only, no runtime endpoints.
NegotiationProposal, NegotiationContext, NegotiationStatus, and NegotiationSessionStatus exist as TypedDicts/enums in bindu/common/protocol/types.py, but there are no JSON-RPC methods for negotiation/* and no server handlers driving the state transitions. The schemas are stable enough to plan against; the dispatch logic is not yet wired up.Agents that need ad-hoc coordination today can carry these payloads inside DataPart content on regular message/send calls — the structure is well-defined, the routing is just up to your application.NegotiationProposal
A structured negotiation proposal exchanged between agents during the negotiation process. Schema:NegotiationContext
Context details for managing the complete lifecycle of agent-to-agent negotiations, including all participants and proposals. Schema:Negotiation Flow Pattern
Understanding how agents negotiate and reach agreements: Basic Negotiation Flow: Multi-Agent Negotiation Flow: Negotiation Statuses (Individual Proposals):proposed- Initial offer made, awaiting responseaccepted- Offer accepted, ready to proceedrejected- Offer declined, negotiation path closedcountered- Counter-offer made, negotiation continues
initiated- Negotiation session startedongoing- Active negotiation in progresscompleted- Agreement reached, all parties alignedrejected- Negotiation failed, no agreement possible