What is the Contract Net Protocol in multi-agent systems?

The Contract Net Protocol (CNP) is a task-allocation and negotiation method for multi-agent systems. An agent with work to distribute acts as a manager, announces the task to eligible agents, evaluates their bids, and awards the task to a suitable contractor. The roles describe a particular negotiation: an agent can be a contractor on one task and a manager for another.

Beginner-friendly example: Assigning API test-generation work

Suppose a testing platform needs to generate test cases for a payment endpoint, and three agents have different expertise and workloads.

1. Task announcement: The manager announces: “Generate negative tests for POST /payments by 5 PM; required skills are API validation and security testing.”
2. Bidding: An available security-testing agent offers to finish in 10 minutes; another qualified agent estimates 20 minutes; an overloaded agent declines.
3. Evaluation: The manager checks eligibility, capability, workload, estimated completion time, and quality constraints.
4. Award: The manager assigns the task to a suitable bidder and communicates the required deliverable.
5. Execution and reporting: The contractor generates tests and reports completion, failure, or a blocker. The manager validates the result.

Task announcement → Bids → Contractor selection → Award → Task execution

A “bid” is a structured offer to do the work; it need not involve money.

What are the main protocol messages?

• Task announcement: Describes the task, eligibility requirements, information expected in bids, and any deadline.
• Bid: Describes an agent's relevant capabilities or proposed terms.
• Award: Tells a chosen agent that it has been selected for the task.
• Result or status report: Communicates progress or completion; exact message types depend on the implementation.

In the classic formulation, the manager can broadcast to all, some, or one potential contractor, and bidding can be limited to eligible agents.

How does this differ from general agent negotiation?

General negotiation may involve many rounds of offers and counteroffers about shared resources or decisions. CNP is a more specific protocol for distributing tasks using announcements, bids, and awards. It can support decentralized coordination because different agents may initiate different contracts.

Practical implementation

For an agent workflow using LangGraph and Celery:

• Define a task ID, required skills, deadline, bid schema, and acceptance criteria.
• Let eligible workers provide capability, capacity, and estimated cost or time.
• Select using explicit scoring rules, not unsupported agent self-claims.
• Persist the award and use idempotent task IDs so retries do not create duplicate assignments.
• Set timeouts, contractor failure handling, and a safe rebidding policy.
• Verify deliverables independently before marking the contracted task complete.

Important: CNP describes coordination logic; it does not by itself guarantee optimal task allocation, trustworthy bids, or exactly-once execution.

When should it be used?

Use CNP when there are multiple eligible agents, their availability or capabilities change, and a task needs to be assigned dynamically. If there is only one obvious executor, direct routing is often simpler.

In short

The Contract Net Protocol lets agents distribute tasks through structured announcements, competitive bids, and explicit awards, making dynamic delegation easier to reason about and audit.

Foundational reference: Reid G. Smith, “The Contract Net Protocol: High-Level Communication and Control in a Distributed Problem Solver,” *IEEE Transactions on Computers* (1980), DOI: 10.1109/TC.1980.1675516.