Skip to main content
Narada supports two industry-standard protocols for agent integration: Agent-to-Agent (A2A) and Model Context Protocol (MCP). These protocols enable seamless communication between Narada and other AI agents or systems.

Overview

Both A2A and MCP provide standardized ways to interact with Narada’s capabilities:
  • A2A Protocol: Enables direct agent-to-agent communication following the A2A specification
  • MCP Protocol: Uses the Model Context Protocol with Streamable HTTP for structured interactions

A2A Integration

Direct agent-to-agent communication using the A2A specification

MCP Integration

Structured interactions using Model Context Protocol with Streamable HTTP

A2A Protocol

The Agent-to-Agent (A2A) protocol enables direct communication between AI agents using a standardized specification.

Agent Discovery

Narada’s A2A agent information is available at the well-known endpoint. You can discover the agent card as :
cURL
Agent Information

A2A Endpoint

The main A2A endpoint follows the exact A2A protocol specification: Endpoint: https://api.narada.ai/fast/v2/a2a
The A2A endpoint implements the complete A2A protocol specification. Refer to the official A2A documentation for detailed protocol requirements and message formats.

Authentication

A2A requests require authentication using your Narada API key:
Authorization
string
required
Bearer token for API authentication. Format: Bearer YOUR_API_KEY

Example A2A Request

This example demonstrates how to use the A2A Python SDK to discover Narada’s agent card and send a streaming message request asking the Operator agent to navigate to google. First, install the A2A Python SDK:
The A2A SDK is the official Python library for the Agent2Agent Protocol. You can find more details in the A2A Python SDK repository.

MCP Protocol

The Model Context Protocol (MCP) provides structured communication using Streamable HTTP for efficient data exchange.

MCP Endpoint

Endpoint: https://api.narada.ai/fast/v2/mcp
The MCP endpoint implements the complete Model Context Protocol specification. Refer to the official MCP documentation for the detailed protocol requirements and message formats

Authentication

MCP requests use the same authentication method as A2A:
Authorization
string
required
Bearer token for API authentication. Format: Bearer YOUR_API_KEY

Example MCP Request

This example demonstrates how to use the FastMCP Python SDK to send a streaming message request asking the Operator agent to navigate to google. First, install the FastMCP Python SDK:
FastMCP is a Python library for the Model Context Protocol. You can find more details in the FastMCP documentation.

Error Handling

Both protocols return standardized error responses:
Error Response

Common Error Codes

  • 401 Unauthorized: Invalid or missing API key
  • 400 Bad Request: Invalid request format or parameters
  • 422 Unprocessable Entity: Request validation failed
  • 500 Internal Server Error: Unexpected server error
  • 503 Service Unavailable: Service temporarily unavailable