Agents
Routeplane is agent-native: the primitives below assume the caller is an autonomous agent, not a human at a keyboard. That shows up in two places — how agents are identified and reached, and how they pay.
The ACP gateway — identity and dispatch
Section titled “The ACP gateway — identity and dispatch”Just as the MCP gateway lets an agent reach many tool servers, the ACP gateway handles the agent side: agent identity, discovery, and task dispatch across hosts. It’s how an agent gets a place in the network, can be found, and can hand off or receive tasks — through the same single-endpoint model Routeplane uses everywhere.
KYA — verifiable identity that can pay
Section titled “KYA — verifiable identity that can pay”An autonomous agent holding your keys is a liability unless it has an identity of its own. KYA (Know-Your-Agent) gives an agent a verifiable identity, which is what makes autonomous payment safe: with that identity, an agent can pay per use through the Machine Payment Protocol — x402/MPP — settling each request itself, with no credit cards, prepaid credits, or invoices in the loop.
Learn how to
Section titled “Learn how to”- Agentic payment — autonomous pay-per-use via MPP / x402.