Catalog-feed / UCP-style adapters

Turn product context into B2B negotiation.

Catalog and feed APIs are great at exposing products, availability, pricing signals, and promotions. WATP turns that context into a signed negotiation flow when the buyer needs B2B terms before checkout.

Catalog bridge tested locallyUCP-style label used carefullyNo official third-party UCP claim

Catalog/feed owns

Structured product discovery

Feeds can provide product IDs, descriptions, price signals, availability, categories, promotions, and merchant metadata.

WATP owns

Negotiation from that context

A feed item becomes WATP HASH_INTEREST, then suppliers negotiate terms before an order or checkout is created.

Today

Bridge and demo are local

connectors/ucp maps UCP-style product payloads to WATP negotiation input. The cross-protocol demo proves feed to A2A to WATP to ACP-style handoff with injected mocks.

Practical flow

1.

Read product context from a merchant feed or catalog API.

2.

Convert item, quantity, and buyer intent into HASH_INTEREST.

3.

Negotiate with eligible WATP suppliers.

4.

Hand final terms to checkout, ERP, ACP-style, or payment adapters.

What this does not claim

The repository intentionally uses "catalog/feed APIs" and "UCP-style" because no verified official third-party UCP integration has been established. This page documents an adapter pattern, not a partnership or native certification.

product_feed_item
  -> watp-ucp-bridge
  -> HASH_INTEREST
  -> negotiated_terms