<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Jeff</title>
    <description/>
    <link>https://speakerdeck.com/jeffishar</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/jeffishar.rss"/>
    <lastBuildDate>2026-10-28 20:16:26 -0400</lastBuildDate>
    <item>
      <title>From Microservices to Multi-Agent Systems: Same APIs, New Rules</title>
      <description>Agents aren’t replacing microservices. They’re a new kind of API consumer, and they hit the same constraints: rate limiting, security, observability and failure. What changes is the unit: tokens instead of requests, delegation instead of a single caller, reasoning traces instead of plain logs. Slides from my talk at #APIDays.</description>
      <media:content url="https://files.speakerdeck.com/presentations/5ab8d9fb13864f9a92f766127807928e/preview_slide_0.jpg?41137244" type="image/jpeg" medium="image"/>
      <content:encoded>Agents aren’t replacing microservices. They’re a new kind of API consumer, and they hit the same constraints: rate limiting, security, observability and failure. What changes is the unit: tokens instead of requests, delegation instead of a single caller, reasoning traces instead of plain logs. Slides from my talk at #APIDays.</content:encoded>
      <pubDate>Thu, 29 Oct 2026 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/jeffishar/from-microservices-to-multi-agent-systems-same-apis-new-rules</link>
      <guid>https://speakerdeck.com/jeffishar/from-microservices-to-multi-agent-systems-same-apis-new-rules</guid>
    </item>
    <item>
      <title>On Behalf of Whom</title>
      <description>When a user asks an agent to do something, and that agent calls another agent, which calls an API, whose request is it by the time it arrives? We followed one request hop by hop and looked at how to keep both the user and the agent visible all the way down: delegation instead of impersonation with token exchange (RFC 8693), tokens bound to their audience with resource indicators (RFC 8707), and a human approval step with CIBA for the risky actions.</description>
      <media:content url="https://files.speakerdeck.com/presentations/677077d47e8c476daa5167cfbe17752b/preview_slide_0.jpg?41130155" type="image/jpeg" medium="image"/>
      <content:encoded>When a user asks an agent to do something, and that agent calls another agent, which calls an API, whose request is it by the time it arrives? We followed one request hop by hop and looked at how to keep both the user and the agent visible all the way down: delegation instead of impersonation with token exchange (RFC 8693), tokens bound to their audience with resource indicators (RFC 8707), and a human approval step with CIBA for the risky actions.</content:encoded>
      <pubDate>Wed, 28 Oct 2026 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/jeffishar/on-behalf-of-whom</link>
      <guid>https://speakerdeck.com/jeffishar/on-behalf-of-whom</guid>
    </item>
  </channel>
</rss>
