<?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: Tolga Coskun</title>
    <description>The latest articles on DEV Community by Tolga Coskun (@tolga_coskun_d0aa35a068f4).</description>
    <link>https://dev.to/tolga_coskun_d0aa35a068f4</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4195704%2F9eaf7617-7b98-4a33-9edf-fec76bad2be1.png</url>
      <title>DEV Community: Tolga Coskun</title>
      <link>https://dev.to/tolga_coskun_d0aa35a068f4</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tolga_coskun_d0aa35a068f4"/>
    <language>en</language>
    <item>
      <title>Your coding agent doesn't need your real API key</title>
      <dc:creator>Tolga Coskun</dc:creator>
      <pubDate>Wed, 28 Oct 2026 01:33:19 +0000</pubDate>
      <link>https://dev.to/tolga_coskun_d0aa35a068f4/your-coding-agent-doesnt-need-your-real-api-key-oki</link>
      <guid>https://dev.to/tolga_coskun_d0aa35a068f4/your-coding-agent-doesnt-need-your-real-api-key-oki</guid>
      <description>&lt;p&gt;A post on r/ClaudeCode this week asked two good questions about coding agents and credentials:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Could the agent see a fake secret, with the real one swapped back in only on the way to the server?&lt;/li&gt;
&lt;li&gt;Could the agent reach only the hosts and calls you gave it permission for?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For any API that takes its key in a header (OpenAI, Anthropic, most SaaS and internal APIs), you can do both today with a gateway between the agent and the API. Below is what that looks like, with real output, and the parts it does not cover.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. The agent never holds the real key
&lt;/h2&gt;

&lt;p&gt;You store the real key in the gateway once. The agent gets its own gateway key instead. When the agent calls the API through the gateway, the gateway removes the agent's key and adds the real one.&lt;/p&gt;

&lt;p&gt;I ran this with Odile Gate (hosted, free for 3 agents), pointing a project at an echo server so I could see exactly what arrived on the other side. The agent only had its Gate key. This is what the "server" received:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;upstream url: https://httpbin.org/anything/chat/completions
upstream saw Authorization: Bearer sk-demo-not-real
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If that agent's key leaks, you revoke that one key. The real key, and every other agent, keep working. Rotating the real key is one admin call; the agents never see the change:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"ok"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nl"&gt;"header_name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="s2"&gt;"Authorization"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nl"&gt;"has_secret"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="err"&gt;upstream&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;saw&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;Authorization:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;Bearer&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;sk-demo-rotated&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  2. Only the calls you allowed
&lt;/h2&gt;

&lt;p&gt;Each agent gets a list of the calls it may make, for example only &lt;code&gt;POST /chat/completions&lt;/code&gt;. Anything else stops at the gateway:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="k"&gt;HTTP&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="m"&gt;2&lt;/span&gt; &lt;span class="m"&gt;403&lt;/span&gt;
&lt;span class="na"&gt;x-gate-refused&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;route_not_allowed&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For a model API you can also list the models an agent may use. Another model is refused before the provider sees the call:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="k"&gt;HTTP&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="m"&gt;2&lt;/span&gt; &lt;span class="m"&gt;403&lt;/span&gt;
&lt;span class="na"&gt;x-gate-refused&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;model_not_allowed&lt;/span&gt;
&lt;span class="na"&gt;{"error"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="s"&gt;"support-agent may not use the model gpt-5-pro","allowed":["gpt-4.1-mini"]}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And an agent stuck in a loop, sending the same request again and again, is stopped on the tenth identical call inside ten seconds:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="k"&gt;HTTP&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="m"&gt;2&lt;/span&gt; &lt;span class="m"&gt;429&lt;/span&gt;  &lt;span class="ne"&gt;x-odile-gate-loop-detected: true&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  What this does not cover
&lt;/h2&gt;

