Guides
Publishing feeds
Turn your audited, enriched catalog into hosted feeds that agent integrations can consume directly.
Supported formats
Every catalog renders to four artifacts:
| File | Format |
|---|---|
| acp.csv | OpenAI ACP product feed, CSV |
| acp.json | OpenAI ACP product feed, JSON |
| gmc.tsv | Google Merchant Center feed, TSV |
| jsonld.json | schema.org Product + Offer JSON-LD |
Feed URLs
Feeds are hosted at stable, tokenized URLs — no auth headers needed, so you can hand a URL to any integration:
https://useshelfready.com/f/<your-slug>/<token>/<file>The token is a capability: anyone with the URL can read the feed, and any mismatch returns a plain 404. List your URLs in Dashboard → Feeds or via GET /api/v1/feeds.
Freshness & re-render
Feeds re-render automatically after every sync — scheduled (every six hours for pull sources) or on demand. You can also force a re-render with POST /api/v1/feeds. Every render emits a feeds.rendered webhook, and a daily drift check compares your live product pages against the catalog so stale prices and availability get caught between syncs.
Seller settings
ACP and GMC items carry seller-level fields — seller name, seller URL, and store country. Set them once in Dashboard → Settings; they are attached to every item at render time.
Until seller settings are filled in, the audit caps your catalog score at 40 — no feed item is valid without them.