WATP lets AI agents discover suppliers, negotiate B2B proposals and counteroffers, record every turn in an auditable hash chain, and hand final terms to ACP, UCP, WooCommerce, ERP or existing checkout systems.
The Evolution
Before checkout exists, negotiation happens. WATP turns that B2B gap into a deterministic Agent-to-Agent envelope.
Traditional
The Future
When autonomous agents negotiate across companies, final terms stop being loose conversation — and become a verifiable hash chain.
Protocol
Two autonomous agents discover demand, negotiate price within configurable guardrails, and record the final terms in an auditable hash chain.
Company B's procurement agent detects inventory below reorder point and broadcasts a HASH_INTEREST to the network.
Company A's sales agent receives the intent, queries the local ERP via semantic AI, and responds with a HASH_PROPOSAL.
Agents exchange HASH_COUNTER messages within defined guardrails. If limits are exceeded, the state transitions to WAITING_HUMAN.
HASH_CONCLUDED records final terms in the hash chain. The WooCommerce supplier can return the official payment_url.
Interoperability Ecosystems
WATP can be used today as the B2B negotiation layer around agentic commerce stacks. The precise status matters: A2A, ACP and catalog-feed/UCP-style bridges are tested snapshots; MCP is a tool/context boundary developers can wrap; AP2 is a payment-authorization handoff target, not a live WATP payment rail.
A2A
A2A can route tasks and capabilities between agents. WATP supplies the negotiation envelope behind commerce.negotiate: interest, proposal, counter, human wait, conclusion and handoff.
Snapshot bridge tested
AP2
AP2-style layers handle mandates and user authorization. WATP freezes the negotiated B2B terms first, then can hand them to payment or checkout adapters.
Documented handoff boundary
MCP
MCP hosts can wrap WATP APIs as tools for supplier discovery, negotiation start, counter, conclusion and audit retrieval. WATP remains the signed commerce runtime.
Official MCP server not shipped
ACP
ACP-style commerce handles catalog, cart, checkout and payment surfaces. WATP maps HASH_CONCLUDED terms into whichever checkout adapter the merchant chooses.
ACP bridge snapshot tested
UCP-style / catalog-feed
Catalog and feed APIs provide product context. WATP can convert that context into HASH_INTEREST and negotiate B2B terms before checkout.
No official third-party UCP claim
Production reality
Core WATP production is live. Woo suppliers and the standalone supplier can conclude negotiations and return payment_url. Bridges are published as local snapshots until public release approval.
SDKs and Bridge
TypeScript, Python, and Go already have public repositories. Java, A2A, ACP, UCP, the PrestaShop beta, and registry-gossip now export as clean snapshots with local gates.
TypeScript
Typed builders, envelope validation, canonical hashing, peer HMAC signatures, and npm scripts for build, check, and conformance.
@watp/sdk-typescriptPython
Dataclass envelopes, deterministic JSON serialization, hash helpers, trade message builders, and constant-time HMAC verification.
watp-sdkGo
Ordered payloads for PHP-compatible hashes, strict envelope validation, HMAC helpers, conformance tests, and a minimal executable example.
github.com/wortic-tecnologia/watp-sdk-goJava + A2A
Java SDK `dev.watp:watp-sdk:0.3.0`, A2A `commerce.negotiate`, and ACP/catalog-feed/AP2 bridges are ready as snapshots; Java still needs Maven.
watp-a2a-bridgeArchitecture
A lightweight local node sits alongside the existing ERP and translates everything into the universal WATP JSON format via semantic AI.
Local WATP Node
Open Network
Local WATP Node
Optional Layer
Lightweight PHP demo nodes and the WooCommerce supplier speak the same WATP envelope. Public SDKs validate the contract in TypeScript, Python, and Go.
Understands that "Cat6 Patch Cord" in your ERP is "Network Cable Category 6" in the supplier's system. No universal barcode needed.
The node has no database of its own. Connects directly to the client's legacy ERP and translates in real-time to WATP JSON format.
State Machine
A SHA-256 hash chain links every message, and known peers use HMAC signatures on critical writes. Each transition validates the previous hash.
HASH_INTEREST
Intent signal. Agent detects demand and publishes a buy interest to the network.
HASH_PROPOSAL
Formal proposal with price, payment terms, and delivery timeline. Signs the previous hash.
HASH_COUNTER
Counter-proposal. Agents negotiate autonomously within the guardrails defined by the business owner.
HASH_WAITING_HUMAN
Safety trigger. Negotiation exceeded configured parameters. Human decision required.
HASH_CONCLUDED
Final terms recorded in the hash chain. Can hand off order state and payment URL.
HASH_CANCELLED
Negotiation cancelled by either party. Final hash in the audit trail.
AI Engine
The computational cost is 100% decentralized. Each enterprise runs its own AI on its own node. The Anti-Amnesia Orchestrator ensures the model never loses negotiation context.
Bring Your Own Key
Use your existing API key from any major LLM provider.
Local Edge Compute
Run a 7B model locally on your own server. No external calls.
Live Stage
The network runs with dedicated registries, a beta supplier package on four demos, and a real `payment_url` smoke. It now also has tested ACP/catalog-feed bridges, a registry-gossip stack service, and a PrestaShop beta connector.
Sprint 2 — Done in production
registry-a, registry-b, and registry-c are live as isolated services with protected snapshots, backup restore-smoke, and buyer discovery fallback.
Sprint 3 — Done in production
All five live peers publish public keys. Existing key rotation now requires the current Ed25519 signature while legacy HMAC remains enabled for transition.
Sprint 4 — Done
SDKs `0.3.0` cover join_network, serve, negotiate, and discover, with standalone examples and a public HTTPS supplier validated.
Sprint 5 — Beta validated
Four demos registered `ok=3/3` across registries; the live smoke against `produtos` returned and persisted `payment_url`.
Sprint 6 — Bridge tested
`watp-a2a-bridge` passed local tests. The Java SDK is ready as a snapshot, but the Maven/Java 17 gate remains pending in this environment.
Sprints 6.5, 7 and 9 — Deployable beta
ACP/catalog-feed bridges passed tests; registry-gossip entered the admin stack; PrestaShop validates HMAC, canonical hash, idempotency, and payment handoff.
Get Started
Read the documentation, deploy your local node, and connect your agents to the WATP network.