&lt;p&gt;Being straight about the limits matters more than the demo:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;AWS-style credentials.&lt;/strong&gt; AWS (and similar) sign every request with the secret, so a gateway cannot simply swap a placeholder for the real key. That needs a proxy that re-signs requests, which Gate does not do.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Any host on the internet.&lt;/strong&gt; A gateway protects the APIs you put behind it. It is not an egress firewall: it does not stop an agent from curling some other website. For that you need a network allow-list where the agent runs (a sandbox or container with outbound rules).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Data the agent already knows.&lt;/strong&gt; The tweet in that thread was about an agent putting personal data into HTTP headers because a site asked it to. A gateway cannot stop the agent sending what is already in its context to a site outside the gateway. What it does change: the real API key is not in the agent's context to begin with, so it cannot be one of the things that leaks.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Setting it up
&lt;/h2&gt;

&lt;p&gt;Three calls: a project holding the real key, one app (key) per agent with its allowed calls, then point the agent's SDK base URL at the gateway with its own key. The full guide, including Anthropic: &lt;a href="https://gate.odilelabs.com/guides/ai-model-api-key-gateway" rel="noopener noreferrer"&gt;https://gate.odilelabs.com/guides/ai-model-api-key-gateway&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Gate never stores prompts or answers; the audit log keeps the time, agent, call, status, duration, body size and a hash. Free covers 3 agents and 10,000 calls a month; Pro is $29 a month for 25 agents and 1,000,000 calls.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>security</category>
      <category>claude</category>
      <category>api</category>
    </item>
    <item>
      <title>Give every AI agent its own key to your OpenAI or Anthropic API key</title>
      <dc:creator>Tolga Coskun</dc:creator>
      <pubDate>Wed, 28 Oct 2026 01:23:25 +0000</pubDate>
      <link>https://dev.to/tolga_coskun_d0aa35a068f4/give-every-ai-agent-its-own-key-to-your-openai-or-anthropic-api-key-4gl0</link>
      <guid>https://dev.to/tolga_coskun_d0aa35a068f4/give-every-ai-agent-its-own-key-to-your-openai-or-anthropic-api-key-4gl0</guid>
      <description>&lt;p&gt;Your agents all call the model API with the same provider key. One of them gets stuck and resends the same request in a loop, another one starts asking for the most expensive model, and the key lives in five different environment files. When it leaks, every agent breaks at once.&lt;/p&gt;

&lt;p&gt;This is how to put a gateway between your agents and the provider so each agent has its own key, its own allowed calls and its own allowed models, without changing the agent code beyond its base URL.&lt;/p&gt;

&lt;h2&gt;
  
  
  The setup
&lt;/h2&gt;

&lt;p&gt;I used Odile Gate, a hosted gateway (free for 3 agents and 10,000 calls a month). Three steps.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. A project in front of the provider.&lt;/strong&gt; The provider key is stored encrypted and never handed to an agent.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-sS&lt;/span&gt; https://gate.odilelabs.com/api/projects &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s1"&gt;'content-type: application/json'&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-d&lt;/span&gt; &lt;span class="s1"&gt;'{"name":"Model API","upstream":"https://api.openai.com/v1","header_value":"Bearer '&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$PROVIDER_KEY&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="s1"&gt;'"}'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You get a project id and an admin key once.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. One app per agent&lt;/strong&gt;, with only the calls it makes, a per-minute limit and the models it may ask for:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-sS&lt;/span&gt; &lt;span class="nt"&gt;-X&lt;/span&gt; POST &lt;span class="s2"&gt;"https://gate.odilelabs.com/api/projects/&lt;/span&gt;&lt;span class="nv"&gt;$PROJECT&lt;/span&gt;&lt;span class="s2"&gt;/apps"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Authorization: Bearer &lt;/span&gt;&lt;span class="nv"&gt;$ODILE_GATE_ADMIN_KEY&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s1"&gt;'content-type: application/json'&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-d&lt;/span&gt; &lt;span class="s1"&gt;'{"name":"support-agent","routes":["POST /chat/completions"],"per_minute":60,"models":["gpt-4.1-mini"]}'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You get that agent's Gate key once.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Point the SDK at Gate&lt;/strong&gt; and give the agent its Gate key instead of the provider key:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="kn"&gt;from&lt;/span&gt; &lt;span class="n"&gt;openai&lt;/span&gt; &lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;OpenAI&lt;/span&gt;
&lt;span class="n"&gt;client&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;OpenAI&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;base_url&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;https://gate.odilelabs.com/g/&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;PROJECT&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;api_key&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;GATE_APP_KEY&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For Anthropic, create the project with &lt;code&gt;"header_name": "x-api-key"&lt;/code&gt; and pass the Gate key as &lt;code&gt;auth_token&lt;/code&gt; in the Anthropic SDK. Streaming passes straight through.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I saw when I ran it
&lt;/h2&gt;

