Agents increasingly call other agents, across teams and across partners. An A2A gateway gives that traffic the same front door as model calls: a signed Agent Card for the agent you expose, partner scopes and rate limits for inbound tasks, and policy, inspection, budgets and evidence for every task in and out.
01
A partner's agent that sends your agent a task is a caller like any other: it must be identified, limited and recorded, and the task it sends may carry an injection or data you must not accept. Your own agent handing work to an external agent is an outbound call that must respect budgets and data policy. Skyfix treats both as governed requests on the Agent2Agent protocol.
02
Each workspace environment can publish one inbound agent, off by default. The control plane renders its Agent Card from operator fields: the skills it offers, the required scope, the accepted content types and the capabilities such as streaming and push notifications. The card is signed under your installation's own keys, and the signing key ID and card fingerprint are shown so a partner can verify what it received.
03
Inbound tasks arrive at the gateway, which is the front door; an internal agent you register does the work. A partner must be on the allowlist, present a bearer token with the required scope, and stay within its rate limit, which is set per partner. Authentication, authorization and limit decisions are recorded in the ledger before the internal agent sees the task.
04
Handoffs to registered external agents leave through the same gateway. The task passes identity, policy, the AI Firewall, the budget check and the ledger exactly like a model call, so data that must not leave your boundary is redacted or blocked before it does, and the cost of the handoff is attributed to the workflow that made it.
05
The inbound agent is off until someone publishes it, and unpublishing withdraws the card at once. Its skills, scope, accepted content types and partner list are edited in the console as a governed change, so a new partner or a new skill is an audited action with an owner. The card's signing key and fingerprint are shown next to the card, and a rotation produces a new fingerprint that partners can verify against the previous one.
06
Inbound and outbound tasks use JSON-RPC, gRPC or HTTP+JSON, the three standard bindings of A2A 1.0. The implementation is tested against the official conformance suite.
07
Every inbound and outbound task lands in the hash-chained ledger with the partner or external agent, the scope, the policy result, the firewall outcome, the budget status and the trace ID, grouped with the model and tool calls it caused. An auditor can follow one partner task through everything it triggered.
FAQ
The front door for Agent2Agent protocol traffic. It publishes your agent's signed card, authenticates partner agents, checks what they may ask, applies limits and records every task before an internal agent sees it, and governs the tasks your agents send out.
An MCP gateway governs an agent calling tools; an A2A gateway governs agents calling agents, inbound from partners and outbound to external agents. Skyfix runs both in the same gateway with the same policy, inspection, budgets and ledger.
JSON-RPC, gRPC and HTTP+JSON, the three standard bindings of A2A 1.0, tested against the official conformance suite.
A partner must be on the allowlist, present a bearer token carrying the required scope and stay within its per-partner rate limit. Each decision is recorded in the ledger.
Yes. Inbound and outbound tasks are governed requests that draw from the same workspace, team, workflow and end-user budgets and appear in the same cost views.
