a2a-json-rpc
A JSON-RPC implementation for the A2A (Agent-to-Agent) Protocol.
Overview
The a2a-json-rpc library provides a lightweight, transport-agnostic implementation of the JSON-RPC 2.0 protocol specifically tailored for A2A (Agent-to-Agent) communication. It includes:
- Complete JSON-RPC 2.0 request/response handling
- A2A-specific error definitions and handling
- Pydantic models for type-safe message processing
- Async/await support via anyio
- Transport abstraction layer
Installation
pip install a2a-json-rpc
Quick Start
import asyncio
from a2a_json_rpc.protocol import JSONRPCProtocol
from a2a_json_rpc.models import Json
# Create a protocol instance
protocol = JSONRPCProtocol()
# Register a method handler
@protocol.method("echo")
async def echo_handler(method: str, params: Json) -> Json:
return params
# Process a request
async def main():
request = protocol.create_request("echo", {"message": "Hello, A2A!"})
response = await protocol._handle_raw_async(request)
print(response)
if __name__ == "__main__":
asyncio.run(main())
Features
- Type Safety: Built with Pydantic for robust data validation and serialization
- Async First: Designed for asynchronous communication patterns
- Transport Agnostic: Can be used with HTTP, WebSockets, or any other transport
- Error Handling: Comprehensive error types for both JSON-RPC and A2A-specific errors
- Notifications: Support for fire-and-forget notifications
A2A Protocol Support
The library implements the latest A2A Protocol specification (2025), which defines a standard way for AI agents to communicate with each other. The implementation includes:
- Task management operations with full lifecycle support
- Push notification handling for asynchronous communication
- Streaming support for real-time interaction
- Message history tracking with configurable length
- Enhanced task states including
rejectedandauth-required - Comprehensive error handling with A2A-specific error codes
- Agent discovery via Agent Cards
- Multi-modal communication (text, files, data)
Error Handling
The library provides a comprehensive set of error types:
from a2a_json_rpc.json_rpc_errors import ParseError, InvalidRequestError
from a2a_json_rpc.a2a_errors import (
TaskNotFoundError,
PushNotificationsNotSupportedError,
TaskRejectedError,
AuthenticationRequiredError
)
# JSON-RPC standard errors
raise ParseError("Invalid JSON payload")
raise InvalidRequestError("Missing required field")
# A2A-specific errors
raise TaskNotFoundError(data={"id": "task-123"})
raise PushNotificationsNotSupportedError()
raise TaskRejectedError("Task was rejected by the agent")
raise AuthenticationRequiredError("Authentication is required")
Transport Layer
The transport layer is defined as a protocol interface, allowing for different implementations:
from a2a_json_rpc.transport import JSONRPCTransport
class MyTransport(JSONRPCTransport):
async def call(self, method: str, params: any) -> any:
# Implementation
...
async def notify(self, method: str, params: any) -> None:
# Implementation
...
def stream(self) -> AsyncIterator[Json]:
# Implementation
...
Development
Setup
# Clone the repository
git clone https://github.com/yourusername/a2a-json-rpc.git
cd a2a-json-rpc
# Install development dependencies
make dev-install
Testing
make test
Building
make build
Publishing
make publish
License
MIT
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
- Fork the repository
- Create your feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add some amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
Metadata
Release files for a2a-json-rpc 0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| a2a_json_rpc-0.4.tar.gz | 36.4 kB | Without provenance | Details for a2a_json_rpc-0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| a2a_json_rpc-0.4-py3-none-any.whl | Python 3 | none | any | Details for a2a_json_rpc-0.4-py3-none-any.whl |
Total release size: 65.1 kB
Release files / a2a_json_rpc-0.4.tar.gz
| Download URL | a2a_json_rpc-0.4.tar.gz |
|---|---|
| Size | 36.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a803e1653e434c03483cadef1d1d7622500d9a3345fbfdd02bf9b7d0e92c0e8
|
|
BLAKE2b-256 checksum How to use checksums |
ddd11598aa2028fe7b922e125c687e4097c018c652b60009d530ce423c830820
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.2
|
Release files / a2a_json_rpc-0.4-py3-none-any.whl
| Download URL | a2a_json_rpc-0.4-py3-none-any.whl |
|---|---|
| Size | 28.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8195de05ff2f525ab20532939ae88067777a38e640ab2ea07c207df475566243
|
|
BLAKE2b-256 checksum How to use checksums |
285e6843811599f9202b77f0ae289f37ab25adfe5e302f295bcc9aaeb70b7689
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.2
|
Security for a2a-json-rpc 0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.