&lt;p&gt;I pointed a test project at an echo server so I could see exactly what reached the "provider".&lt;/p&gt;

&lt;p&gt;An allowed call arrives with the real provider key, which the agent never had:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;upstream url: https://httpbin.org/anything/chat/completions
upstream saw Authorization: Bearer sk-demo-not-real
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A call the agent was not given (here &lt;code&gt;GET /models&lt;/code&gt;) never leaves Gate:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="k"&gt;HTTP&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="m"&gt;2&lt;/span&gt; &lt;span class="m"&gt;403&lt;/span&gt;
&lt;span class="na"&gt;x-gate-refused&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;route_not_allowed&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The same request body sent again and again: the first nine pass, the tenth inside ten seconds is stopped before the provider bills it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="k"&gt;HTTP&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="m"&gt;2&lt;/span&gt; &lt;span class="m"&gt;200&lt;/span&gt;  &lt;span class="ne"&gt;#1 ... #9&lt;/span&gt;
&lt;span class="s"&gt;HTTP/2 429  x-odile-gate-loop-detected: true  #10&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;An agent that asks for a model it was not given is refused before the provider sees the call:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="k"&gt;HTTP&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="m"&gt;2&lt;/span&gt; &lt;span class="m"&gt;403&lt;/span&gt;
&lt;span class="na"&gt;x-gate-refused&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;model_not_allowed&lt;/span&gt;
&lt;span class="na"&gt;{"error"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="s"&gt;"support-agent may not use the model gpt-5-pro","allowed":["gpt-4.1-mini"]}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Rotating the provider key is one call with the admin key; every agent keeps working on the new key, and the value is never returned or logged:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-sS&lt;/span&gt; &lt;span class="nt"&gt;-X&lt;/span&gt; PUT &lt;span class="s2"&gt;"https://gate.odilelabs.com/api/projects/&lt;/span&gt;&lt;span class="nv"&gt;$PROJECT&lt;/span&gt;&lt;span class="s2"&gt;/secret"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Authorization: Bearer &lt;/span&gt;&lt;span class="nv"&gt;$ODILE_GATE_ADMIN_KEY&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s1"&gt;'content-type: application/json'&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-d&lt;/span&gt; &lt;span class="s1"&gt;'{"header_value":"Bearer '&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="nv"&gt;$NEW_PROVIDER_KEY&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="s1"&gt;'"}'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"ok"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nl"&gt;"header_name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="s2"&gt;"Authorization"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nl"&gt;"has_secret"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="err"&gt;upstream&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;saw&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;Authorization:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;Bearer&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;sk-demo-rotated&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  What it does not do
&lt;/h2&gt;

&lt;p&gt;Limits count calls, not tokens or dollars, so it complements your provider's spend limits rather than replacing them. Gate never stores prompts or answers: the audit log keeps the time, agent, allowed or refused call, status, duration, body size and a hash.&lt;/p&gt;

