Skip to content

Instantly share code, notes, and snippets.

Hyper Agent Protocol (HAP) - An Overview

What is HAP?

The Hyper Agent Protocol (HAP) is a new, simplified standard for how software "agents" (or any automated services and capabilities) communicate with each other over the web. Imagine a universal way for different software components to discover what other components can do and then ask them to do it, all using standard web technologies.

The goal of HAP is to make it much easier to build flexible, interoperable systems where different services, tools, or AI agents can work together seamlessly, regardless of how they are built internally.

Core Idea: Every Capability has a Web Address (URI)

@webr3
webr3 / mcp_a2a_comparison.md
Last active May 8, 2025 10:23
mcp_a2a_comparison

This document outlines the key functionalities of the Model Context Protocol (MCP) and the Agent-to-Agent (A2A) protocol, derived from their respective JSON schema definitions (schema.json for MCP, dated 2025-03-26, and a2a.json for A2A). It then presents a comparative table to identify common and unique functionalities and analyze interoperability.

Part 1: Model Context Protocol (MCP) Functionality

Derived from schema.json. MCP facilitates interactions between a "client" (e.g., an LLM-hosting environment or agent framework) and a "server" (providing tools, resources, or prompts).

Client-to-Server Request Methods:

  • initialize: Client initiates connection with the server, exchanging capabilities (ClientCapabilities, ServerCapabilities), protocol versions, and implementation information.
  • ping: Client sends to server to check liveness and ensure the connection is active.
  • resources/list: Client requests a list of available data resources from the server.