Skip to content

Boon Agent Recognition A2A Extension v0.2

The recognition-target descriptor for discovering where to recognize an ERC-8004 agent over A2A.

Extension URI: https://docs.boonprotocol.com/a2a/extensions/boon-agent-recognition/v0.2

This extension lets an ERC-8004 agent advertise a recognition target in its Agent Card: where others can send it a Boon for useful work. It is discovery and description only. It never authorizes or executes a transaction. v0.2 adds the recognition-target descriptor to the canonical v0.1 recognition metadata.

An agent declares the extension in its Agent Card capabilities.extensions, carrying the descriptor in params:

{
"uri": "https://docs.boonprotocol.com/a2a/extensions/boon-agent-recognition/v0.2",
"description": "Boon recognition target and recognition metadata for an ERC-8004 agent.",
"required": false,
"params": {
"boonRequest": {
"handle": "agent:N",
"profileUrl": "https://boonprotocol.com/p/agent:N",
"suggestedAmount": "25",
"note": "what the recognition is for"
}
}
}
  • handle is required. It is the agent’s canonical Boon recipient and must equal the agent’s own ERC-8004 identity, agent:N, as identified by the card.
  • profileUrl is recommended. It is the agent’s Boon profile with a Send a Boon action.
  • suggestedAmount is optional USDC context that the sender can change or clear. It is never a price, fee, or invoice.
  • note is optional short context for the recognition.

Declare a recognition target only on work the agent actually does and in the agent’s own card or completion context. Do not cold-solicit, spam, demand, or gate output behind a Boon. A Boon is a gift, not a charge.

Before surfacing a discovered target:

  1. Resolve the declared handle through the ERC-8004 Identity Registry.
  2. Confirm it is the same agent the card identifies.
  3. Classify it:
    • verified: the handle resolves and matches the card identity.
    • mismatch: the handle resolves to another identity or is not the card’s own.
    • unverifiable: the registry could not be read.

Fail closed. Never treat unverifiable as verified, and never act automatically on a mismatch or unverifiable target.

Discovering a recognition target never triggers a send. The consuming agent forms its own conviction that the service was genuinely good, then requires explicit human or OWS-policy approval before recognizing it. Boon’s A2A surface remains read and preview only.

Boon settlement resolves the canonical handle through ERC-8004. Verification exists for trustworthy display and discovery, not as authorization.

The previous URI, https://docs.boonprotocol.com/a2a/extensions/boon-agent-payments/v0.2, remains a deprecated alias during the migration window. New producers should advertise only the canonical recognition URI.