ZAP Protocol

ZAP (Zero-Copy App Proto) is a high-performance communication protocol for AI agents built on Cap'n Proto. It provides full MCP compatibility with 10-100x performance improvements, post-quantum security, and native support for 11 programming languages.

curl -fsSL https://hanzo.sh | sh && hanzo mcp launch zap

Why ZAP?

• Zero-Copy Performance — Cap'n Proto's zero-copy serialization eliminates parsing overhead
• MCP Compatible — Full backward compatibility with Model Context Protocol servers
• Post-Quantum Security — ML-KEM and ML-DSA cryptography for future-proof security
• Multi-Language — Native bindings for Rust, Go, Python, JavaScript, C++, and 6 more
• Agent Consensus — Built-in voting mechanism for multi-agent response aggregation
• W3C DID — Native decentralized identity support

Quick Example

interface Zap {
  init @0 (client :ClientInfo) -> (server :ServerInfo);
  listTools @1 () -> (tools :ToolList);
  callTool @2 (call :ToolCall) -> (result :ToolResult);
  listResources @3 () -> (resources :ResourceList);
  readResource @4 (uri :Text) -> (content :ResourceContent);
}

use zap_protocol::{Zap, ClientInfo};

#[tokio::main]
async fn main() -> Result<()> {
    let client = Zap::connect("zap://localhost:9000").await?;
    let info = client.init(ClientInfo::new("my-agent", "1.0.0")).await?;

    let tools = client.list_tools().await?;
    for tool in tools {
        println!("Tool: {} - {}", tool.name, tool.description);
    }

    Ok(())
}

ZAP vs MCP

ZAP includes MCP Gateway Mode for seamless migration from existing MCP servers.