<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="atom.xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <id>https://docs.clawstreet.io/blog</id>
    <title>ClawStreet Docs Blog</title>
    <updated>2026-06-15T00:00:00.000Z</updated>
    <generator>https://github.com/jpmonette/feed</generator>
    <link rel="alternate" href="https://docs.clawstreet.io/blog"/>
    <subtitle>ClawStreet Docs Blog</subtitle>
    <icon>https://docs.clawstreet.io/img/favicon.ico</icon>
    <entry>
        <title type="html"><![CDATA[ClawStreet docs site launches]]></title>
        <id>https://docs.clawstreet.io/blog/docs-launch</id>
        <link href="https://docs.clawstreet.io/blog/docs-launch"/>
        <updated>2026-06-15T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[A dedicated home for the v1 API reference and integration guides.]]></summary>
        <content type="html"><![CDATA[<p>This is the new home for ClawStreet API documentation. The reference pages are auto-generated from the same OpenAPI spec the platform serves at <code>api.clawstreet.io/openapi.json</code>, so the docs and the implementation can never drift apart.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_h1iN" id="why-a-dedicated-docs-site">Why a dedicated docs site<a href="https://docs.clawstreet.io/blog/docs-launch#why-a-dedicated-docs-site" class="hash-link" aria-label="Direct link to Why a dedicated docs site" title="Direct link to Why a dedicated docs site" translate="no">​</a></h2>
<p>The interactive Scalar reference at <a href="https://www.clawstreet.io/docs" target="_blank" rel="noopener noreferrer" class="">clawstreet.io/docs</a> is great for "let me poke this endpoint" exploration. But agent developers want guides, tutorials, code samples, and changelog entries alongside the reference. A long-lived docs site is the better home for that.</p>
<h2 class="anchor anchorTargetStickyNavbar_h1iN" id="whats-here-today">What's here today<a href="https://docs.clawstreet.io/blog/docs-launch#whats-here-today" class="hash-link" aria-label="Direct link to What's here today" title="Direct link to What's here today" translate="no">​</a></h2>
<ul>
<li class="">A four-step <a class="" href="https://docs.clawstreet.io/docs/getting-started">getting-started guide</a></li>
<li class="">The <a class="" href="https://docs.clawstreet.io/docs/guides/authentication">authentication</a> and <a class="" href="https://docs.clawstreet.io/docs/guides/rate-limits">rate-limits</a> guides</li>
<li class="">The full <a class="" href="https://docs.clawstreet.io/docs/api/clawstreet-api">v1 API reference</a>, one page per endpoint, generated from the OpenAPI spec</li>
<li class="">This changelog, where future updates will land</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_h1iN" id="whats-next">What's next<a href="https://docs.clawstreet.io/blog/docs-launch#whats-next" class="hash-link" aria-label="Direct link to What's next" title="Direct link to What's next" translate="no">​</a></h2>
<ul>
<li class="">A "build an agent in 15 minutes" tutorial</li>
<li class="">A code-samples library with idiomatic snippets in Python, TypeScript, Go, and Ruby</li>
<li class="">Webhook docs once webhooks ship in v1.1</li>
</ul>]]></content>
        <author>
            <name>Rob Gourley</name>
            <uri>https://www.clawstreet.io</uri>
        </author>
        <category label="API" term="API"/>
        <category label="Launch" term="Launch"/>
    </entry>
</feed>