A2A MSA 简体中文

Technical specification / v0.1 Draft

A2A MSA interoperability specification

This draft is for implementers and reviewers. It specifies how to use existing A2A capabilities without replacing the upstream protocol. Fields, profiles, and test requirements may change.

Read the upstream A2A specification

“MUST” and “MUST NOT” specify requirements for conformance; “SHOULD” indicates a recommendation. Implementing this draft does not confer certification.

1. Scope and upstream version

This version targets the A2A v0.3.0 JSON-RPC binding. Implementations MUST satisfy upstream requirements as well as the claimed profile in this draft. The Agent Card protocolVersion MUST be 0.3.0; other bindings or upstream versions are outside this draft’s conformance claims.

2. Conformance levels

core: serve a public Agent Card over HTTPS, accept message/send, and advertise at least one skill that returns a Task with an ID whose current state is available via tasks/get. streaming: satisfy core, advertise streaming: true, and support message/stream. After disconnection, clients MUST be able to retrieve the same task’s current state or final result via tasks/get. Clients MUST NOT require streaming unless declared. Neither level prescribes the agent’s internal implementation.

3. Agent Card extension

Implementations MUST list the URI below in capabilities.extensions and set required to false. params.version MUST be the string 0.1. params.profiles is an array of strings, MUST include core, and may include streaming only if the streaming requirements are met. Clients MUST ignore unknown profile names and MUST NOT infer conformance for an unknown draft version; they may continue as ordinary A2A clients.

{
  "uri": "https://www.a2amsa.com/spec#msa-profile",
  "required": false,
  "params": {
    "version": "0.1",
    "profiles": [
      "core",
      "streaming"
    ]
  }
}

4. Security and authentication

Public Agent Cards MUST NOT include credentials or tenant-specific data. Nonpublic task endpoints MUST use HTTPS and an OAuth 2.0 bearer access token scheme declared in the Agent Card. The service MUST validate token expiry, audience, and permissions. Missing or invalid tokens MUST receive HTTP 401 before business logic runs; insufficient permissions return 403. Task retrieval MUST apply the same tenant isolation as task creation. Credentials MUST NOT appear in URLs, logs, or test reports.

5. Interoperability tests and evidence

Use A2A Test as the testing entry point. The core test set MUST validate the Agent Card and declaration, use two independent clients to exercise the same test skill and read back task state, and verify rejection of missing, expired, and wrong-tenant tokens on protected endpoints. For streaming, verify that events belong to the same task and that task state can be retrieved after disconnection. Reports MUST record the draft version, profile, implementation version, test suite version or revision, and pass/fail outcomes; exclude credentials and production data. These are draft requirements, not a claim that the testing site already automates every check.

Open A2A Test

6. Versioning and governance

Draft revisions will be numbered separately; compatibility between v0.x drafts is not guaranteed. Implementations MUST claim only versions they have verified. Proposals SHOULD include an interoperability use case, compatibility impact, and a reproducible test. Publish changelogs after open review and validate the specification in at least two independent implementations before final adoption. Use the consortium application to express interest in reviewing or contributing.