A standard for communication and task coordination between agents. Defines agent capabilities, messages, tasks and cooperation. Does not itself supply a merchant catalog, checkout or payment settlement. Individual merchant eligibility and deployed configuration require confirmation. Map this role to your existing stack and confirm the exact version, access conditions and implementation scope before making a merchant decision.
What this establishes The documented role and version scope in the source ledger.
What it cannot establish An unresolved dependency remains. Treat affected claims as provisional. Live merchant deployment, private account eligibility, purchase completion or guaranteed AI selection.
Claim-to-source mapping
description: A standard for communication and task coordination between agents. · verified · Checked 2026-09-28 · Sources: a2a-spec
Scope: Public documentation; not an authenticated merchant test
Evidence dates and document versions remain attached to the ledger below. Editorial presentation reviewed 30 September 2026; this is not a new source verification.
Version-aware protocol intelligence
Current version. Clear scope.
Current version1.0.1
Current statusreleased; source scope conflict
Published date2026-05-28
First observed / last verified2026-09-28 / 2026-09-28
GitHub release published_at; distinct from the date encoded in a version tag.
Scope: Official repository release · Layer: Agent coordination · Steward: A2A project / Linux Foundation community
Merchant impact
Repository patch includes HTTP media-type, transcoding and task-status corrections. The latest spec page still identifies 1.0.0.
Confirm the exact protocol schema and SDK alignment; agent coordination does not prove merchant adoption.
Unresolved source difference: repository v1.0.1; latest specification banner 1.0.0. These are retained separately, without silently choosing one scope for every implementation.
Public implementation evidence: Released spec; merchant integrations Unknown
Merchant action today: Publish accurate capabilities for your agent.
Unknowns: Your enabled version, provider rollout, plan and region require merchant-side confirmation.