Single A2A JSON-RPC 2.0 transport endpoint. The body is a JSON-RPC envelope whose method field selects the operation. Choose a request example (SendMessage, GetTask, CancelTask) to see the payload for each method. On success the response result holds a Task or a Message. All failures — including request-validation errors such as an invalid enum value — are returned as a JSON-RPC error object with HTTP status 200, per the A2A JSON-RPC binding; the endpoint does not use HTTP 4xx status codes to signal application or validation errors.
Client-chosen request identifier, echoed back in the response.
The A2A method to invoke. Supported values: SendMessage, GetTask, CancelTask. Confirm the exact literals against the Agent Card before use, as additional methods may be added over time.
- CDQ Genius A2A base URL. The Agent Card is served at /.well-known/agent-card.json and all JSON-RPC operations are POSTed to /.https://api.cdq.com/a2a/cdq-genius
{ "jsonrpc": "2.0", "id": 1, "method": "SendMessage", "params": { "message": { … }, "metadata": {} } }
JSON-RPC 2.0 response. On success result is a Task or a Message; on any failure — including validation errors — error is populated (see JSONRPCError). This endpoint always responds with HTTP 200; it does not return HTTP 4xx codes for application or validation errors.
JSON-RPC 2.0 success response envelope.
The request identifier echoed back from the request.
{ "jsonrpc": "2.0", "id": 1, "result": { "id": "task-abc123", "contextId": "ctx-xyz789", "status": { … }, "artifacts": [ … ] } }