<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Pedro Teixeira</title>
    <description>The latest articles on DEV Community by Pedro Teixeira (@pgte).</description>
    <link>https://dev.to/pgte</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2603038%2F6954f79f-3ac7-44e2-a4f3-179b9bfe133d.jpg</url>
      <title>DEV Community: Pedro Teixeira</title>
      <link>https://dev.to/pgte</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/pgte"/>
    <language>en</language>
    <item>
      <title>Subscription-Based API Throttling Without Client API Keys</title>
      <dc:creator>Pedro Teixeira</dc:creator>
      <pubDate>Thu, 12 Feb 2026 09:54:03 +0000</pubDate>
      <link>https://dev.to/pgte/subscription-based-api-throttling-without-client-api-keys-310n</link>
      <guid>https://dev.to/pgte/subscription-based-api-throttling-without-client-api-keys-310n</guid>
      <description>&lt;p&gt;How to implement tiered API throttling in AWS API Gateway using subscriptions, without requiring clients to send or manage API keys. Learn how to map subscriptions to usage plans with a custom Lambda authorizer for seamless and secure rate limiting.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://metaduck.com/subscription-based-api-throttling-without-client-api-keys/" rel="noopener noreferrer"&gt;Read more 👉&lt;/a&gt;&lt;/p&gt;

</description>
      <category>infrastructureascode</category>
      <category>aws</category>
      <category>saas</category>
    </item>
    <item>
      <title>How We Give AI Agents Long-Term Memory Without Blowing the Budget</title>
      <dc:creator>Pedro Teixeira</dc:creator>
      <pubDate>Mon, 09 Feb 2026 10:09:10 +0000</pubDate>
      <link>https://dev.to/pgte/how-we-give-ai-agents-long-term-memory-without-blowing-the-budget-3ib1</link>
      <guid>https://dev.to/pgte/how-we-give-ai-agents-long-term-memory-without-blowing-the-budget-3ib1</guid>
      <description>&lt;p&gt;Giving agents long-term memory is hard: context windows are limited, storing every raw message is expensive, and retrieval has to be both fast and relevant. We solved this with a time-stratified design: organize memory by temporal grain, summarize progressively, and pair it with a graph-based knowledge base for structured facts. &lt;/p&gt;

&lt;p&gt;Read more: &lt;a href="https://metaduck.com/how-we-give-ai-agents-long-term-memory-without-blowing-the-budget/" rel="noopener noreferrer"&gt;https://metaduck.com/how-we-give-ai-agents-long-term-memory-without-blowing-the-budget/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
    </item>
    <item>
      <title>Embedding an All-Seeing AI Agent in your web app</title>
      <dc:creator>Pedro Teixeira</dc:creator>
      <pubDate>Mon, 16 Jun 2025 16:43:00 +0000</pubDate>
      <link>https://dev.to/pgte/embedding-an-all-seeing-ai-agent-in-your-web-app-41hn</link>
      <guid>https://dev.to/pgte/embedding-an-all-seeing-ai-agent-in-your-web-app-41hn</guid>
      <description>&lt;p&gt;Instead of building a complex API surface for your &lt;strong&gt;AI agent&lt;/strong&gt;, make it interact with your app like a human user would. &lt;strong&gt;Use the Accessibility Object Model (AOM) to give your agent “eyes” to see the UI and “hands” to interact with it&lt;/strong&gt;. This approach is simpler, more maintainable, and has the bonus of making your app more accessible for screen readers.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://metaduck.com/embedding-an-all-seeing-ai-agent/" rel="noopener noreferrer"&gt;Read on&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>a11y</category>
      <category>webdev</category>
      <category>automation</category>
    </item>
  </channel>
</rss>
