A2A interoperability

Use WATP as the negotiation layer for A2A agents.

A2A coordinates agents and long-running tasks. WATP gives those agents a commerce-specific envelope for supplier discovery, proposals, counteroffers, hash continuity, and checkout handoff.

WATP network liveA2A bridge snapshot testedNo official A2A endorsement claimed

A2A owns

Capability discovery and task routing

An A2A runtime can advertise a commerce capability, receive a buyer task, and coordinate the agent lifecycle.

WATP owns

Commercial negotiation state

The A2A task becomes HASH_INTEREST, then WATP records proposals, counters, human waits, conclusion, or cancellation.

Today

Usable as a guided beta path

connectors/a2a exposes commerce.negotiate and passed local tests. The live WATP network, Woo supplier package, and standalone supplier can already return payment_url.

Practical flow

1.

Advertise commerce.negotiate in the agent runtime.

2.

Validate the A2A task and create WATP HASH_INTEREST.

3.

Negotiate with supplier nodes through signed HTTPS messages.

4.

Return HASH_CONCLUDED, final terms, and optional payment_url.

What this does not claim

This page describes an adapter boundary. It does not claim partnership, certification, or native approval from Google, the Linux Foundation, or any A2A governance body. A2A keeps agent collaboration generic; WATP specializes the commercial negotiation that happens inside the task.

{
  "capability": "commerce.negotiate",
  "result": "HASH_CONCLUDED",
  "handoff": "payment_url"
}