Review the ACP Feed specification in the official repository and implement the required product feed JSON schema: each product object must include id, name, description, price (with currency), availability, images array, and variants
Host the feed at a stable HTTPS URL and expose it via the ACP feed endpoint (typically GET /acp/feed); support pagination via cursor-based parameters as specified in the ACP Feed RFC
Implement the optional search and filter query parameters (category, price range, availability) so agent clients can narrow results without fetching the full catalog
Register your feed URL in the ACP merchant onboarding flow with your ACP provider (Stripe or compatible) so agent platforms like ChatGPT can discover and index your catalog
Keep the feed fresh with incremental updates; implement the If-Modified-Since and ETag caching headers so agents can poll for changes efficiently without re-downloading the full catalog
Known gotchas
ACP Feed schema validation is strict; missing required fields (especially price or availability) will cause agent platforms to exclude your products from discovery — validate every product object against the published JSON Schema before deploying
Product IDs in the feed must be stable and globally unique within your catalog; if you recycle IDs after deleting products, an agent may attempt to purchase a product that no longer exists, causing checkout failures
The ACP spec is still evolving; check the GitHub repository for schema version changes before each production deploy, as breaking changes to required fields have occurred between minor spec versions
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp