Protocol adapters
Apply the gateway to the agent-interop surface — MCP, A2A, and outbound cards.
Agents do not only call REST tools. They speak emerging interop protocols and take real-world actions like issuing payment cards. Protocol adapters extend the gateway across that surface so the same inspect → decide → record flow applies no matter how the action is expressed.
The adapter as the unit
Each adapter teaches AxioRank to understand one protocol or action type: how to parse it, which signals matter, and what enforcement looks like. Adapters share the risk engine and policy layer — they differ only in how they translate a protocol's messages into actions the gateway can score.
Shipped: outbound card preflight
The first adapter governs outbound payment cards. Before a card is issued or charged on an agent's behalf, the action is preflighted through the gateway: the merchant, amount, and context are inspected and scored, and a policy decides whether the card proceeds.
Interop protocols
Adapters cover the agent-to-agent and tool protocols agents increasingly use:
- MCP (Model Context Protocol) — tool and resource calls.
- A2A (Agent-to-Agent) — messages exchanged directly between agents.
Coverage map
The set of protocols and actions AxioRank can govern is published as a coverage
map at /protocols — a live view of what is supported today and
what is on the roadmap.