{
  "source": "Agentic Commerce Atlas",
  "url": "https://agenticcommerceatlas.com/resources/",
  "license": "CC BY 4.0: quote or reuse with attribution to Agentic Commerce Atlas.",
  "updated": "2026-06-28",
  "resources": [
    {
      "title": "Merchant Agent-Readiness Checklist",
      "description": "A practical checklist to assess whether a business is ready for AI agents to find and buy its products.",
      "url": "https://agenticcommerceatlas.com/resources/agent-readiness-checklist.md",
      "encodingFormat": "text/markdown",
      "contentMarkdown": "# Merchant Agent-Readiness Checklist\n\nAgentic Commerce Atlas - agenticcommerceatlas.com - CC BY 4.0\n\nA practical checklist to assess whether your business is ready for AI agents to find and buy your products. Work top to bottom; the early items are foundational.\n\n## 1. Product data\n- [ ] Every product has complete attributes (title, description, price, currency, availability, images, brand, category, identifiers, variants)\n- [ ] Your product feed is structured and machine-readable (a recognized schema), not just web-page prose\n- [ ] Feed prices and stock match your live store exactly, to the cent and the unit\n- [ ] Price and availability sync in near real time, not in slow batches\n- [ ] You monitor for drift between the feed and the live store\n\n## 2. Discoverability\n- [ ] Your products are present on at least one live agent surface your customers use\n- [ ] You have verified how agents represent and rank your products\n- [ ] If you sell through a platform, syndication to agent surfaces is enabled and checked\n\n## 3. Transactability\n- [ ] Your checkout is reachable via an API that returns structured data, not only rendered web-page elements\n- [ ] You support, or have a clear path to support, a checkout standard (ACP and/or UCP) for the surfaces you care about\n- [ ] You have completed an agent-initiated order end to end in a test\n\n## 4. Payments and verification\n- [ ] You rely on the networks' agent-verification and scoped-token mechanisms rather than building your own trust layer\n- [ ] You understand the Shared Payment Token or delegated-payment flow for your processor\n- [ ] You have read the terms of any agent-payment program you have joined\n\n## 5. Evidence and monitoring\n- [ ] You log agent authorization and behavior continuously across the transaction\n- [ ] You can defend a dispute with a recorded audit trail rather than a reconstruction\n\n## 6. Governance and risk\n- [ ] Agentic commerce has a named owner in your organization\n- [ ] Leadership is briefed on the two contested points: the checkout-standard question and the liability picture\n- [ ] You handle agent-channel data to the same standard as the rest of your customer data\n- [ ] You have a deliberate plan to protect your first-party customer relationship\n\nHow to read it: mostly unchecked means start with section 1 (product data); mostly checked means you are ready to run a real pilot and measure.\n\n---\n\nLearn more at agenticcommerceatlas.com. Free to reuse under CC BY 4.0 with attribution."
    },
    {
      "title": "Agentic Commerce Vendor and Platform Evaluation Scorecard",
      "description": "Questions to ask platforms, processors, and vendors before committing to an agentic commerce integration.",
      "url": "https://agenticcommerceatlas.com/resources/vendor-evaluation-scorecard.md",
      "encodingFormat": "text/markdown",
      "contentMarkdown": "# Agentic Commerce Vendor and Platform Evaluation Scorecard\n\nAgentic Commerce Atlas - agenticcommerceatlas.com - CC BY 4.0\n\nQuestions to ask a platform, processor, or vendor before committing to an agentic commerce integration. Score each from 1 (poor) to 5 (strong), or mark N/A, and add notes. A low score on trust and liability or on lock-in deserves extra weight.\n\n## Standards and surfaces\n- Which checkout standards do you support (ACP, UCP, both)?  [ 1 - 5 ]\n- Which agent surfaces does this reach (ChatGPT, Google AI Mode and Gemini, others)?  [ 1 - 5 ]\n- Do you support the discovery (MCP) and authorization (AP2) layers, or only checkout?  [ 1 - 5 ]\n\n## Data and feed\n- How is our product feed ingested, and how is live-store parity maintained?  [ 1 - 5 ]\n- How quickly do price and stock changes propagate to agent surfaces?  [ 1 - 5 ]\n\n## Payments and economics\n- What payment methods and tokens are supported (Shared Payment Token, network tokens, stablecoins)?  [ 1 - 5 ]\n- What are the fees, including any per-sale fee on agent-initiated orders?  [ 1 - 5 ]\n\n## Trust, fraud, and liability\n- How do you verify that an agent is legitimately authorized to act for a customer?  [ 1 - 5 ]\n- Who bears liability for an agent-initiated chargeback, and what are the dispute terms?  [ 1 - 5 ]\n- What consumer-protection commitments apply?  [ 1 - 5 ]\n\n## Independence and lock-in\n- Is this built on open standards, or proprietary to one network or platform?  [ 1 - 5 ]\n- How portable is our integration if we switch providers?  [ 1 - 5 ]\n\n## Support and roadmap\n- What is your support model and response commitment?  [ 1 - 5 ]\n- What is on your agentic commerce roadmap for the next 6 to 12 months?  [ 1 - 5 ]\n\nTotal: ____ / 70. Add notes against each row, and weight trust, liability, and lock-in heavily.\n\n---\n\nLearn more at agenticcommerceatlas.com. Free to reuse under CC BY 4.0 with attribution."
    },
    {
      "title": "Agentic Commerce RFP Question Bank",
      "description": "A buyer-ready question bank for RFPs, procurement reviews, and vendor demos involving agentic commerce platforms.",
      "url": "https://agenticcommerceatlas.com/resources/rfp-question-bank.md",
      "encodingFormat": "text/markdown",
      "contentMarkdown": "# Agentic Commerce RFP Question Bank\n\nAgentic Commerce Atlas - agenticcommerceatlas.com - CC BY 4.0\n\nA buyer-ready question bank for RFPs, procurement reviews, and vendor demos involving agentic commerce platforms. Use these questions to turn broad claims about \"AI commerce\" into specific evidence.\n\n## 1. Scope and supported use cases\n- Which agentic commerce use cases do you support today: product discovery, comparison, cart creation, checkout, payment authorization, post-purchase support, or all of these?\n- Which parts are generally available, in private beta, or still roadmap?\n- Which customer segments or verticals are live on the capability now?\n- Can you show a real end-to-end demo using our category, not only a generic sample catalog?\n\n## 2. Standards and interoperability\n- Which open standards do you support: ACP, AP2, UCP, MCP, A2A, x402, MPP, or others?\n- Where do you use open standards, and where do you use proprietary APIs?\n- Can we export our integration, data mappings, and transaction records if we move providers?\n- How do you handle standards changes, versioning, and backward compatibility?\n\n## 3. Product data and catalog quality\n- What product data fields are required, recommended, and optional?\n- Which identifiers do you use for matching: GTIN, SKU, brand, category, variant, merchant ID, or platform-specific IDs?\n- How quickly do price, availability, promotion, and variant changes reach agent surfaces?\n- How do you detect and report catalog errors, mismatches, or missing attributes?\n- Can we see how agents currently describe and compare our products?\n\n## 4. Agent discovery and ranking\n- Which agent surfaces, marketplaces, assistants, or shopping interfaces can discover our products through your integration?\n- What factors influence whether our products are shown, ranked, or excluded?\n- Can we receive reporting on impressions, recommendations, comparisons, clicks, carts, and completed purchases by agent surface?\n- How do sponsored placements, retail media, or paid listings interact with organic agent recommendations?\n\n## 5. Checkout and transaction control\n- Does the agent complete checkout through your platform, our checkout, or a third-party checkout surface?\n- Which checkout standard or API is used?\n- What customer, cart, shipping, tax, promotion, and inventory data is exchanged at checkout?\n- Can we enforce business rules such as restricted products, shipping limits, minimum order values, fraud controls, and promotion exclusions?\n- How are failed, partial, canceled, refunded, or changed orders handled?\n\n## 6. Payments, authorization, and disputes\n- Which payment methods and delegated-payment models are supported?\n- How is customer authorization captured, scoped, stored, and auditable?\n- Do you support Shared Payment Tokens, network tokens, stablecoins, or other payment artifacts?\n- Who is liable for fraud, agent error, customer dispute, chargeback, or unauthorized purchase claims?\n- What evidence is available to defend a dispute?\n\n## 7. Privacy, security, and data use\n- What customer, product, transaction, and behavioral data do you collect?\n- Which data is shared with agent platforms or model providers?\n- Do you use our data to train models, rank competitors, or improve unrelated services?\n- What security certifications, data retention terms, deletion controls, and access logs are available?\n- Can we restrict sensitive products, customer groups, or geographies?\n\n## 8. Measurement and reporting\n- What dashboards and exports are available for agent-driven discovery, conversion, order value, returns, and disputes?\n- Can reporting separate agent surface, protocol, product category, campaign, and transaction status?\n- How do you attribute a purchase when an agent researches on one surface and checkout happens elsewhere?\n- Can data be exported to our analytics, warehouse, or BI tools?\n\n## 9. Operations and support\n- What implementation work is required from our ecommerce, payments, product data, legal, and customer-service teams?\n- What is the typical pilot timeline and launch checklist?\n- What support, incident response, uptime commitment, and escalation path do you provide?\n- How are breaking changes, partner outages, policy changes, and standards updates communicated?\n\n## 10. Commercial terms and lock-in\n- What fees apply: setup, monthly platform, per-order, payment, referral, ad, data, or support fees?\n- Are fees different by agent surface, protocol, payment method, geography, or category?\n- What contract terms limit portability, direct customer relationships, data reuse, or future integrations?\n- What happens to our data, listings, and transaction history if we leave?\n\n## Red-flag answers\n- \"We support agentic commerce\" without naming which use cases are live.\n- \"Standards-based\" without saying where standards end and proprietary APIs begin.\n- \"Real-time catalog sync\" without a measurable freshness commitment.\n- \"Agents can buy for users\" without a clear authorization and dispute record.\n- \"Full reporting\" without exports by agent surface and transaction state.\n\n---\n\nLearn more at agenticcommerceatlas.com. Free to reuse under CC BY 4.0 with attribution."
    }
  ]
}