&lt;p&gt;The full guide, with the Anthropic setup, is here: &lt;a href="https://gate.odilelabs.com/guides/ai-model-api-key-gateway" rel="noopener noreferrer"&gt;https://gate.odilelabs.com/guides/ai-model-api-key-gateway&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Pro is $29 a month for 25 agents and 1,000,000 calls a month. Your model usage stays billed by your provider as before.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>openai</category>
      <category>security</category>
      <category>api</category>
    </item>
    <item>
      <title>What AI agent crawlers read on your site (and what they never do)</title>
      <dc:creator>Tolga Coskun</dc:creator>
      <pubDate>Mon, 26 Oct 2026 09:33:18 +0000</pubDate>
      <link>https://dev.to/tolga_coskun_d0aa35a068f4/what-ai-agent-crawlers-read-on-your-site-and-what-they-never-do-p87</link>
      <guid>https://dev.to/tolga_coskun_d0aa35a068f4/what-ai-agent-crawlers-read-on-your-site-and-what-they-never-do-p87</guid>
      <description>&lt;p&gt;If you publish an MCP server or an A2A agent card, a small crowd of bots starts visiting within days. I spent a morning reading a day of our worker logs to see who they are, what they fetch, and what that means for anyone shipping agent-facing endpoints.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who shows up
&lt;/h2&gt;

&lt;p&gt;Every one of them announces itself in the User-Agent, often with a link and a promise about what it will not do:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Registries and directories&lt;/strong&gt; that list agents and MCP servers, re-checking the entries they already hold.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Liveness monitors&lt;/strong&gt; that hit the same endpoint on a fixed schedule, every few minutes, around the clock.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Trust and quality scorers&lt;/strong&gt; that read your card, check it against the spec and rank you.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Research probes&lt;/strong&gt;, including at least one academic study measuring MCP quality of service.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Onboarding probes&lt;/strong&gt; for newer agent registries that do one handshake per published endpoint.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Several say outright "read-only", "liveness-only" or "never invokes tools" in their User-Agent. They come to read, not to use.&lt;/p&gt;

&lt;h2&gt;
  
  
  What they fetch
&lt;/h2&gt;

