<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Research · Aandeg</title>
    <link>https://www.aandeg.dev/blog</link>
    <description>Research from Aandeg on how AI agents interact with websites, APIs, and tools.</description>
    <language>en-us</language>
    <lastBuildDate>Thu, 01 Oct 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://www.aandeg.dev/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Before the fetch: how AI agents discover what they can do with your site</title>
      <link>https://www.aandeg.dev/blog/before-the-fetch-agent-discovery</link>
      <guid isPermaLink="true">https://www.aandeg.dev/blog/before-the-fetch-agent-discovery</guid>
      <pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate>
      <description>Long before an agent&apos;s harness fetches your page, it already asked two other questions elsewhere - is it allowed here, and what else is available. A tour of robots.txt, Content Signals, llms.txt, .well-known, MCP, A2A, and the newer ARD discovery layer.</description>
      <author>Aandeg</author>
      <category>ai-agents</category>
      <category>agent-readiness</category>
      <category>agent-discovery</category>
    </item>
    <item>
      <title>Same prompt, different answer: how each harness defines web search and fetch</title>
      <link>https://www.aandeg.dev/blog/how-harnesses-define-web-search-and-fetch</link>
      <guid isPermaLink="true">https://www.aandeg.dev/blog/how-harnesses-define-web-search-and-fetch</guid>
      <pubDate>Sat, 26 Sep 2026 00:00:00 GMT</pubDate>
      <description>An agent&apos;s web search and web fetch tools are defined by its harness, not the model. Three harnesses, three very different implementations, and why the same prompt can land on your site differently depending on who is asking.</description>
      <author>Aandeg</author>
      <category>ai-agents</category>
      <category>agent-harnesses</category>
      <category>agent-tools</category>
    </item>
    <item>
      <title>Who&apos;s knocking? How AI agents identify themselves to websites</title>
      <link>https://www.aandeg.dev/blog/who-is-knocking-agent-identity</link>
      <guid isPermaLink="true">https://www.aandeg.dev/blog/who-is-knocking-agent-identity</guid>
      <pubDate>Thu, 24 Sep 2026 00:00:00 GMT</pubDate>
      <description>Amazon just blocked Meta&apos;s shopping agent for not identifying itself. If you run a website, the same question is already arriving at your server - who is knocking, and should you let them in?</description>
      <author>Aandeg</author>
      <category>ai-agents</category>
      <category>agent-readiness</category>
      <category>agent-identity</category>
    </item>
    <item>
      <title>The AI agent onion: what happens when an agent reads your website</title>
      <link>https://www.aandeg.dev/blog/the-ai-agent-onion</link>
      <guid isPermaLink="true">https://www.aandeg.dev/blog/the-ai-agent-onion</guid>
      <pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate>
      <description>Follow a single request from prompt to page and the layers of an AI agent reveal themselves - including the one that quietly decides whether your site exists at all.</description>
      <author>Aandeg</author>
      <category>ai-agents</category>
      <category>agent-readiness</category>
    </item>
  </channel>
</rss>
