Agent Text Transfer Protocol - ATTP
Last updated
Last updated
ATTP (Agent Text Transfer Protocol) is a robust networking infrastructure designed for seamless agent-to-agent communication. It encompasses essential components such as the Agent Registry, Agent Name Server (ANS), and the ATTP Protocol itself. Additionally, it ensures agent network security with features like the Agent Private Cloud (APC). The ecosystem facilitates efficient agent discovery, interaction, and communication using the ATTP protocol. Through ANS, agents can identify and connect with the most suitable counterpart for specific tasks or queries, ensuring a streamlined and secure communication process.
The ATTP network is composed of the following key components:
Client-Agent: This is the entry point for user queries. It extracts intent and entities from the input and initiates communication with the ANS.
Agent Name Server (ANS): Acts as a lookup service, querying the Agent Registry to resolve the intent into a specific agent UUID and its associated endpoint.
Agent Registry: A centralized repository storing agent metadata, including their UUIDs and capabilities.
Server-Agent: Processes queries received from the Client-Agent and generates appropriate responses.
Agent Private Cloud (APC): Ensures secure communication and isolated environments for sensitive agent interactions. Only agents that are part of a specific APC can communicate with each other. The APC UUID acts as an identifier for the secure network of agents
Architecture Diagram
The architecture of ATTP is depicted in the diagram below:
Intent Detection and Orchestration: Detects intent and orchestrates relevant intent handlers
Built in Core Capabilities: Has some common used built it capabilities to summarize any content, do sentiment analysis on text (reviews, emails) and provide basic chatbot functionality for world knowledge
Inter-Agent Communication: Facilitates real-time communication among agents across diverse systems using ATTP adaptor.
Scalability: Supports distributed processing, allowing multiple agents to work together to handle large-scale tasks.
Security: Ensures secure and authenticated data exchanges between agents using ATTP adaptor.
The main components of ATTP payload are:
Example: In the query “Find Italian restaurants near me,” the query text is “Find Italian restaurants near me”.
Example: For the query, “Find action movies with a rating above 8”, the intent is “recommend_movie”.
3. Entities: Key details or data points extracted from the query that helps fulfill the intent.
Example: In “Find action movies with a rating above 8”, entities include:
Type: “genre,” Value: “action”
Type: “rating,” Value: “8”
4. Metadata: Additional common context or supplementary information associated with the query and entities. This can include sessions details, timestamps, user preferences, user id, account id or device information.
Example: Metadata might include:
User ID: “user123”
Timestamp: “2025–01–22T12:34:56”
Device: “Mobile”
ATTP is the core communication protocol enabling text-based interactions between agents. It is designed to be lightweight, secure, and efficient. The protocol supports: ● Query exchange. ● Agent UUID resolution and endpoint discovery. ● Secure messaging between agents within the APC.
The ATTP protocol header includes the following fields:
Version: The version of the ATTP protocol.
Message Type: Specifies the type of message (e.g., Request, Response, or Error).
APC ID: The unique identifier of the Agent Private Cloud.
Client Agent UUID: The unique identifier of the client agent initiating the communication.
Server Agent UUID: The unique identifier of the server agent receiving the communication.
Message ID: ID of the message to identify communication.
Task ID: ID of the task to identify a task flow.
The body contains:
query_text: The user query or request for processing.
intent: High-level intent of the user query.
entities: Structured information extracted from the query text.
metadata: Contextual data supporting the query.
Intent Extraction: The Client-Agent receives a query, extracts the intent and entities, and prepares an ATTP request.
Intent Resolution via ANS: ○ The Client-Agent sends the intent to the ANS. ○ ANS queries the Agent Registry to find the corresponding agent UUIDand endpoint. ○ ANS returns the resolved UUID and endpoint to the Client-Agent.
Connection Establishment: ○ The Client-Agent establishes a connection with the resolved Server-Agent using the UUID and endpoint. ○ The ATTP request is sent to the Server-Agent. The request includes the APC ID, Agent UUID, and Auth Token in the header for authentication and security.
Query Processing: ○ The Server-Agent processes the request, generates a response, and sends it back to the Client-Agent.
Response Handling: ○ The Client-Agent receives the response and delivers it to the user.
The ATTP protocol provides a comprehensive framework for agent-to-agent communication. By leveraging ANS for efficient agent discovery and ATTP for secure messaging within the APC, it enables scalable and reliable interactions in distributed environments. This architecture is adaptable to various use cases, including automation, AI-driven workflows, and dynamic task allocation.