&lt;p&gt;The same four things, over and over:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;code&gt;/.well-known/agent-card.json&lt;/code&gt;, the A2A card.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;/llms.txt&lt;/code&gt; (and sometimes &lt;code&gt;/llms-full.txt&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;MCP &lt;code&gt;initialize&lt;/code&gt;, then &lt;code&gt;tools/list&lt;/code&gt;, and stop.&lt;/li&gt;
&lt;li&gt;Newer discovery files: an AI catalog or an MCP server card under &lt;code&gt;/.well-known/&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;That is your storefront for machines. A coding agent that later decides whether to use your tool is reading the same files, or a registry's copy of them.&lt;/p&gt;

&lt;h2&gt;
  
  
  What they never do
&lt;/h2&gt;

&lt;p&gt;In our logs none of them signed up or bought anything. Crawler traffic tells you that you are indexed. It does not tell you anyone is interested. Count it separately from people and real agent calls, or it will flatter every chart you have.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this means if you ship agent endpoints
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Keep &lt;code&gt;tools/list&lt;/code&gt; cheap and free of side effects.&lt;/strong&gt; Crawlers call it all day, and nobody calling it is a user.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep the card valid and the facts current.&lt;/strong&gt; Registries copy what you publish. A stale price or a removed feature in your llms.txt lives on in other indexes after you fix the page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Answer probes fast and the same way every time.&lt;/strong&gt; Monitors mark you down for slow or flaky answers long before any person notices.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Make the first real call succeed.&lt;/strong&gt; When an agent finally tries you, the example in your tool description has to work as written. We found ours pointed at demo data that returned a 404 on the obvious first try, and fixed the hint the same day.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tag bot traffic by User-Agent before you report anything.&lt;/strong&gt; Ours turned out to be mostly monitors and our own test clients.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Our setup, for reference
&lt;/h2&gt;

&lt;p&gt;We run Odile Gate, which keeps AI agents inside the calls an API allows (per-app keys, allowed calls, approvals and an audit log). Its hosted MCP server is &lt;code&gt;https://gate.odilelabs.com/mcp&lt;/code&gt;, and an agent can create a free project there with no signup. The crawlers above read it all day; that is how we learned all of this.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>mcp</category>
      <category>agents</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Give your AI agent a phone number that answers</title>
      <dc:creator>Tolga Coskun</dc:creator>
      <pubDate>Mon, 26 Oct 2026 00:13:52 +0000</pubDate>
      <link>https://dev.to/tolga_coskun_d0aa35a068f4/give-your-ai-agent-a-phone-number-that-answers-33ef</link>
      <guid>https://dev.to/tolga_coskun_d0aa35a068f4/give-your-ai-agent-a-phone-number-that-answers-33ef</guid>
      <description>&lt;p&gt;Your agent can book, write and search. The moment a human wants to &lt;em&gt;call&lt;/em&gt; the business it works for, it has nothing to answer with. Most small-business apps hit this wall the first week: the owner forwards the shop line to a voicemail box nobody checks, and the app gets blamed for the missed jobs.&lt;/p&gt;

&lt;p&gt;Here is the shortest path I know to a real line that picks up.&lt;/p&gt;

&lt;h2&gt;
  
  
  Hear it before you build anything
&lt;/h2&gt;

&lt;p&gt;Call &lt;strong&gt;(561) 375-2995&lt;/strong&gt;. No account. The same receptionist that answers for our customers answers for us: it says it is an AI, asks whether it may record, takes your name, number and what you need, and texts the owner. It answers in 32 languages and follows whichever one you speak.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make a test line in one call
&lt;/h2&gt;

&lt;p&gt;Sign in at &lt;a href="https://odilelabs.com/developers" rel="noopener noreferrer"&gt;odilelabs.com/developers&lt;/a&gt;, make a key, then:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-X&lt;/span&gt; POST https://api.odilelabs.com/v1/test-lines &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Authorization: Bearer &lt;/span&gt;&lt;span class="nv"&gt;$ODILE_KEY&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt; &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Content-Type: application/json"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-d&lt;/span&gt; &lt;span class="s1"&gt;'{"business_name":"Bay Plumbing","trade":"plumbing"}'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You get back a shared test number and a 4-digit code (I ran this tonight through the MCP tool &lt;code&gt;try_answering_line&lt;/code&gt;; code and link blanked):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"sandbox"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"test_number"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"(561) 783-6044"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"test_code"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"____"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
 &lt;/span&gt;&lt;span class="nl"&gt;"hear_url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"https://odilelabs.com/hear/..."&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"expires_at"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"2026-10-27T00:12:06Z"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"calls_allowed"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;5&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
 &lt;/span&gt;&lt;span class="nl"&gt;"how"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Call (561) 783-6044, key the code when asked, then talk to it like a customer would. It answers as Bay Plumbing."&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Call the number, key the code, and the receptionist answers as Bay Plumbing: your business name, your trade, your hours if you set them. The test line is free, lasts 24 hours and takes 5 calls; nothing is booked, sent or charged on it.&lt;/p&gt;

&lt;p&gt;If your agent speaks MCP, skip the curl. In Claude Code:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;claude mcp add &lt;span class="nt"&gt;--transport&lt;/span&gt; http odile https://odilelabs.com/mcp
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;In Cursor, add &lt;code&gt;{"mcpServers":{"odile":{"url":"https://odilelabs.com/mcp"}}}&lt;/code&gt; to &lt;code&gt;.cursor/mcp.json&lt;/code&gt;. Then tell it to set up an answering line. Before any sign-in the server already answers &lt;code&gt;get_answering_line_offer&lt;/code&gt; (the prices below) and &lt;code&gt;get_receptionist_benchmark&lt;/code&gt; (how the receptionist scores on recorded test calls), so an agent can read the terms first.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a real line costs
&lt;/h2&gt;

&lt;p&gt;Read from the offer tool tonight, not from a pricing page:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;$0.25 a minute&lt;/strong&gt;, billed by the second, 20-second minimum, only for real answered calls.&lt;/li&gt;
&lt;li&gt;Prepaid: &lt;strong&gt;40 minutes for $10&lt;/strong&gt; or &lt;strong&gt;200 minutes for $50&lt;/strong&gt;. Nothing renews.&lt;/li&gt;
&lt;li&gt;Not charged: robocalls, calls from your own numbers or ours, website and widget chats, text messages, and calls whose transcript cannot be read.&lt;/li&gt;
&lt;li&gt;At zero the line keeps answering and the balance goes negative; the next pack pays it first. You are emailed at 5 minutes left, at zero, and at 10 minutes below zero. Nothing switches the line off on its own.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Per-minute lines are for United States businesses. The owner forwards their existing number to the new one with a carrier code from the welcome email; their number stays theirs.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it will not do
&lt;/h2&gt;

&lt;p&gt;It makes no outbound calls and runs no campaigns. Every caller hears that the line is an AI and that the call is recorded, and the line only goes further with a yes. It takes messages and books; it does not quote prices or give legal or medical advice. If that is the product you need, it is not this one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it lives
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Docs and keys: &lt;a href="https://odilelabs.com/developers" rel="noopener noreferrer"&gt;odilelabs.com/developers&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Hosted MCP server: &lt;code&gt;https://odilelabs.com/mcp&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;The same line is listed on &lt;a href="https://rapidapi.com/TOLGACOSKUN/api/after-hours-by-the-minute-ai-phone-line" rel="noopener noreferrer"&gt;RapidAPI Hub&lt;/a&gt; for teams that bill through RapidAPI.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I am Tolga, the founder. Questions go to &lt;a href="mailto:hello@odilelabs.com"&gt;hello@odilelabs.com&lt;/a&gt;; I read every one.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>api</category>
      <category>agents</category>
      <category>voice</category>
    </item>
    <item>
      <title>How an AI agent reaches a real business by its phone number</title>
      <dc:creator>Tolga Coskun</dc:creator>
      <pubDate>Sun, 25 Oct 2026 04:25:16 +0000</pubDate>
      <link>https://dev.to/tolga_coskun_d0aa35a068f4/how-an-ai-agent-reaches-a-real-business-by-its-phone-number-455a</link>
      <guid>https://dev.to/tolga_coskun_d0aa35a068f4/how-an-ai-agent-reaches-a-real-business-by-its-phone-number-455a</guid>
      <description>&lt;p&gt;Your agent can search the web, write code and fill forms. Ask it to leave a message for the plumber down the road and it stops: most small businesses have no API. What they all have is a phone number.&lt;/p&gt;

&lt;p&gt;Odile Direct makes that number addressable. An agent looks a business up by its number, reads what that business accepts, and leaves a message or books an open slot. The business gets it as a text or an email, with the person's callback number.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it in one line (no key, no card)
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-fsS&lt;/span&gt; https://odilelabs.com/m2m-quickstart.sh | sh
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It runs four tasks against a fictional demo business with an in-memory inbox and calendar: find it, check open times, book the first available slot, leave a message. Nobody is contacted and nothing is charged. Output:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;find_business_agent: task_id=... state=TASK_STATE_COMPLETED callback_check=unverified
check_availability: task_id=... state=TASK_STATE_COMPLETED callback_check=unverified
book_first_available: task_id=... state=TASK_STATE_COMPLETED callback_check=unverified
take_message: task_id=... state=TASK_STATE_COMPLETED callback_check=unverified
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Step 1: look the number up
&lt;/h2&gt;

&lt;p&gt;Lookups are free (30 an hour per IP without a key):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-s&lt;/span&gt; &lt;span class="s2"&gt;"https://api.odilelabs.com/a2a/v1/resolve?number=%2B15613752995"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"agent_card"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"https://api.odilelabs.com/a2a/v1/b/odile-labs/agent-card.json"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
 &lt;/span&gt;&lt;span class="nl"&gt;"business"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Odile Labs"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"trade"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"AI receptionist and AI agent tools"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"town"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"West Palm Beach, Florida"&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A number that isn't on the network returns nothing. A phone number alone does not mean a business takes part; your agent should say so and stop, not guess.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: read the card, then act
&lt;/h2&gt;

&lt;p&gt;The agent card lists the skills that business accepts (&lt;code&gt;take_message&lt;/code&gt;, &lt;code&gt;check_availability&lt;/code&gt;, &lt;code&gt;book&lt;/code&gt;, &lt;code&gt;book_first_available&lt;/code&gt;). Use only what the card lists. From an MCP client the same flow is two tools on the hosted server &lt;code&gt;https://odilelabs.com/mcp&lt;/code&gt;: &lt;code&gt;find_business_agent&lt;/code&gt;, then &lt;code&gt;send_to_business&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: read the result, not the HTTP status
&lt;/h2&gt;

&lt;p&gt;A 200 is not a delivered message. Read &lt;code&gt;task.status.state&lt;/code&gt;: only &lt;code&gt;TASK_STATE_COMPLETED&lt;/code&gt; is done, and a booking is confirmed only when the result says &lt;code&gt;booked: true&lt;/code&gt; with a booking id. The sending agent can fetch a signed receipt for each task at &lt;code&gt;/a2a/v1/receipts/{task_id}&lt;/code&gt; and check it at odilelabs.com/m2m/verify.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;callback_check: verified&lt;/code&gt; means the listing is verified and the callback number is valid and distinct from the business. It does not prove who owns the caller's number.&lt;/p&gt;

&lt;h2&gt;
  
  
  The rules your agent must follow
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Ask the person before every send, and show them what will be shared.&lt;/li&gt;
&lt;li&gt;Say it is an automated assistant writing for the person. Never imply a human.&lt;/li&gt;
&lt;li&gt;Use the person's own callback number, never the business's.&lt;/li&gt;
&lt;li&gt;On a timeout, don't retry on your own; reuse the same &lt;code&gt;message_id&lt;/code&gt; if the person retries.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What it costs
&lt;/h2&gt;

&lt;p&gt;Lookups and availability checks are free. Each agent gets 50 free tasks a month. After that a message is 1 credit and a booking 5; credits are 10 cents (100 for $10, 1,000 for $90), sold as one-time packs; nothing renews. Live prices are machine-readable at &lt;code&gt;https://api.odilelabs.com/a2a/v1/pricing&lt;/code&gt;. When the free tasks run out, the 402 answer lists the packs and the exact checkout call; a person approves the Stripe payment, nothing is charged without that.&lt;/p&gt;

&lt;p&gt;Not available yet, and the API says so: quotes, payment settlement, and agent-to-agent voice.&lt;/p&gt;

&lt;h2&gt;
  
  
  For businesses
&lt;/h2&gt;

&lt;p&gt;Any business can claim its number for free at odilelabs.com/direct/claim, or by calling (561) 375-2995 and asking Odile to claim the number it is calling from (a six-digit code is texted to that number), and choose whether to appear in the public directory. Messages arrive by email; businesses with a calendar-enabled line can also take bookings.&lt;/p&gt;

&lt;p&gt;Docs and OpenAPI: &lt;a href="https://odilelabs.com/m2m" rel="noopener noreferrer"&gt;https://odilelabs.com/m2m&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>mcp</category>
      <category>api</category>
      <category>agents</category>
    </item>
    <item>
      <title>How to stop an AI agent looping on your API</title>
      <dc:creator>Tolga Coskun</dc:creator>
      <pubDate>Tue, 20 Oct 2026 08:34:53 +0000</pubDate>
      <link>https://dev.to/tolga_coskun_d0aa35a068f4/how-to-stop-an-ai-agent-looping-on-your-api-1p4</link>
      <guid>https://dev.to/tolga_coskun_d0aa35a068f4/how-to-stop-an-ai-agent-looping-on-your-api-1p4</guid>
      <description>&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/9wJtsjkIwoM" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;An agent that hits an error it does not understand often retries the same call, again and again, for as long as it runs. Each call is small, so nothing alarms, but your database, your API bill and your logs fill up. Here is how to stop it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;Agents built with Claude Code, Cursor or an agent framework recover from failures by trying again. When the failure is permanent (a schema change, a missing record, a 400 they misread), trying again never works, and the agent can keep going until it runs out of turns or budget.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why rate limits miss it
&lt;/h2&gt;

&lt;p&gt;A rate limit counts calls per minute. A looping agent can stay under it: three identical calls a second is well inside a normal limit, and it is still 10,000 useless calls an hour. What gives a loop away is not volume but repetition: the same method, path, query and body, over and over, at a machine-steady pace.&lt;/p&gt;

&lt;h2&gt;
  
  
  Stop it in your code
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Cap retries per call (three is plenty) and back off between them (1 s, 2 s, 4 s).&lt;/li&gt;
&lt;li&gt;Do not retry 4xx answers except 408 and 429; they will not change.&lt;/li&gt;
&lt;li&gt;Give writes an idempotency key so a repeated POST cannot create a second order.&lt;/li&gt;
&lt;li&gt;Give every agent run a budget (calls or time) it cannot exceed.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Stop it at the gateway
&lt;/h2&gt;

&lt;p&gt;Code fixes only help code you control. An agent someone else wrote, or one that ignores its limits, still reaches your API. A gateway in front of the API catches it no matter who wrote it. &lt;a href="https://odilelabs.com/gate" rel="noopener noreferrer"&gt;Odile Gate&lt;/a&gt; does this on its free tier: each app gets its own key and an allow-list of the calls it may make, and the loop breaker stops an app that keeps sending the same call before the call reaches your API or uses your quota. The stopped call gets &lt;code&gt;429&lt;/code&gt; with &lt;code&gt;x-odile-gate-loop-detected: true&lt;/code&gt;, your webhook gets one message at once, and you can make it stricter or looser for each app.&lt;/p&gt;

&lt;h3&gt;
  
  
  Set it up in three calls
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-X&lt;/span&gt; POST https://gate.odilelabs.com/api/projects &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"content-type: application/json"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-d&lt;/span&gt; &lt;span class="s1"&gt;'{"name":"Shop API","upstream":"https://api.example.com/v1","header_name":"Authorization","header_value":"Bearer ..."}'&lt;/span&gt;

curl &lt;span class="nt"&gt;-X&lt;/span&gt; POST https://gate.odilelabs.com/api/projects/&amp;lt;project-id&amp;gt;/apps &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Authorization: Bearer &amp;lt;admin key&amp;gt;"&lt;/span&gt; &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"content-type: application/json"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-d&lt;/span&gt; &lt;span class="s1"&gt;'{"name":"claude-agent","routes":["GET /orders/:id","POST /orders"],"per_minute":60}'&lt;/span&gt;

curl &lt;span class="s2"&gt;"https://gate.odilelabs.com/g/&amp;lt;project-id&amp;gt;/orders/42"&lt;/span&gt; &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Authorization: Bearer &amp;lt;app key&amp;gt;"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Point the agent at the Gate address instead of your API, with its own key. Your real API key stays inside Gate, encrypted.&lt;/p&gt;

&lt;p&gt;One limit to know, updated: Gate checks the key, the method, the path and the limits, and since 21 October it can pin calls to the signed-in user. When the app sends that user's login token (JWT), rules like &lt;code&gt;GET /users/{user}/orders/:id&lt;/code&gt; or &lt;code&gt;GET /orders?user_id=eq.{user}&lt;/code&gt; pass only for that user's own records. Calls whose rule does not name &lt;code&gt;{user}&lt;/code&gt; are not checked per user, so row-level rules for those stay in your API.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://gate.odilelabs.com" rel="noopener noreferrer"&gt;Start free&lt;/a&gt; · &lt;a href="https://odilelabs.com/gate" rel="noopener noreferrer"&gt;How Gate works&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Free: 3 apps, 10,000 calls a month. Pro: $29 a month, 25 apps, 1,000,000 calls a month.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I work on Odile Gate.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>api</category>
      <category>security</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
