Inferensys

Glossary

Agent Communication Language (ACL)

An Agent Communication Language (ACL) is a formal language with defined syntax, semantics, and pragmatics that enables autonomous software agents to exchange information, knowledge, and requests.
Developer working on RAG retrieval system, document chunks visible on screen, technical workspace with code editor.
AGENT COORDINATION PATTERNS

What is Agent Communication Language (ACL)?

A formal language enabling autonomous agents to exchange knowledge and coordinate actions.

An Agent Communication Language (ACL) is a formal language with precisely defined syntax, semantics, and pragmatics that enables heterogeneous autonomous software agents to exchange information, knowledge, and requests. It provides the foundational grammar for speech acts, such as informing, requesting, or promising, allowing agents to engage in structured dialogues. The Foundation for Intelligent Physical Agents (FIPA) established the most prominent standard, FIPA ACL, which is often paired with a content language like FIPA SL to express the actual message payload.

The core purpose of an ACL is to ensure semantic interoperability between potentially disparate agents by providing a shared, unambiguous protocol for interaction. This is distinct from lower-level transport protocols, focusing instead on the meaning and intended effect of messages. ACLs enable advanced coordination patterns like negotiation, auctions, and cooperative problem-solving, forming the communication backbone of multi-agent systems where agents must collaborate or compete to achieve individual or collective goals.

AGENT COMMUNICATION LANGUAGE

Core Components of an ACL

An Agent Communication Language (ACL) is a formal language enabling autonomous agents to exchange information. Its core components define the structure, meaning, and rules of agent conversations.

01

Communicative Acts

The fundamental units of an ACL message, based on Speech Act Theory. Each act performs an action through communication.

  • Inform: Assert a proposition believed to be true (e.g., inform(sender, receiver, price=50)).
  • Request: Ask another agent to perform an action.
  • Propose: Submit an offer during a negotiation.
  • CFP (Call for Proposals): Solicit bids, as used in the Contract Net Protocol.
  • Accept/Reject: Respond to a proposal or request.

These acts define the illocutionary force—the speaker's intent—of a message.

02

Message Content

The payload of a communicative act, representing the information exchanged. Content must be expressed in a separate Content Language that all participating agents understand.

  • Syntax: Often uses a knowledge representation language like KIF (Knowledge Interchange Format) or FIPA-SL.
  • Semantics: The meaning of the content expression must be unambiguous.
  • Example: In inform(sender, receiver, (price stock-A 50)), the content (price stock-A 50) is a proposition in KIF stating a fact.
03

Message Envelope

A wrapper containing the metadata necessary for message delivery and processing in a distributed system. It is separate from the communicative act and its content.

  • Sender/Receiver: Agent identifiers.
  • Message ID: Unique identifier for the message and for linking replies (via in-reply-to).
  • Protocol: The Interaction Protocol governing this conversation (e.g., fipa-contract-net).
  • Ontology: References the shared ontology that defines the vocabulary for the content.
  • Encoding & Transport Details: Specifies how the content is serialized (e.g., string, XML) and transport mechanism (e.g., HTTP, IIOP).
04

Interaction Protocols

Pre-defined, structured sequences of communicative acts designed to achieve a specific coordination goal. They define the legal flow of conversation.

  • Request Protocol: A simple request followed by agree/refuse and then failure/inform-done.
  • Contract Net Protocol: A complex protocol involving cfp, propose, accept-proposal, reject-proposal, and inform.
  • Auction Protocols: Define sequences for English, Dutch, or Vickrey auctions.
  • Specification: Often modeled as finite state machines or using Agent UML sequence diagrams.
05

Content Language & Ontology

Two layers that give meaning to the data inside a message.

Content Language: The formal syntax for expressing propositions, actions, or objects (e.g., KIF, RDF, FIPA-SL). It provides the grammatical structure.

Ontology: A shared conceptualization. It defines the vocabulary (terms like 'Price', 'Stock'), their types, properties, and relationships. An ontology reference in the message envelope allows agents to map terms to a common understanding, which is critical for semantic interoperability.

COMPARISON

ACL Standards and Frameworks

A comparison of formal standards and influential frameworks for Agent Communication Languages, detailing their core communication model, semantic grounding, and typical application context.

Feature / AspectFIPA ACL (Standard)KQML (Influential Predecessor)MCP (Modern API-Focused)Custom/Internal DSL

Defining Body / Origin

Foundation for Intelligent Physical Agents (FIPA)

DARPA Knowledge Sharing Initiative

OpenAI (Model Context Protocol)

Individual organization or research project

Core Communication Model

Speech acts (communicative acts) with formal semantics

Speech acts (performatives) with less formal semantics

Function calls and structured data exchange

Varies; often request-response or event-driven

Primary Semantic Grounding

Precisely defined semantics based on modal logic (belief, desire, intention)

Largely pragmatics-based; semantics often left to agent implementation

Semantics defined by the function schema and execution result

Defined by the internal system ontology and rules

Standard Message Structure

Defined envelope with fields for sender, receiver, performative, content, language, ontology

Similar performative-content structure, but less standardized envelope

Structured JSON objects following a defined schema for tools/context

Proprietary format (e.g., JSON, XML, Protobuf with custom fields)

Native Support for Negotiation Protocols

Requires a Shared Ontology

Typical Transport Layer

Any (e.g., HTTP, IIOP, direct TCP); defined by FIPA agent platform specs

Any (often TCP sockets)

HTTP/HTTPS, WebSockets

Varies (often message queues, gRPC, internal buses)

Primary Use Case

Open, heterogeneous multi-agent systems requiring verifiable interaction

Early knowledge-sharing and information brokering systems

Tool/API calling and context management for LLM-based agents

Closed, homogeneous systems with optimized internal communication

Runtime Discovery & Directory Services

Integrated (via FIPA Agent Management and DF services)

Often required as a separate component (e.g., Facilitators)

Formal Conformance Testing

AGENT COORDINATION PATTERNS

Frequently Asked Questions

Agent Communication Language (ACL) is the formal foundation for agent-to-agent interaction. These FAQs address its core principles, standards, and practical implementation.

An Agent Communication Language (ACL) is a formal language with precisely defined syntax, semantics, and pragmatics that enables autonomous software agents to exchange information, make requests, and coordinate actions. It works by standardizing the structure and meaning of messages, ensuring that agents with different internal architectures can understand each other. An ACL message is not just data; it is a communicative act (or speech act) that performs an action, such as informing, requesting, or promising. The most prominent standard is the FIPA ACL (Foundation for Intelligent Physical Agents Agent Communication Language), which defines a set of performatives (message types), a content language, and interaction protocols. Agents communicate by exchanging these structured messages over a transport protocol, allowing for complex, goal-directed dialogues like negotiations and task delegations.

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.