<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>APIs on Software - art</title>
		<link>https://softwareengineeringblog.com/tags/APIs/</link>
		<description>Recent content in APIs on Software - art</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
			<copyright>Laszlo Varga</copyright>
		
		
			<lastBuildDate>Thu, 08 Oct 2026 12:00:00 +0200</lastBuildDate>
		
			<atom:link href="https://softwareengineeringblog.com/tags/APIs/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Extracting a Centralized Prompt Gateway</title>
				<link>https://softwareengineeringblog.com/post/2026-10-08-extracting-a-centralized-prompt-gateway/</link>
				<pubDate>Thu, 08 Oct 2026 12:00:00 +0200</pubDate>
				<guid>https://softwareengineeringblog.com/post/2026-10-08-extracting-a-centralized-prompt-gateway/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;https://softwareengineeringblog.com/images/blog/extracting-a-centralized-prompt-gateway.webp&#34; alt=&#34;A contemporary office setup featuring computers on desks with modern flat screens.&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;Photo by &lt;a href=&#34;https://www.pexels.com/@vladimirsrajber&#34;&gt;Vladimir Srajber&lt;/a&gt; on &lt;a href=&#34;https://www.pexels.com/photo/a-flat-screen-computer-monitor-on-a-white-desk-12509206/&#34;&gt;Pexels&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;Every AI-generated reply, suggestion and document SimpleWP produces is supposed to come from one place: a single, versioned &lt;a href=&#34;https://simplewp.com&#34;&gt;SimpleWP&lt;/a&gt; prompt gateway, rather than prompt wording scattered across the codebase. This is the story of how that gateway went from technically correct to actually complete — the one caller it was never built to serve, the audit that counted what was still outside it, and the missing transport feature that turned out to be the real fix. If you&amp;rsquo;ve ever &lt;a href=&#34;https://simplewp.com/create&#34;&gt;described a site to SimpleWP&amp;rsquo;s chat assistant&lt;/a&gt;, every word of that conversation now comes from the same place this story is about.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Connecting AI Agents with MCP OAuth</title>
				<link>https://softwareengineeringblog.com/post/2026-10-08-connecting-ai-agents-with-mcp-oauth/</link>
				<pubDate>Thu, 08 Oct 2026 11:00:00 +0200</pubDate>
				<guid>https://softwareengineeringblog.com/post/2026-10-08-connecting-ai-agents-with-mcp-oauth/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;https://softwareengineeringblog.com/images/blog/connecting-ai-agents-with-mcp-oauth.webp&#34; alt=&#34;Detailed view of a backlit laptop keyboard keys with blue LED lighting for tech concepts.&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;Photo by &lt;a href=&#34;https://www.pexels.com/@castorlystock&#34;&gt;Castorly Stock&lt;/a&gt; on &lt;a href=&#34;https://www.pexels.com/photo/black-and-white-computer-keyboard-4065748/&#34;&gt;Pexels&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;An AI assistant that can act on a website needs more than an address to call. At &lt;a href=&#34;https://simplewp.com&#34;&gt;SimpleWP&lt;/a&gt;, that need led to an MCP OAuth connection for the product&amp;rsquo;s site-management tools: an authorization flow that lets &lt;a href=&#34;https://claude.ai/&#34;&gt;Claude.ai&lt;/a&gt;, &lt;a href=&#34;https://chatgpt.com/&#34;&gt;ChatGPT&lt;/a&gt; and other MCP clients reach a user&amp;rsquo;s sites by signing in and clicking Allow, the same way any other app connects to an account. This is how that MCP OAuth flow was built, from serving the tools themselves to proving the whole exchange against a real client before shipping it.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
