a2a-integration

Expose orxhestra agents as JSON-RPC A2A endpoints or connect to remote A2A agents.

19|6|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/NicolaiLassen/orxhestra --skill a2a-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a2a-integration
Source: https://github.com/NicolaiLassen/orxhestra/tree/main/docs/skills/a2a-integration
Command: npx skills add https://github.com/NicolaiLassen/orxhestra --skill a2a-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the friction of connecting locally hosted orxhestra agents with other systems by providing standardized A2A protocol endpoints and client connectivity.

Core Features & Use Cases

  • A2A Server (Expose an agent): Publish an orxhestra agent as a JSON-RPC 2.0 A2A service with agent-card discovery and task lifecycle methods.
  • A2A Agent (Connect to a remote agent): Consume events from a remote A2A agent to integrate external expertise into your orchestration flow.
  • In YAML Composer (Wire into agent setups): Declare remote agents in YAML and route tool calls through the main orchestrator.

Quick Start

Ask orxhestra to expose your agent as an A2A server using A2AServer and start it so other A2A clients can discover and send JSON-RPC messages to it.

Frequently Asked Questions about a2a-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the A2A protocol and how does multi-agent JSON-RPC orchestration work?

A2A protocol enables multi-agent orchestration by exposing agents as JSON-RPC 2.0 endpoints. It allows systems to discover services via agent cards, delegate tasks, stream responses, and manage task lifecycles across service boundaries using standardized communication.

How do I expose a FastAPI agent as an A2A service for remote orchestration?

You can expose an agent as an A2A service by initializing an A2AServer. This publishes your agent as a JSON-RPC endpoint with agent-card discovery at /.well-known/agent.json, enabling other A2A clients to send messages and manage task completion.

Can I connect to remote A2A agents and route their tool calls through a main orchestrator?

Yes, you can consume events from remote A2A agents using an A2AAgent. You can declare these remote agents in YAML Composer, allowing the main orchestrator to route tool calls and integrate external expertise into your multi-agent workflow.

Does the A2A protocol support task streaming and lifecycle control like cancellation?

A2A protocol supports task streaming and lifecycle control through JSON-RPC methods. It handles message streaming for delegated tasks and provides methods to manage task completion or cancellation across connected service boundaries.

What do I need to set up before implementing A2A server discovery for my agents?

You need an orchestration framework with agents ready to be exposed. The A2A integration relies on standard A2A server discovery at /.well-known/agent.json to publish your agent's capabilities, requiring no additional dependencies to establish connectivity.