Skip to main content

What is A2A?

The Agent-to-Agent (A2A) Protocol is an open standard that enables AI agents from different platforms and frameworks to communicate and collaborate effectively. Slide’s Tyler package includes comprehensive A2A v0.3.0 support, allowing your agents to:
  • Delegate tasks to remote A2A-compatible agents
  • Expose Tyler agents as A2A endpoints for other systems
  • Stream responses in real-time with token-level streaming via SSE
  • Exchange files, structured data, and text between agents
  • Produce and consume Artifacts as task deliverables
  • Group related tasks with context IDs
  • Receive real-time updates via push notifications
  • Enable seamless interoperability between different agent frameworks
Use A2A for agent-to-agent delegation and interoperability. For general external tool or data-source integration, use MCP.
💻 Code Examples

A2A Server

Expose a Tyler agent via A2A

A2A Client

Connect to remote A2A agents

Multi-Agent

Coordinate multiple A2A agents

A2A Architecture in Slide

Quick start

Delegating to Remote A2A Agents

Exposing Tyler Agents via A2A

A2A Protocol v0.3.0 Features

Tyler fully supports the A2A Protocol v0.3.0 specification, including:

1. All Part Types

A2A messages can contain multiple types of content:

2. Artifacts

Artifacts are the formal deliverables of a task, providing structured outputs:

3. Context ID for Task Grouping

Group related tasks together using context IDs:

4. Real-Time Token Streaming

A2A clients can receive response tokens as they’re generated via Server-Sent Events (SSE):
The A2A server uses Tyler’s streaming internally for all requests. The A2A SDK handles delivery:
  • message/send: Returns aggregated response after completion
  • message/stream: Streams tokens via SSE as they’re generated
For non-streaming requests, use send_task which waits for completion:

5. Push Notifications

Receive real-time updates for long-running tasks via webhooks:

6. Authentication Declaration

Declare authentication requirements in your Agent Card:

A2A Protocol Features

Agent Discovery

A2A uses Agent Cards to describe agent capabilities:

Task Management

A2A provides full task lifecycle management:

Secure Communication

A2A supports standard web security practices:

Multi-Agent Coordination

Creating Specialized Agent Networks

Task Delegation with Files and Data

A2A vs MCP Comparison

Production Deployment

Server Configuration

Installation and Setup

Install A2A Dependencies

Environment Setup

Security Considerations

Production Security: Always use HTTPS endpoints, implement proper authentication, and validate agent cards in production environments.

Authentication Methods

Webhook Security

Best practices

Design Principles

  • Specialized Agents: Create agents with focused, well-defined capabilities
  • Clear Interfaces: Use descriptive agent cards and task descriptions
  • Use Artifacts: Structure task outputs as formal Artifacts for better interoperability
  • Context Grouping: Use context IDs to group related tasks for better tracking
  • Push Notifications: Use webhooks for long-running tasks instead of polling
  • Error Handling: Implement robust connection and task failure handling
  • Monitoring: Track agent health and task completion rates
  • Security: Always use secure connections and proper authentication

Next steps

A2A Integration Guide

Step-by-step A2A integration tutorial

Multi-Agent Patterns

Learn advanced delegation patterns

A2A Specification

Read the official A2A protocol specification

Agent Architecture

Understand Tyler’s agent architecture