<?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>Routebase Blog</title>
    <link>https://routebase.dev/blog/</link>
    <description>Practical writing on API design, mocking, testing, and agent-ready APIs from the team building Routebase.</description>
    <language>en</language>
    <atom:link href="https://routebase.dev/blog/feed.xml" rel="self" type="application/rss+xml" />
    <image>
      <url>https://routebase.dev/icon.png</url>
      <title>Routebase Blog</title>
      <link>https://routebase.dev/blog/</link>
    </image>
    <lastBuildDate>Tue, 01 Sep 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>What Belongs in an API Style Guide</title>
      <link>https://routebase.dev/blog/what-belongs-in-an-api-style-guide/</link>
      <guid isPermaLink="true">https://routebase.dev/blog/what-belongs-in-an-api-style-guide/</guid>
      <pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate>
      <dc:creator>The Routebase Team</dc:creator>
      <description>Most style guides fail with too many rules, not too few. The work is not collecting rules — it is deciding which ones stop a build, which ones only leave a note, and which ones you were never going to enforce anyway.</description>
      <category>API Design</category>
      <category>Governance</category>
      <category>OpenAPI</category>
    </item>
    <item>
      <title>Writing API Descriptions an LLM Can Actually Use</title>
      <link>https://routebase.dev/blog/api-descriptions-llms-can-use/</link>
      <guid isPermaLink="true">https://routebase.dev/blog/api-descriptions-llms-can-use/</guid>
      <pubDate>Tue, 25 Aug 2026 00:00:00 GMT</pubDate>
      <dc:creator>The Routebase Team</dc:creator>
      <description>A linter can tell you a description is missing. It cannot tell you the description is useless — and that is the one an agent chokes on. What belongs in a description, what to leave out, and how to check whether it worked.</description>
      <category>AI Agents</category>
      <category>OpenAPI</category>
      <category>API Design</category>
    </item>
    <item>
      <title>Migrating from Postman to an OpenAPI-First Workflow</title>
      <link>https://routebase.dev/blog/migrating-from-postman-to-openapi-first/</link>
      <guid isPermaLink="true">https://routebase.dev/blog/migrating-from-postman-to-openapi-first/</guid>
      <pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate>
      <dc:creator>The Routebase Team</dc:creator>
      <description>The migration everyone postpones is almost entirely mechanical — and mechanical work is what agents are for. How an AI with an MCP connection imports your collections, rebuilds your assertions, and verifies its own work against your real API.</description>
      <category>OpenAPI</category>
      <category>Postman</category>
      <category>Migration</category>
    </item>
    <item>
      <title>Why Your OpenAPI Spec Drifts (and How to Catch It)</title>
      <link>https://routebase.dev/blog/why-openapi-specs-drift/</link>
      <guid isPermaLink="true">https://routebase.dev/blog/why-openapi-specs-drift/</guid>
      <pubDate>Fri, 24 Jul 2026 00:00:00 GMT</pubDate>
      <dc:creator>The Routebase Team</dc:creator>
      <description>Every API contract decays the moment it stops being enforced. The four ways specs drift from reality, why code generation doesn&apos;t save you, and how to turn your spec back into a source of truth.</description>
      <category>OpenAPI</category>
      <category>Contract Testing</category>
      <category>API Design</category>
    </item>
    <item>
      <title>Consistent Error Handling with RFC 9457 Problem Details</title>
      <link>https://routebase.dev/blog/consistent-error-handling-rfc-9457/</link>
      <guid isPermaLink="true">https://routebase.dev/blog/consistent-error-handling-rfc-9457/</guid>
      <pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate>
      <dc:creator>The Routebase Team</dc:creator>
      <description>Why every API needs exactly one error shape, how RFC 9457 Problem Details provides it, and the conventions — stable type URIs, validation extensions, safe detail fields — that make it stick.</description>
      <category>API Design</category>
      <category>Error Handling</category>
      <category>REST</category>
    </item>
    <item>
      <title>API Design Principles: A Practical Guide</title>
      <link>https://routebase.dev/blog/api-design-principles/</link>
      <guid isPermaLink="true">https://routebase.dev/blog/api-design-principles/</guid>
      <pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate>
      <dc:creator>The Routebase Team</dc:creator>
      <description>The six design decisions that make or break an API: resource modeling, naming, idempotency, pagination, error formats, and versioning — with concrete examples.</description>
      <category>API Design</category>
      <category>REST</category>
      <category>Guide</category>
    </item>
    <item>
      <title>Designing Agent-Ready APIs</title>
      <link>https://routebase.dev/blog/designing-agent-ready-apis/</link>
      <guid isPermaLink="true">https://routebase.dev/blog/designing-agent-ready-apis/</guid>
      <pubDate>Mon, 06 Jul 2026 00:00:00 GMT</pubDate>
      <dc:creator>The Routebase Team</dc:creator>
      <description>AI agents are becoming API consumers. What that changes about API design — descriptions as prompts, error messages agents can act on, and why MCP is the new integration surface.</description>
      <category>AI Agents</category>
      <category>MCP</category>
      <category>API Design</category>
    </item>
    <item>
      <title>Design-First vs. Code-First API Development</title>
      <link>https://routebase.dev/blog/design-first-vs-code-first/</link>
      <guid isPermaLink="true">https://routebase.dev/blog/design-first-vs-code-first/</guid>
      <pubDate>Fri, 03 Jul 2026 00:00:00 GMT</pubDate>
      <dc:creator>The Routebase Team</dc:creator>
      <description>Two workflows for building APIs, and why the order you write the contract in changes everything downstream: parallel work, review quality, and drift.</description>
      <category>API Design</category>
      <category>Workflow</category>
      <category>OpenAPI</category>
    </item>
    <item>
      <title>Versioning APIs Without Breaking Your Consumers</title>
      <link>https://routebase.dev/blog/api-versioning-without-breaking-consumers/</link>
      <guid isPermaLink="true">https://routebase.dev/blog/api-versioning-without-breaking-consumers/</guid>
      <pubDate>Wed, 01 Jul 2026 00:00:00 GMT</pubDate>
      <dc:creator>The Routebase Team</dc:creator>
      <description>What actually counts as a breaking change, why additive evolution beats version bumps, and how to run a deprecation your consumers will forgive.</description>
      <category>API Design</category>
      <category>Versioning</category>
      <category>Breaking Changes</category>
    </item>
  </channel>
</rss>
