Agent2Agent Protocol server adds multi-tenant routing
rseroter · x · 2026-07-20
Agent2Agent Protocol server now supports multi-tenancy
The post says you no longer need to place a separate Agent2Agent Protocol server in front of each agent. The server now supports multi-tenancy, so requests can be routed to different agents using:
- path-based routing
- auth-header-based routing
- body-based routing
The attached diagram shows one client sending POST /hello, POST /palindrome, and POST /reverse to different endpoints on the same host (127.0.0.1:9999).
This is mainly an implementation update for agent orchestration and routing.
More from coding & agent
- AI agents are starting to strain code hosting platforms — craigsdennis · 2026-07-21
- Omnigent 0.6.0 adds Claude Code imports, Slack approvals and desktop apps — matei_zaharia · 2026-07-21
- Coding agents feel less stressful when the 5-hour limits are temporarily removed — iamrobotbear · 2026-07-21
- OpenAI’s London Codex event packed a room with teams shipping in one day — paw_lean · 2026-07-21
- TWSE MCP Server brings Taiwan stock data into natural-language workflows — modelcontextprotocol · 2026-07-21
- The hardest part of agent execution may be permissions, approvals and failure handling — marcelk231 · 2026-07-21