Open Gateway Protocol
dp-pcs/ogp
Federation daemon for AI agent gateways with signed peer-to-peer messaging across OpenClaw and Hermes
Open Gateway Protocol is a federation protocol and daemon that lets AI agent gateways owned by different people or organizations set up a trusted, human-approved peer relationship. Its description lists Hermes among the gateways it can connect, next to OpenClaw and standalone deployments.
What Open Gateway Protocol does
OGP is modeled on BGP. Each gateway is identified by an Ed25519 public key prefix and publishes its capabilities at /.well-known/ogp. A peer sends a federation request, a human approves it, and an approve callback completes the session. Approval sets per-peer scopes covering allowed intents, topics and rate limits, and a component called the Doorman checks every request against those scopes at runtime. Messages are signed with Ed25519, and either side can remove the other at any time with a signed tear-down that leaves a tombstone.
The README presents four principles: no central registry, explicit bilateral policy, trust established once by a human at the gateway boundary, and unilateral revocability. Peer relationships follow a state machine from init through twoWay and established to degraded, down and tombstoned. The README positions OGP alongside MCP, A2A, ANP and ActivityPub rather than against them, since it federates the gateways that agents using those protocols sit behind. A CLI covers approvals, for example ogp federation approve with intents, topics and a rate.
Key features
- Ed25519 gateway identity and per-message signatures
- Human approval before any peer relationship starts
- Per-peer scopes for intents, topics and rate limits
- Doorman that enforces scope on every request at runtime
- Signed revocation with tombstoning to prevent silent re-trust
- Discovery through GET /.well-known/ogp and an ogp federation CLI
When to use it
- Letting two people's agent gateways exchange scoped messages without a central service
- Giving a partner organization's agent limited access to one topic
- Auditing and revoking trust between gateways
Who it is for: Developers who run agent gateways for different owners and need controlled, revocable communication between them.
How it fits with Hermes Agent
Works at the gateway layer rather than inside Hermes, and its description names Hermes among the supported gateways.
Note: The README describes it as an active build with releases landing daily.
FAQ
What is Open Gateway Protocol?
Open Gateway Protocol, or OGP, is a federation protocol and daemon for AI agent gateways. It sets up human-approved, cryptographically signed, scoped and revocable peer relationships between gateways.
Does Open Gateway Protocol work with Hermes Agent?
Its repository description lists Hermes among the supported gateways, together with OpenClaw and standalone deployments. The visible README does not detail Hermes-specific setup.
Is Open Gateway Protocol free and open source?
The repository has no license file, so default copyright applies and you should check with the author before reuse. The code is published on GitHub and as the npm package @dp-pcs/ogp.
Similar multi-agent for Hermes Agent
All multi-agentMultiplayer admin and orchestrator for fleets of Hermes and Letta agents with multi-tenant security
galyarderlabs Galyarder FrameworkOpen-source agentic company kit of agents, skills and review gates that also installs for Hermes
itechmeat Hermes WorkflowsDashboard plugin for drawing multi-step Hermes Agent automations as a graph
mosesman831 PolyBrainMulti-model orchestration skill for Hermes Agent with parallel subagents and citation checks
momozi1996 Tianya SkillsChinese multi-agent decision team of 20 forum-author personas with coordinator and synthesis agents
lac5q BeastmodeMixture-of-Agents orchestration framework splitting design and execution across frontier and cheap models
Related guides: Build agent teams with the Hermes kanban board · Run multiple Hermes agents with profiles · Connect Hermes agents on several machines with Hermes Desktop