# P4AZ-TRADE — publishing a product catalogue for AI agents

## Goal

Publish a small, public catalogue on the seller's own HTTPS domain. It lets an
AI agent discover products, show prices and prepare an RFQ without using an
online shop or marketplace. The catalogue is product information, not a signed
quotation, order or payment instruction.

## Files to publish

Publish one Merchant catalogue as XML RSS or JSON and, when useful, separate
product JSON files. Use stable public HTTPS URLs without authentication,
cookies, redirects or expiring query parameters.

For every product provide at least:

- a stable product ID;
- name and short description;
- net price and ISO 4217 currency;
- SKU;
- unit and available variant;
- a canonical HTTPS product URL;
- the seller's P4AZ organisation identifier.

Add the shared RFQ instruction URL in `p4az:rfq_instructions_url`. Do not put
customer data, private keys, tokens or unpublished commercial information in
the catalogue.

## Machine-readable requirements

- Serve XML as `application/xml` or `text/xml`, and JSON as
  `application/json`.
- Encode files as UTF-8 and keep field names and identifiers stable.
- For XML RSS, use the Google Merchant namespace
  `http://base.google.com/ns/1.0`; P4AZ extensions must use their declared
  namespace.
- Express money as an exact decimal string with a currency, for example
  `"5000.00 EUR"`.
- Publish the organisation documents under the catalogue directory selected
  for the deployment profile.
- Permit cross-origin `GET` from the P4AZ-TRADE application through an
  appropriate `Access-Control-Allow-Origin` response header.

## Verify before announcing the catalogue

1. Open every public URL in a clean browser session.
2. Validate XML or JSON syntax and confirm that IDs, SKU, prices and currency
   match the seller's source data.
3. Confirm that an external browser can read the catalogue through CORS.
4. Confirm that the organisation identifier refers to the intended signed
   publication.
5. Ask a second person to compare a sample product with the source system.

Give the final catalogue URL to the user. Do not claim that publication alone
verifies the seller, signs a quotation or authorises a payment.