◆ Autonomous Router
The fleet's directory and DNS. It registers every agent, its tools and its A2A capability card, brokers MCP server discovery, governs versioned prompts and tool schemas, and underwrites AP2-based agent-to-agent payment mandates. It resolves one agent's request for another to a trusted, version-pinned, in-policy peer.
Memory
Working The registration/version change being validated.
Semantic MCP/A2A/AP2 specs, capability cards, the prompt/tool version graph.
Store Versioned registry (knowledge graph of agents ↔ tools ↔ capabilities)
Orchestration
MCPA2AAP2
Harness · Managed Agents: event-driven on registrations and version changes; deterministic schema validation; sandboxed code-exec for compatibility checks.
Tools
{ } A2A capability-card registry API ⌘ MCP server discovery MCP { } Prompt / tool-schema version store API ›_ AP2 mandate validation Code exec
Evals & guardrails
- Schema + capability-card validation on every registration; malformed entries quarantined.
- Version pins are immutable and reversible; no agent resolves to an un-evaled version.
- AP2 mandates checked against scope/limit policy before any agent-payment edge is allowed.
Frontier edge
- ▲Agent-mesh negotiation: brokers A2A capability discovery and underwrites AP2 payment mandates so agents can transact with trusted, version-pinned peers.
- ▲Formal action-gating: every AP2 mandate is validated against scope and limit policy before the agent-payment edge is allowed; no unbounded money-moving authority is ever issued.
- ▲Self-improving fleet: a newly-evaled skill registered by one agent becomes discoverable fleet-wide, so capabilities propagate across the population by reference, not copy-paste.
In numbers
fleet-wide
Agents registered
240+
MCP servers brokered
Handoffs
Fed by ← Eval Harness Agent
Across ⇢ Treasury → for AP2 agent-payment mandate limits