Operations

AI-commerce feed onboarding

This guide explains how external AI-commerce or answer-engine consumers should discover, verify, and ingest Pawalink's public catalog and commerce exports.

What Pawalink publishes

Pawalink currently exposes 6 machine-readable feed surfaces for storefront discovery, product freshness, and external AI-commerce ingestion.

Use the catalog index for discovery, the delta feed for freshness, and the OpenAI-compatible exports when an external commerce adapter needs a merchant-style payload.

Integration sequence

Start with the catalog integrations manifest, then verify public access policy and allowlisting before attempting ingestion.

Only consume published storefronts and public buyer-safe trust surfaces. Do not assume authenticated or private commerce data is part of the public contract.

Merchant readiness

Merchants appear in external answer or commerce systems only when their storefront is published, products are active, and trust or fulfillment details are present where supported.

Treat shipping, returns, variant, and barcode fields as governed enhancements rather than guaranteed universal fields across all merchants.

Published integration datasets

30 minutes

Global public catalog index

application/json

https://app.pawalink.com/api/v1/public/catalog

5 minutes

Incremental catalog delta

application/json

https://app.pawalink.com/api/v1/public/catalog/delta

60 minutes

OpenAI-compatible product export

application/json

https://app.pawalink.com/api/v1/public/catalog/exports/openai/products

5 minutes

OpenAI-compatible delta export

application/json

https://app.pawalink.com/api/v1/public/catalog/exports/openai/products/delta

30 minutes

Google Merchant Center RSS feed

application/xml

https://app.pawalink.com/api/v1/public/catalog/exports/google/products.xml

30 minutes

Public XML sitemap

application/xml

https://app.pawalink.com/sitemap.xml