<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Api on Capsule One</title><link>https://capsule.one/tags/api/</link><description>Recent content in Api on Capsule One</description><generator>Hugo</generator><language>en-us</language><copyright>Capsule One B.V.</copyright><lastBuildDate>Thu, 10 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://capsule.one/tags/api/index.xml" rel="self" type="application/rss+xml"/><item><title>Make your API available</title><link>https://capsule.one/mindscape/make-your-api-available/</link><pubDate>Thu, 10 Sep 2026 00:00:00 +0000</pubDate><guid>https://capsule.one/mindscape/make-your-api-available/</guid><description>&lt;p&gt;For all the existing SaaS: It&amp;rsquo;s imperative that you spend the time to make an API available for your customers, together with its documentation.&lt;/p&gt;&#10;&lt;p&gt;MCP is nice. Skills are nice. Those are a bonus.&lt;/p&gt;&#10;&lt;p&gt;But make that API available!&lt;/p&gt;&#10;&lt;p&gt;Let your customers connect their agents to your tool WITHOUT opening their browser.&lt;/p&gt;&#10;&lt;p&gt;They need to be able to do anything they would use the web UI for and more!&lt;/p&gt;&#10;&lt;hr&gt;&#10;&lt;p&gt;&lt;em&gt;Originally posted on &lt;a href="https://x.com/RCM7/status/2098093407000465554"&gt;X&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Building for agents first</title><link>https://capsule.one/mindscape/building-for-agents-first/</link><pubDate>Sun, 06 Sep 2026 00:00:00 +0000</pubDate><guid>https://capsule.one/mindscape/building-for-agents-first/</guid><description>&lt;p&gt;As I build new tools and products, one of the first thoughts that now comes to my mind is:&lt;/p&gt;&#10;&lt;p&gt;How can I make it easy for an agent to use this?&lt;/p&gt;&#10;&lt;p&gt;Today we don’t to be convincing people to use certain tools as much as before, we need to convince their agents!&lt;/p&gt;&#10;&lt;p&gt;And it needs to be as plug and play as possible.&lt;/p&gt;&#10;&lt;p&gt;An API + set of skills (and maybe mcp) are more important than a dashboard UI.&lt;/p&gt;</description></item></channel></rss>