Expand description
A2A protocol 1.0, JSON-RPC binding: the wire shapes (protobuf-JSON, camelCase) both roles build and check. Pinned to the released 1.0 specification as implemented by a2a-sdk 1.2.1.
Structs§
- Incoming
- A message sent to the agent, checked.
Constants§
- CARD_
PATH - CONTENT_
TYPE_ NOT_ SUPPORTED - EXTENDED_
CARD_ NOT_ CONFIGURED - INVALID_
AGENT_ RESPONSE - MAX_
BODY_ BYTES - MAX_
PARTS - MAX_
TEXT_ BYTES - PROTOCOL_
VERSION - PUSH_
NOT_ SUPPORTED - STATES
- TASK_
NOT_ CANCELABLE - TASK_
NOT_ FOUND - UNSUPPORTED_
OPERATION - VERSION_
HEADER - VERSION_
NOT_ SUPPORTED
Functions§
- agent_
message - budget_
ok - card
- Agent card built from configuration.
- card_
rpc_ url - Client-side: the JSON-RPC interface a card offers for protocol 1.0.
- check_
result - Client-side check of a result for
method. - incoming_
message - new_id
- parts_
from - Parts a handler supplies: text, data or file references (never inline bytes).
- rpc_
error - rpc_
result - sse
- One SSE event carrying a JSON-RPC response.
- state_
short - state_
wire - stream_
events - The SSE sequence for a streamed task: snapshot, working, artifacts, final status.
- task
- A task from a handler’s
{id, state, text, artifacts}description. - terminal
- timestamp
- version_
ok A2A-Versionmust name 1.0 (patch ignored); missing means 0.3, which is refused.