<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sill Signals</title>
    <link>https://sill.so/signals</link>
    <atom:link href="https://sill.so/signals/feed.xml" rel="self" type="application/rss+xml" />
    <description>Guides, protocol explainers and data on AI agents visiting and buying from websites.</description>
    <language>en</language>
    <lastBuildDate>Thu, 19 Nov 2026 12:00:00 GMT</lastBuildDate>
    <item>
      <title>Web Bot Auth at the IETF: where the standard stands in late 2026</title>
      <link>https://sill.so/signals/web-bot-auth-ietf-status-2026</link>
      <guid isPermaLink="true">https://sill.so/signals/web-bot-auth-ietf-status-2026</guid>
      <pubDate>Tue, 17 Nov 2026 12:00:00 GMT</pubDate>
      <category>trust</category>
      <description>Web Bot Auth is not a finished standard yet. The IETF working group adopted its protocol draft in September 2026, and the current version, draft-ietf-webbotauth-httpsig-protocol-01, is dated October 29, 2026. The charter aimed to send it for approval by April 2026, so it is running late, and early adopters such as Cloudflare and Google document different versions of the format.</description>
      <enclosure url="https://sill.so/signals/audio/web-bot-auth-ietf-status-2026.mp3" length="2777376" type="audio/mpeg" />
    </item>
    <item>
      <title>The EU AI Act and AI agents: what changes for online businesses (2026 update)</title>
      <link>https://sill.so/signals/eu-ai-act-ai-agents-merchants</link>
      <guid isPermaLink="true">https://sill.so/signals/eu-ai-act-ai-agents-merchants</guid>
      <pubDate>Tue, 17 Nov 2026 12:00:00 GMT</pubDate>
      <category>trust</category>
      <description>For many online stores, the parts of the EU AI Act most often discussed are the transparency duties in Article 50, which have applied since 2 August 2026, and the AI literacy duty in Article 4. Product search, recommendations and customer-service chat are not named in the Act's list of high-risk uses, though classification depends on each system's intended purpose, and the Digital Omnibus (Regulation (EU) 2026/1744) pushed the high-risk rules back to December 2027 and August 2028. The Act has no separate rules for AI agents; the Commission's AI Act Service Desk says, in views it calls preliminary, that the existing rules for AI systems and general-purpose AI models cover them. This is general information, not legal advice.</description>
      <enclosure url="https://sill.so/signals/audio/eu-ai-act-ai-agents-merchants.mp3" length="2975712" type="audio/mpeg" />
    </item>
    <item>
      <title>ChatGPT Wallet: what merchants need to know about agent payments</title>
      <link>https://sill.so/signals/chatgpt-wallet-what-merchants-need-to-know</link>
      <guid isPermaLink="true">https://sill.so/signals/chatgpt-wallet-what-merchants-need-to-know</guid>
      <pubDate>Tue, 17 Nov 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>ChatGPT Wallet lets a ChatGPT user's agent pay on your website with their card. OpenAI says it works with your existing checkout pages and payment forms, with no Wallet-specific integration, and that you receive a network token instead of the card number. Your business still handles the order, fulfillment, support and fraud decisions.</description>
      <enclosure url="https://sill.so/signals/audio/chatgpt-wallet-what-merchants-need-to-know.mp3" length="2160864" type="audio/mpeg" />
    </item>
    <item>
      <title>Can agents prove they're trusted without revealing who they are? Anonymous bot authentication</title>
      <link>https://sill.so/signals/anonymous-bot-auth-privacy-pass</link>
      <guid isPermaLink="true">https://sill.so/signals/anonymous-bot-auth-privacy-pass</guid>
      <pubDate>Tue, 17 Nov 2026 12:00:00 GMT</pubDate>
      <category>trust</category>
      <description>Yes, in principle. Privacy Pass, published by the IETF in 2024, lets a trusted party vouch for a visitor with a token your site can check without learning who the visitor is. Proposals to apply the same idea to AI agents and bots are still early drafts, so today the practical way for an agent to prove it is trusted is to sign its requests with Web Bot Auth, which does reveal who it is.</description>
      <enclosure url="https://sill.so/signals/audio/anonymous-bot-auth-privacy-pass.mp3" length="2299872" type="audio/mpeg" />
    </item>
    <item>
      <title>Agentic commerce in 2026: every major launch, change and shutdown</title>
      <link>https://sill.so/signals/agentic-commerce-2026-year-in-review</link>
      <guid isPermaLink="true">https://sill.so/signals/agentic-commerce-2026-year-in-review</guid>
      <pubDate>Tue, 17 Nov 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>In 2026, AI agent shopping moved from a few pilots to shared standards. Google and Shopify launched UCP, Microsoft launched Copilot Checkout, OpenAI said Instant Checkout was moving to apps and later launched ChatGPT Wallet, and Meta and Sierra released PAP 1.0. Governance also shifted: AP2 went to the FIDO Alliance, A2A joined the Agentic AI Foundation, x402 got its own foundation and MCP became stateless.</description>
      <enclosure url="https://sill.so/signals/audio/agentic-commerce-2026-year-in-review.mp3" length="3337440" type="audio/mpeg" />
    </item>
    <item>
      <title>Is your website ready for AI agents? A 2026 checklist</title>
      <link>https://sill.so/signals/agent-ready-checklist-2026</link>
      <guid isPermaLink="true">https://sill.so/signals/agent-ready-checklist-2026</guid>
      <pubDate>Tue, 17 Nov 2026 12:00:00 GMT</pubDate>
      <category>playbooks</category>
      <description>A website is ready for AI agents when agents can reach it, read it, use it and be trusted on it. That means robots.txt and firewall settings that let the agents you want in, clear pages with product data and an llms.txt map, machine-readable entry points such as an MCP server, agent card or UCP profile if you sell, and a way to verify agents and set rules for what they may buy.</description>
      <enclosure url="https://sill.so/signals/audio/agent-ready-checklist-2026.mp3" length="3226560" type="audio/mpeg" />
    </item>
    <item>
      <title>Who pays when an AI agent buys the wrong thing? Disputes and liability</title>
      <link>https://sill.so/signals/agent-chargebacks-liability</link>
      <guid isPermaLink="true">https://sill.so/signals/agent-chargebacks-liability</guid>
      <pubDate>Tue, 17 Nov 2026 12:00:00 GMT</pubDate>
      <category>trust</category>
      <description>Usually the same people as for any online card sale: the shopper can dispute the charge, the card issuer decides, and the merchant loses the money if it can't show the sale was valid. Visa's rules now say a cardholder is responsible for what a registered agent does on their behalf, but we found no card network that has published a separate dispute process for agent purchases. Keep clear records of what was ordered, approved and delivered.</description>
      <enclosure url="https://sill.so/signals/audio/agent-chargebacks-liability.mp3" length="2253696" type="audio/mpeg" />
    </item>
    <item>
      <title>How to see AI agent traffic your analytics misses</title>
      <link>https://sill.so/signals/track-ai-agent-traffic-in-analytics</link>
      <guid isPermaLink="true">https://sill.so/signals/track-ai-agent-traffic-in-analytics</guid>
      <pubDate>Mon, 16 Nov 2026 12:00:00 GMT</pubDate>
      <category>playbooks</category>
      <description>Most AI crawlers and fetchers never run the JavaScript tag that tools like GA4 rely on, and Google Analytics also filters out known bots automatically. To see AI agent traffic, look where every request is recorded: your server or hosting logs, or your CDN's bot reports such as Cloudflare AI Crawl Control. Use GA4's AI Assistant channel for the people who click through from AI answers.</description>
      <enclosure url="https://sill.so/signals/audio/track-ai-agent-traffic-in-analytics.mp3" length="2288832" type="audio/mpeg" />
    </item>
    <item>
      <title>PayPal Agent Ready and Store Sync: what merchants get</title>
      <link>https://sill.so/signals/paypal-agent-ready-store-sync</link>
      <guid isPermaLink="true">https://sill.so/signals/paypal-agent-ready-store-sync</guid>
      <pubDate>Mon, 16 Nov 2026 12:00:00 GMT</pubDate>
      <category>playbooks</category>
      <description>PayPal Agent Ready lets PayPal and Braintree merchants accept payments from AI shopping assistants without building a separate integration for each one. Store Sync shares your product catalog with AI platforms and sends orders into your existing systems, while you stay the merchant of record. PayPal announced both in October 2025 and says they are live with Perplexity and Microsoft Copilot. You get access by contacting PayPal.</description>
      <enclosure url="https://sill.so/signals/audio/paypal-agent-ready-store-sync.mp3" length="2043072" type="audio/mpeg" />
    </item>
    <item>
      <title>Klarna's Agentic Product Protocol: product data for AI agents</title>
      <link>https://sill.so/signals/klarna-agentic-product-protocol</link>
      <guid isPermaLink="true">https://sill.so/signals/klarna-agentic-product-protocol</guid>
      <pubDate>Mon, 16 Nov 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>Klarna's Agentic Product Protocol (APP) is a product-data standard announced in December 2025 that lets AI agents search products and compare offers, such as price, stock and shipping, across merchants. In practice it is an API on top of Klarna's own catalog, open to approved partners. The open draft spec on GitHub was archived in August 2026, so treat APP as a Klarna service rather than a standard your store needs to implement.</description>
      <enclosure url="https://sill.so/signals/audio/klarna-agentic-product-protocol.mp3" length="1925568" type="audio/mpeg" />
    </item>
    <item>
      <title>Google-GeminiNotebook (formerly NotebookLM): why it fetches your pages</title>
      <link>https://sill.so/signals/gemini-notebook-fetcher</link>
      <guid isPermaLink="true">https://sill.so/signals/gemini-notebook-fetcher</guid>
      <pubDate>Mon, 16 Nov 2026 12:00:00 GMT</pubDate>
      <category>spotlights</category>
      <description>Google-GeminiNotebook is the user agent Google's Gemini Notebook uses when it fetches a web page that one of its users has added as a source. Gemini Notebook is the product formerly called NotebookLM, and Google lists Google-NotebookLM as the former user agent, supported until August 2026. Google classes it as a user-triggered fetcher, which generally ignores robots.txt.</description>
      <enclosure url="https://sill.so/signals/audio/gemini-notebook-fetcher.mp3" length="2040384" type="audio/mpeg" />
    </item>
    <item>
      <title>Content-Signal in robots.txt: ai-train, ai-input and search explained</title>
      <link>https://sill.so/signals/content-signals-ai-train-ai-input</link>
      <guid isPermaLink="true">https://sill.so/signals/content-signals-ai-train-ai-input</guid>
      <pubDate>Mon, 16 Nov 2026 12:00:00 GMT</pubDate>
      <category>playbooks</category>
      <description>Content-Signal is a robots.txt line from Cloudflare that states how you want content used after it is fetched: search, ai-input (feeding AI answers) and ai-train (model training), each set to yes or no. It is a preference, not a block, and the AI crawler pages we checked do not say they follow it. Google and Anthropic have pointed instead to a separate IETF-based training signal, so use Content-Signal alongside named bot rules, not instead of them.</description>
      <enclosure url="https://sill.so/signals/audio/content-signals-ai-train-ai-input.mp3" length="2522112" type="audio/mpeg" />
    </item>
    <item>
      <title>Browserbase and Anchor Browser: the cloud browsers behind many AI agents</title>
      <link>https://sill.so/signals/browserbase-and-anchor-cloud-browsers</link>
      <guid isPermaLink="true">https://sill.so/signals/browserbase-and-anchor-cloud-browsers</guid>
      <pubDate>Mon, 16 Nov 2026 12:00:00 GMT</pubDate>
      <category>spotlights</category>
      <description>Browserbase and Anchor Browser rent out cloud browsers that AI agents and automation tools use to visit websites. Their traffic comes from many different customers, not from one company's bot. Both can sign requests with Web Bot Auth so a site can verify them, but signing is an option the customer turns on, so unsigned sessions look like ordinary browser visits.</description>
      <enclosure url="https://sill.so/signals/audio/browserbase-and-anchor-cloud-browsers.mp3" length="1756320" type="audio/mpeg" />
    </item>
    <item>
      <title>How to allow good AI agents through Cloudflare without opening the door to bad bots</title>
      <link>https://sill.so/signals/allow-ai-agents-on-cloudflare</link>
      <guid isPermaLink="true">https://sill.so/signals/allow-ai-agents-on-cloudflare</guid>
      <pubDate>Mon, 16 Nov 2026 12:00:00 GMT</pubDate>
      <category>playbooks</category>
      <description>Allow AI agents by identity, not by name. In Cloudflare, set the Agent behavior (and any Personal Agents you want) to Allow in AI Crawler and Agent access policies, and add a WAF custom rule with the Skip action for verified bots if Super Bot Fight Mode or other rules are in the way. Keep your bot protection on for everything else, and never allow traffic just because its user-agent string names a well-known agent.</description>
      <enclosure url="https://sill.so/signals/audio/allow-ai-agents-on-cloudflare.mp3" length="2249184" type="audio/mpeg" />
    </item>
    <item>
      <title>ACP in 2026: what the Agentic Commerce Protocol does now</title>
      <link>https://sill.so/signals/acp-agentic-commerce-protocol-2026</link>
      <guid isPermaLink="true">https://sill.so/signals/acp-agentic-commerce-protocol-2026</guid>
      <pubDate>Mon, 16 Nov 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>ACP, the Agentic Commerce Protocol, is an open standard for AI agents to buy from businesses. In 2026 it grew from a checkout spec into a set of building blocks: carts, product feeds, orders, payment and 3DS authentication, a discovery file and an MCP binding. It is still in beta, governed by OpenAI and Stripe with Meta on its steering committee, and most merchants will meet it through a platform such as Stripe rather than by building it.</description>
      <enclosure url="https://sill.so/signals/audio/acp-agentic-commerce-protocol-2026.mp3" length="1929984" type="audio/mpeg" />
    </item>
    <item>
      <title>What is PAP? The Personal Agent Protocol from Meta and Sierra explained</title>
      <link>https://sill.so/signals/what-is-pap-personal-agent-protocol</link>
      <guid isPermaLink="true">https://sill.so/signals/what-is-pap-personal-agent-protocol</guid>
      <pubDate>Sun, 15 Nov 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>PAP, the Personal Agent Protocol (also called Poppy), is an open standard from Meta and Sierra that defines how a shopper's personal AI agent finds a business, says who it is and who it acts for, and gets access, as a guest or signed in. It does not handle payment itself: for shopping and checkout it hands off to UCP. Version 1.0 was published on 14 November 2026.</description>
      <enclosure url="https://sill.so/signals/audio/what-is-pap-personal-agent-protocol.mp3" length="2412192" type="audio/mpeg" />
    </item>
    <item>
      <title>Should you block AI agents? Training bots vs search bots vs shopping agents</title>
      <link>https://sill.so/signals/should-you-block-ai-agents</link>
      <guid isPermaLink="true">https://sill.so/signals/should-you-block-ai-agents</guid>
      <pubDate>Sun, 15 Nov 2026 12:00:00 GMT</pubDate>
      <category>trust</category>
      <description>Not all of them, and not in the same way. Blocking AI training crawlers such as GPTBot keeps your content out of model training without hurting search, according to OpenAI and Google. Blocking AI search crawlers can keep you out of AI answers. Shopping agents act for a real customer, may not follow robots.txt, and are better handled by verifying who they are and setting rules for what they may do.</description>
      <enclosure url="https://sill.so/signals/audio/should-you-block-ai-agents.mp3" length="1851840" type="audio/mpeg" />
    </item>
    <item>
      <title>How to let AI agents buy from your Shopify store</title>
      <link>https://sill.so/signals/how-to-let-ai-agents-buy-from-your-shopify-store</link>
      <guid isPermaLink="true">https://sill.so/signals/how-to-let-ai-agents-buy-from-your-shopify-store</guid>
      <pubDate>Sun, 15 Nov 2026 12:00:00 GMT</pubDate>
      <category>playbooks</category>
      <description>To let AI agents buy from your Shopify store, check what they can see today, make your products and policies easy to read, allow the right bots in robots.txt, choose how checkout will work, and set spending limits before any agent pays. Shopify also offers its own agentic commerce tools, which you can use alongside these steps.</description>
      <enclosure url="https://sill.so/signals/audio/how-to-let-ai-agents-buy-from-your-shopify-store.mp3" length="2213952" type="audio/mpeg" />
    </item>
    <item>
      <title>Rules for AI agent orders: spending limits, holds and human review</title>
      <link>https://sill.so/signals/ai-agent-order-rules-for-merchants</link>
      <guid isPermaLink="true">https://sill.so/signals/ai-agent-order-rules-for-merchants</guid>
      <pubDate>Sun, 15 Nov 2026 12:00:00 GMT</pubDate>
      <category>playbooks</category>
      <description>Give AI agent orders their own rules: a maximum amount per order, a daily limit per customer, a list of agents you accept, and a hold for anything unusual so a person can approve or decline it. Agent platforms and payment providers already add some limits, such as Stripe's Shared Payment Token caps and AP2 mandates, but none of them know your store's risks. Default a held order to decline if nobody answers in time.</description>
      <enclosure url="https://sill.so/signals/audio/ai-agent-order-rules-for-merchants.mp3" length="2092992" type="audio/mpeg" />
    </item>
    <item>
      <title>What is A2A (Agent2Agent)? How AI agents talk to each other</title>
      <link>https://sill.so/signals/what-is-a2a-agent2agent-protocol</link>
      <guid isPermaLink="true">https://sill.so/signals/what-is-a2a-agent2agent-protocol</guid>
      <pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>A2A (Agent2Agent) is an open protocol that lets AI agents from different companies find each other, hand off work and send back results. One agent reads another agent's agent card, sends it a message, and gets back a task that moves through set states until it is done. Google created A2A in 2025, it reached a stable v1.0 in 2026, and it now sits in the Agentic AI Foundation under the Linux Foundation.</description>
      <enclosure url="https://sill.so/signals/audio/what-is-a2a-agent2agent-protocol.mp3" length="2411232" type="audio/mpeg" />
    </item>
    <item>
      <title>MCP vs A2A vs UCP: AI agent protocols compared</title>
      <link>https://sill.so/signals/mcp-vs-a2a-vs-ucp</link>
      <guid isPermaLink="true">https://sill.so/signals/mcp-vs-a2a-vs-ucp</guid>
      <pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>MCP, A2A and UCP connect different things. MCP connects an AI app to tools and data, A2A connects one AI agent to another agent, and UCP is a commerce standard that lets an agent shop and check out with a business. They are not rivals: UCP can run over MCP or A2A, and an A2A agent can use MCP behind the scenes.</description>
      <enclosure url="https://sill.so/signals/audio/mcp-vs-a2a-vs-ucp.mp3" length="2524608" type="audio/mpeg" />
    </item>
    <item>
      <title>The new MCP spec (2026-07-28): stateless servers and what changed</title>
      <link>https://sill.so/signals/mcp-2026-07-28-spec-changes</link>
      <guid isPermaLink="true">https://sill.so/signals/mcp-2026-07-28-spec-changes</guid>
      <pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>The 2026-07-28 MCP spec makes the protocol stateless. It removes sessions and the initialize handshake, so every request carries its own version and client details, and it adds a required server/discover call, cache hints on tool lists and new routing headers. Clients built only for the old handshake cannot talk to a server that supports only the new version, so most servers will need to support both eras for a while.</description>
      <enclosure url="https://sill.so/signals/audio/mcp-2026-07-28-spec-changes.mp3" length="2406624" type="audio/mpeg" />
    </item>
    <item>
      <title>Machine Payments Protocol (MPP): Stripe and Tempo's agent payment standard</title>
      <link>https://sill.so/signals/machine-payments-protocol-mpp</link>
      <guid isPermaLink="true">https://sill.so/signals/machine-payments-protocol-mpp</guid>
      <pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>The Machine Payments Protocol (MPP) is an open protocol, co-authored by Stripe and Tempo and announced on March 18, 2026, that lets an AI agent pay for an API, service or web resource inside the HTTP request itself. The server answers with HTTP 402 and its price, the agent pays and retries, and the server returns the resource with a receipt. Unlike x402, which Stripe supports for stablecoins only, MPP also covers card payments on Stripe.</description>
      <enclosure url="https://sill.so/signals/audio/machine-payments-protocol-mpp.mp3" length="2516544" type="audio/mpeg" />
    </item>
    <item>
      <title>ExaSearchBot: the signed crawler behind Exa search</title>
      <link>https://sill.so/signals/exasearchbot</link>
      <guid isPermaLink="true">https://sill.so/signals/exasearchbot</guid>
      <pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate>
      <category>spotlights</category>
      <description>ExaSearchBot is the crawler Exa uses to discover and index public web pages for Exa, a search engine and search API used by people and AI applications. Exa says every ExaSearchBot request is signed with HTTP Message Signatures under the Web Bot Auth scheme, so you can check it is genuine regardless of IP address. It follows robots.txt, and you can address it by the product token ExaSearchBot.</description>
      <enclosure url="https://sill.so/signals/audio/exasearchbot.mp3" length="2089344" type="audio/mpeg" />
    </item>
    <item>
      <title>Microsoft Copilot as a shopper: how Copilot reads and buys from stores</title>
      <link>https://sill.so/signals/copilot-shopping-agent</link>
      <guid isPermaLink="true">https://sill.so/signals/copilot-shopping-agent</guid>
      <pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate>
      <category>spotlights</category>
      <description>Microsoft Copilot mostly learns about your store through Bing search results and your Microsoft Merchant Center feed, and Bing's crawler is Bingbot. When Copilot acts on websites, Microsoft documents two Edge setups: the shopper's own browser through Browse with Copilot, or a remote Edge browser in Microsoft's cloud for some work accounts. Microsoft does not document a separate Copilot user agent, IP list or signature.</description>
      <enclosure url="https://sill.so/signals/audio/copilot-shopping-agent.mp3" length="2049600" type="audio/mpeg" />
    </item>
    <item>
      <title>Cloudflare verified bots and signed agents: what changed in July 2026</title>
      <link>https://sill.so/signals/cloudflare-signed-agents-verified-bots</link>
      <guid isPermaLink="true">https://sill.so/signals/cloudflare-signed-agents-verified-bots</guid>
      <pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate>
      <category>trust</category>
      <description>A Cloudflare verified bot is a bot or agent that Cloudflare has confirmed identifies itself honestly and behaves well. Signed agents used to be a separate category for agents that sign their requests with Web Bot Auth. Since 1 July 2026 they are part of Verified, and Cloudflare marks the difference with a Direct or Intermediary label instead.</description>
      <enclosure url="https://sill.so/signals/audio/cloudflare-signed-agents-verified-bots.mp3" length="2421504" type="audio/mpeg" />
    </item>
    <item>
      <title>Alexa for Shopping and Buy for Me: when Amazon's agent buys from your site</title>
      <link>https://sill.so/signals/alexa-for-shopping-buy-for-me</link>
      <guid isPermaLink="true">https://sill.so/signals/alexa-for-shopping-buy-for-me</guid>
      <pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate>
      <category>spotlights</category>
      <description>Buy for Me is Amazon's agentic buying feature. A shopper taps a button in Amazon's app or in Alexa for Shopping, and Amazon's AI completes the purchase on the merchant's own website using the shopper's details. It works with products listed through Amazon's Shop Direct program, which merchants can join or leave. Amazon documents user agents for Amazonbot, Amzn-SearchBot and Amzn-User, but not one for Buy for Me checkouts.</description>
      <enclosure url="https://sill.so/signals/audio/alexa-for-shopping-buy-for-me.mp3" length="2034528" type="audio/mpeg" />
    </item>
    <item>
      <title>ACP, AP2, UCP and x402: the four ways AI agents pay, compared</title>
      <link>https://sill.so/signals/ai-agent-payment-protocols-acp-ap2-ucp-x402</link>
      <guid isPermaLink="true">https://sill.so/signals/ai-agent-payment-protocols-acp-ap2-ucp-x402</guid>
      <pubDate>Sat, 14 Nov 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>ACP, AP2, UCP and x402 are four open protocols that let an AI agent pay for something. ACP (OpenAI, Stripe and Meta) and UCP (Google, Shopify and partners) are checkout standards for stores, AP2 (Google) is a way to prove a person authorised a purchase, and x402 (Coinbase) lets an agent pay for a web resource with stablecoins. For most online stores, UCP is the one to look at first.</description>
      <enclosure url="https://sill.so/signals/audio/ai-agent-payment-protocols-acp-ap2-ucp-x402.mp3" length="2199456" type="audio/mpeg" />
    </item>
    <item>
      <title>What is Know Your Agent (KYA)? A plain guide for merchants</title>
      <link>https://sill.so/signals/know-your-agent-kya</link>
      <guid isPermaLink="true">https://sill.so/signals/know-your-agent-kya</guid>
      <pubDate>Fri, 13 Nov 2026 12:00:00 GMT</pubDate>
      <category>trust</category>
      <description>Know Your Agent (KYA) is an emerging term for confirming which AI agent you are dealing with, who operates it, who it acts for and what it is allowed to do. It is not one finished standard. Skyfire, which Mastercard describes as a provider of KYA technology, leads a protocol by that name, while Visa, Mastercard and Ant International use it for a shared set of principles they began working on in September 2026.</description>
      <enclosure url="https://sill.so/signals/audio/know-your-agent-kya.mp3" length="2220000" type="audio/mpeg" />
    </item>
    <item>
      <title>How to tell if a visitor really is ChatGPT, and not something pretending</title>
      <link>https://sill.so/signals/how-to-tell-if-a-visitor-is-really-chatgpt</link>
      <guid isPermaLink="true">https://sill.so/signals/how-to-tell-if-a-visitor-is-really-chatgpt</guid>
      <pubDate>Fri, 13 Nov 2026 12:00:00 GMT</pubDate>
      <category>trust</category>
      <description>A user-agent string proves nothing, because anyone can type it. A stronger check is to match the visitor's IP address against the lists OpenAI publishes for its bots. The strongest check, for ChatGPT agent, is a cryptographic signature that your site or CDN verifies as the request arrives.</description>
      <enclosure url="https://sill.so/signals/audio/how-to-tell-if-a-visitor-is-really-chatgpt.mp3" length="2131872" type="audio/mpeg" />
    </item>
    <item>
      <title>Verifying AI bots by IP range and reverse DNS: a 2026 reference</title>
      <link>https://sill.so/signals/ai-agent-ip-ranges-reverse-dns</link>
      <guid isPermaLink="true">https://sill.so/signals/ai-agent-ip-ranges-reverse-dns</guid>
      <pubDate>Fri, 13 Nov 2026 12:00:00 GMT</pubDate>
      <category>trust</category>
      <description>Most AI bot operators publish the IP addresses their bots use, and a few also support a reverse DNS check. OpenAI, Anthropic, Perplexity, Google, Apple, Amazon, Common Crawl, DuckDuckGo and Microsoft's Bing publish IP lists; Google, Bing, Apple and Common Crawl document reverse DNS. Meta's crawler page gives no list or DNS method. Match a request's IP against the list for the exact bot it claims to be.</description>
      <enclosure url="https://sill.so/signals/audio/ai-agent-ip-ranges-reverse-dns.mp3" length="2814048" type="audio/mpeg" />
    </item>
    <item>
      <title>Claude in Chrome: what Anthropic's browser agent does on your website</title>
      <link>https://sill.so/signals/claude-in-chrome-on-your-website</link>
      <guid isPermaLink="true">https://sill.so/signals/claude-in-chrome-on-your-website</guid>
      <pubDate>Thu, 12 Nov 2026 12:00:00 GMT</pubDate>
      <category>spotlights</category>
      <description>Claude in Chrome is Anthropic's browser extension that lets Claude read, click and fill in forms on websites inside a person's own Chrome browser. Anthropic's rules say it may not make purchases, create accounts or handle card data. Anthropic does not document a user agent, IP list or signature for it, so it is not the same as ClaudeBot, Claude-User, Claude-SearchBot or the hosted Claude-Agent browser.</description>
      <enclosure url="https://sill.so/signals/audio/claude-in-chrome-on-your-website.mp3" length="2089920" type="audio/mpeg" />
    </item>
    <item>
      <title>ChatGPT agent: what it does when it visits your website</title>
      <link>https://sill.so/signals/chatgpt-agent-on-your-website</link>
      <guid isPermaLink="true">https://sill.so/signals/chatgpt-agent-on-your-website</guid>
      <pubDate>Thu, 12 Nov 2026 12:00:00 GMT</pubDate>
      <category>spotlights</category>
      <description>ChatGPT agent uses a cloud browser to read pages, click buttons and fill in forms on a person's behalf. OpenAI says it requires human review before any consequential action. It signs its requests with Web Bot Auth, with a Signature-Agent header of &quot;https://chatgpt.com&quot;, and OpenAI does not document a user agent string for it.</description>
      <enclosure url="https://sill.so/signals/audio/chatgpt-agent-on-your-website.mp3" length="2114496" type="audio/mpeg" />
    </item>
    <item>
      <title>AI agent identity: the complete guide for website owners</title>
      <link>https://sill.so/signals/ai-agent-identity-guide</link>
      <guid isPermaLink="true">https://sill.so/signals/ai-agent-identity-guide</guid>
      <pubDate>Thu, 12 Nov 2026 12:00:00 GMT</pubDate>
      <category>trust</category>
      <description>An AI agent's identity is only as strong as the check behind it. A user-agent string is a claim anyone can send, IP lists and reverse DNS prove which network a request came from, and a cryptographic signature (Web Bot Auth) proves which operator sent it. None of these tells you who the person behind the agent is, so your own rules still decide what each agent may do.</description>
      <enclosure url="https://sill.so/signals/audio/ai-agent-identity-guide.mp3" length="3032352" type="audio/mpeg" />
    </item>
    <item>
      <title>robots.txt for AI agents: which bots to allow and which to block</title>
      <link>https://sill.so/signals/robots-txt-for-ai-agents</link>
      <guid isPermaLink="true">https://sill.so/signals/robots-txt-for-ai-agents</guid>
      <pubDate>Wed, 11 Nov 2026 12:00:00 GMT</pubDate>
      <category>playbooks</category>
      <description>If you want to be found and bought from but not used for AI training, allow the search and answer bots (such as OAI-SearchBot, PerplexityBot and Claude-SearchBot) and block the training crawlers (such as GPTBot, ClaudeBot and CCBot). User-initiated fetchers like ChatGPT-User may not follow robots.txt at all, so treat the file as a request, not a lock.</description>
      <enclosure url="https://sill.so/signals/audio/robots-txt-for-ai-agents.mp3" length="2056992" type="audio/mpeg" />
    </item>
    <item>
      <title>Web Bot Auth: how AI agents sign their requests, and why it matters</title>
      <link>https://sill.so/signals/web-bot-auth-signed-agent-requests</link>
      <guid isPermaLink="true">https://sill.so/signals/web-bot-auth-signed-agent-requests</guid>
      <pubDate>Tue, 10 Nov 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>Web Bot Auth is a way for an AI agent to prove who it is. The agent signs each request with a private key, and your site (or your CDN) checks the signature against a public key the agent's operator publishes. It is stronger than trusting a user agent or an IP address, and it is still an IETF draft, not a final standard.</description>
      <enclosure url="https://sill.so/signals/audio/web-bot-auth-signed-agent-requests.mp3" length="1957248" type="audio/mpeg" />
    </item>
    <item>
      <title>Agentic commerce protocols explained: MCP, A2A, UCP, ACP, AP2, x402 and Web Bot Auth</title>
      <link>https://sill.so/signals/agentic-commerce-protocols-explained</link>
      <guid isPermaLink="true">https://sill.so/signals/agentic-commerce-protocols-explained</guid>
      <pubDate>Tue, 10 Nov 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>Agentic commerce protocols are open standards that each handle one step of an AI agent's visit or purchase. llms.txt and MCP help agents read and use your site, A2A lets agents work with other agents, UCP and ACP run checkout, AP2 proves a person approved the payment, x402 handles pay-per-request payments, Web Bot Auth proves which agent is calling, and PAP lets a shopper's personal agent say who it acts for.</description>
      <enclosure url="https://sill.so/signals/audio/agentic-commerce-protocols-explained.mp3" length="3413280" type="audio/mpeg" />
    </item>
    <item>
      <title>Perplexity Comet: what the AI browser does on your site</title>
      <link>https://sill.so/signals/perplexity-comet-on-your-website</link>
      <guid isPermaLink="true">https://sill.so/signals/perplexity-comet-on-your-website</guid>
      <pubDate>Mon, 09 Nov 2026 12:00:00 GMT</pubDate>
      <category>spotlights</category>
      <description>Comet is Perplexity's AI browser. Its built-in Comet Assistant can browse pages and take actions, such as shopping, for the person using it. Perplexity's documentation we checked lists no user agent, IP list or signature for Comet, so on your site its visits can look like an ordinary browser session rather than a declared bot like PerplexityBot or Perplexity-User.</description>
      <enclosure url="https://sill.so/signals/audio/perplexity-comet-on-your-website.mp3" length="2044416" type="audio/mpeg" />
    </item>
    <item>
      <title>How to get your products into ChatGPT shopping in 2026</title>
      <link>https://sill.so/signals/chatgpt-shopping-after-instant-checkout</link>
      <guid isPermaLink="true">https://sill.so/signals/chatgpt-shopping-after-instant-checkout</guid>
      <pubDate>Sun, 08 Nov 2026 12:00:00 GMT</pubDate>
      <category>playbooks</category>
      <description>ChatGPT now finds products through the public web, merchant product feeds and other integrations, and sends the purchase to your own site or a plugin. To show up, allow OAI-SearchBot in robots.txt, claim your business in OpenAI's Business Hub and submit a product feed. In March 2026 OpenAI said in-chat Instant Checkout was moving to apps, with ACP serving as the underlying infrastructure.</description>
      <enclosure url="https://sill.so/signals/audio/chatgpt-shopping-after-instant-checkout.mp3" length="2264544" type="audio/mpeg" />
    </item>
    <item>
      <title>How to sell in Google AI Mode and Gemini</title>
      <link>https://sill.so/signals/how-to-sell-in-google-ai-mode-and-gemini</link>
      <guid isPermaLink="true">https://sill.so/signals/how-to-sell-in-google-ai-mode-and-gemini</guid>
      <pubDate>Sat, 07 Nov 2026 12:00:00 GMT</pubDate>
      <category>playbooks</category>
      <description>Your products can appear in Google AI Mode and Gemini through your normal Merchant Center feed and a crawlable, indexed site. Letting shoppers buy without leaving Google is a separate step: it uses the Universal Commerce Protocol (UCP) and Google Pay, is open to select merchants through an interest form, and is rolling out country by country.</description>
      <enclosure url="https://sill.so/signals/audio/how-to-sell-in-google-ai-mode-and-gemini.mp3" length="1882080" type="audio/mpeg" />
    </item>
    <item>
      <title>Fake GPTBot, ClaudeBot and Googlebot: how user-agent spoofing works and how to catch it</title>
      <link>https://sill.so/signals/fake-ai-crawlers-spoofed-user-agents</link>
      <guid isPermaLink="true">https://sill.so/signals/fake-ai-crawlers-spoofed-user-agents</guid>
      <pubDate>Fri, 06 Nov 2026 12:00:00 GMT</pubDate>
      <category>trust</category>
      <description>Any program can put GPTBot, ClaudeBot or Googlebot in its user-agent string, so the name alone proves nothing. To catch requests that claim a bot name but fail verification, check the IP address against the vendor's own published list (OpenAI, Anthropic, Perplexity, Google) or run a reverse and forward DNS lookup (Google, Bing). If the check fails, treat the request as an ordinary unverified visitor.</description>
      <enclosure url="https://sill.so/signals/audio/fake-ai-crawlers-spoofed-user-agents.mp3" length="2477088" type="audio/mpeg" />
    </item>
    <item>
      <title>UCP vs ACP: which agentic checkout protocol matters for your store?</title>
      <link>https://sill.so/signals/ucp-vs-acp</link>
      <guid isPermaLink="true">https://sill.so/signals/ucp-vs-acp</guid>
      <pubDate>Thu, 05 Nov 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>UCP and ACP are both open standards that let an AI agent check out on your store while you stay the merchant of record. UCP comes from Google, Shopify and a long list of co-developers, and powers checkout in Google's AI Mode and Gemini for approved merchants. ACP was created by OpenAI and Stripe, now counts Meta as a third maintainer, and is still in beta. For most stores selling physical products, UCP is the one to look at first.</description>
      <enclosure url="https://sill.so/signals/audio/ucp-vs-acp.mp3" length="2185440" type="audio/mpeg" />
    </item>
    <item>
      <title>Copilot Checkout: how merchants sell inside Microsoft Copilot</title>
      <link>https://sill.so/signals/microsoft-copilot-checkout-merchants</link>
      <guid isPermaLink="true">https://sill.so/signals/microsoft-copilot-checkout-merchants</guid>
      <pubDate>Wed, 04 Nov 2026 12:00:00 GMT</pubDate>
      <category>playbooks</category>
      <description>Copilot Checkout lets US shoppers buy products inside Microsoft Copilot without leaving the chat, while the merchant stays the merchant of record. Shopify stores that qualify are enrolled automatically and can turn direct checkout off in the Shopify admin. Other merchants apply through Microsoft and connect a payment partner such as PayPal or Stripe, and Microsoft's current requirements include a Microsoft Merchant Center account and a product feed.</description>
      <enclosure url="https://sill.so/signals/audio/microsoft-copilot-checkout-merchants.mp3" length="1911456" type="audio/mpeg" />
    </item>
    <item>
      <title>Google-Agent: Google's AI agent fetcher, explained</title>
      <link>https://sill.so/signals/google-agent-user-agent</link>
      <guid isPermaLink="true">https://sill.so/signals/google-agent-user-agent</guid>
      <pubDate>Wed, 04 Nov 2026 12:00:00 GMT</pubDate>
      <category>spotlights</category>
      <description>Google-Agent is the user agent Google uses for AI agents hosted on its infrastructure that browse the web and take actions when a user asks. Google lists it as a user-triggered fetcher, so it generally ignores robots.txt. You can verify it against Google's user-triggered-agents.json IP list, and Google is testing Web Bot Auth signatures for it under the identity https://agent.bot.goog.</description>
      <enclosure url="https://sill.so/signals/audio/google-agent-user-agent.mp3" length="2014752" type="audio/mpeg" />
    </item>
    <item>
      <title>What is UCP? Google and Shopify's Universal Commerce Protocol explained</title>
      <link>https://sill.so/signals/what-is-ucp-universal-commerce-protocol</link>
      <guid isPermaLink="true">https://sill.so/signals/what-is-ucp-universal-commerce-protocol</guid>
      <pubDate>Tue, 03 Nov 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>UCP (Universal Commerce Protocol) is an open standard that lets AI agents discover a business, build an order and check out, without a custom integration for every store. Google announced it on 11 January 2026, co-developed with Shopify, Etsy, Wayfair, Target and Walmart. The retailer stays the seller of record, and Google uses UCP for checkout in AI Mode in Search and the Gemini app.</description>
      <enclosure url="https://sill.so/signals/audio/what-is-ucp-universal-commerce-protocol.mp3" length="1958784" type="audio/mpeg" />
    </item>
    <item>
      <title>Shopify Agentic Storefronts: how to set up ChatGPT, Google, Copilot and Meta selling</title>
      <link>https://sill.so/signals/shopify-agentic-storefronts-setup</link>
      <guid isPermaLink="true">https://sill.so/signals/shopify-agentic-storefronts-setup</guid>
      <pubDate>Tue, 03 Nov 2026 12:00:00 GMT</pubDate>
      <category>playbooks</category>
      <description>Shopify Agentic Storefronts lets your products appear, and in some channels be bought, inside AI chats: ChatGPT, Google AI Mode and Gemini, Microsoft Copilot and Meta, according to Shopify's help center. It is on by default for eligible stores. To be eligible you need products that qualify for Shopify Catalog, completed store policies and acceptance of Shopify's supplemental terms, plus each channel's own country rules. You manage it in Sales channels &gt; Agentic.</description>
      <enclosure url="https://sill.so/signals/audio/shopify-agentic-storefronts-setup.mp3" length="2553600" type="audio/mpeg" />
    </item>
    <item>
      <title>Prompt injection and AI shopping agents: what store owners should know</title>
      <link>https://sill.so/signals/prompt-injection-shopping-agents</link>
      <guid isPermaLink="true">https://sill.so/signals/prompt-injection-shopping-agents</guid>
      <pubDate>Tue, 03 Nov 2026 12:00:00 GMT</pubDate>
      <category>trust</category>
      <description>Prompt injection is when text an AI agent reads, such as a web page or a product review, contains instructions that try to make the agent act against its user. AI companies treat it as a serious, unsolved risk and screen web content and agent actions for it. Store owners should never hide instructions for agents in their pages, should moderate content customers post, and should keep firm rules on anything an agent can do on their site.</description>
      <enclosure url="https://sill.so/signals/audio/prompt-injection-shopping-agents.mp3" length="2341632" type="audio/mpeg" />
    </item>
    <item>
      <title>AP2 moves to the FIDO Alliance: what it means for agent payments</title>
      <link>https://sill.so/signals/ap2-fido-alliance-agent-payments</link>
      <guid isPermaLink="true">https://sill.so/signals/ap2-fido-alliance-agent-payments</guid>
      <pubDate>Tue, 03 Nov 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>AP2, the Agent Payments Protocol, is an open protocol Google announced in September 2025 to prove that a person really authorized an AI agent's purchase. On April 28, 2026, the FIDO Alliance announced that Google had contributed AP2 to it, alongside Mastercard's Verifiable Intent framework, and said its working groups would develop standards. For most stores, AP2 arrives through checkout standards such as UCP rather than as a separate project.</description>
      <enclosure url="https://sill.so/signals/audio/ap2-fido-alliance-agent-payments.mp3" length="2183712" type="audio/mpeg" />
    </item>
    <item>
      <title>How to let AI agents buy from your WooCommerce store</title>
      <link>https://sill.so/signals/woocommerce-ai-agents-checkout</link>
      <guid isPermaLink="true">https://sill.so/signals/woocommerce-ai-agents-checkout</guid>
      <pubDate>Sun, 01 Nov 2026 12:00:00 GMT</pubDate>
      <category>playbooks</category>
      <description>Yes, but the official routes are still arriving. WooCommerce points merchants to the Stripe extension for Stripe's Agentic Commerce Suite, and its WooCommerce AI plugin has an &quot;Enable agentic commerce&quot; setting that turns on UCP checkout services, off by default. Each AI shopping service also needs its own onboarding and payment setup, so start with accurate product data, Google Merchant Center and clear rules for agent orders.</description>
      <enclosure url="https://sill.so/signals/audio/woocommerce-ai-agents-checkout.mp3" length="2077536" type="audio/mpeg" />
    </item>
    <item>
      <title>Does your store need an MCP server? A plain-English guide</title>
      <link>https://sill.so/signals/mcp-server-for-your-store</link>
      <guid isPermaLink="true">https://sill.so/signals/mcp-server-for-your-store</guid>
      <pubDate>Sat, 31 Oct 2026 12:00:00 GMT</pubDate>
      <category>playbooks</category>
      <description>A store MCP server lets AI assistants search your products, check stock and look up orders through defined tools instead of guessing from your web pages. You may already have one: Shopify documents a UCP-based catalog and cart MCP endpoint for stores, and WooCommerce offers an MCP integration in developer preview for managing a store. Add one if you want agents to act on accurate data, and keep anything that moves money behind limits and review.</description>
      <enclosure url="https://sill.so/signals/audio/mcp-server-for-your-store.mp3" length="1981248" type="audio/mpeg" />
    </item>
    <item>
      <title>What is MCP (Model Context Protocol)? A guide for website owners</title>
      <link>https://sill.so/signals/what-is-mcp-model-context-protocol</link>
      <guid isPermaLink="true">https://sill.so/signals/what-is-mcp-model-context-protocol</guid>
      <pubDate>Thu, 29 Oct 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>MCP, the Model Context Protocol, is an open standard that lets AI applications such as Claude and ChatGPT connect to outside tools and data. A business runs an MCP server that lists what it can do, such as searching products, and an AI assistant calls those tools on a person's behalf. Anthropic introduced MCP in November 2024, and it is now hosted by the Agentic AI Foundation under the Linux Foundation.</description>
      <enclosure url="https://sill.so/signals/audio/what-is-mcp-model-context-protocol.mp3" length="1793280" type="audio/mpeg" />
    </item>
    <item>
      <title>llms.txt for online stores: what to put in it and does it work</title>
      <link>https://sill.so/signals/llms-txt-guide-for-online-stores</link>
      <guid isPermaLink="true">https://sill.so/signals/llms-txt-guide-for-online-stores</guid>
      <pubDate>Wed, 28 Oct 2026 12:00:00 GMT</pubDate>
      <category>playbooks</category>
      <description>llms.txt is a short Markdown file at yourstore.com/llms.txt that gives AI tools a map of your site: who you are, and links to your key pages and policies. It is a proposal, not a standard. Google says Google Search does not use it, and we found no OpenAI, Anthropic or Perplexity documentation saying their bots read it, so treat it as a cheap extra, not a ranking lever.</description>
      <enclosure url="https://sill.so/signals/audio/llms-txt-guide-for-online-stores.mp3" length="2501952" type="audio/mpeg" />
    </item>
    <item>
      <title>What happened to ChatGPT Instant Checkout?</title>
      <link>https://sill.so/signals/what-happened-to-chatgpt-instant-checkout</link>
      <guid isPermaLink="true">https://sill.so/signals/what-happened-to-chatgpt-instant-checkout</guid>
      <pubDate>Tue, 27 Oct 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>ChatGPT Instant Checkout let US shoppers buy from some merchants inside the chat, starting in September 2025. In March 2026 an OpenAI spokesperson, quoted by Digital Commerce 360, said Instant Checkout was moving to apps and that OpenAI was prioritizing search and product discovery. The Agentic Commerce Protocol (ACP) behind it is still maintained and in beta, now by OpenAI, Stripe and Meta.</description>
      <enclosure url="https://sill.so/signals/audio/what-happened-to-chatgpt-instant-checkout.mp3" length="2142432" type="audio/mpeg" />
    </item>
    <item>
      <title>Meta's AI crawlers: Meta-ExternalAgent, Meta-ExternalFetcher and Meta-WebIndexer</title>
      <link>https://sill.so/signals/meta-ai-crawlers-explained</link>
      <guid isPermaLink="true">https://sill.so/signals/meta-ai-crawlers-explained</guid>
      <pubDate>Tue, 27 Oct 2026 12:00:00 GMT</pubDate>
      <category>spotlights</category>
      <description>Meta documents three crawlers tied to its AI work. Meta-ExternalAgent crawls for uses such as training foundation AI models, Meta-WebIndexer improves Meta AI search results and helps Meta cite and link to your content, and Meta-ExternalFetcher fetches single links when a user asks. Each has its own robots.txt token, but Meta says Meta-ExternalFetcher may bypass robots.txt.</description>
      <enclosure url="https://sill.so/signals/audio/meta-ai-crawlers-explained.mp3" length="2025600" type="audio/mpeg" />
    </item>
    <item>
      <title>What is x402? HTTP 402 payments for AI agents, explained</title>
      <link>https://sill.so/signals/what-is-x402</link>
      <guid isPermaLink="true">https://sill.so/signals/what-is-x402</guid>
      <pubDate>Mon, 26 Oct 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>x402 is an open protocol that turns the long-unused HTTP 402 Payment Required status into a working payment step. A server answers a request with 402 and its price, the client pays (today usually in a stablecoin such as USDC) and retries, and the server returns the content. Coinbase created it, and since July 2026 it is governed by the x402 Foundation under the Linux Foundation.</description>
      <enclosure url="https://sill.so/signals/audio/what-is-x402.mp3" length="1930176" type="audio/mpeg" />
    </item>
    <item>
      <title>Visa Intelligent Commerce, Mastercard Agent Pay and Amex ACE: how card networks handle AI agents</title>
      <link>https://sill.so/signals/card-networks-ai-agents-visa-mastercard-amex</link>
      <guid isPermaLink="true">https://sill.so/signals/card-networks-ai-agents-visa-mastercard-amex</guid>
      <pubDate>Sat, 24 Oct 2026 12:00:00 GMT</pubDate>
      <category>protocols</category>
      <description>Visa, Mastercard and American Express each run a program that lets AI agents pay with a customer's card without ever seeing the card number. The agent gets a token tied to that customer and agent, the network registers which agents it trusts, and merchants can check a signature on each request to confirm a registered agent sent it. For most merchants, this arrives through their payment provider and CDN rather than a new integration.</description>
      <enclosure url="https://sill.so/signals/audio/card-networks-ai-agents-visa-mastercard-amex.mp3" length="2213472" type="audio/mpeg" />
    </item>
    <item>
      <title>Visa Trusted Agent Protocol: how merchants recognise real shopping agents</title>
      <link>https://sill.so/signals/visa-trusted-agent-protocol</link>
      <guid isPermaLink="true">https://sill.so/signals/visa-trusted-agent-protocol</guid>
      <pubDate>Thu, 22 Oct 2026 12:00:00 GMT</pubDate>
      <category>trust</category>
      <description>Visa's Trusted Agent Protocol (TAP) is a set of rules that lets a merchant recognise an AI shopping agent Visa has approved. The agent signs each request using the HTTP Message Signatures standard, says whether it is browsing or paying, and can carry optional data about the shopper and the payment. Visa announced it in October 2025, built with Cloudflare, and publishes the specification on its developer site and GitHub.</description>
      <enclosure url="https://sill.so/signals/audio/visa-trusted-agent-protocol.mp3" length="1840416" type="audio/mpeg" />
    </item>
  </channel>
</rss>
