The latest articles on DEV Community by Okafor Francis (@majesticfranc). https://dev.to/majesticfranc 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%2F4020112%2F96c6407e-c595-4831-9887-ac09aaf48a19.jpg https://dev.to/majesticfranc en Okafor Francis Tue, 07 Jul 2026 19:34:00 +0000 https://dev.to/majesticfranc/building-sluice-a-settlement-layer-for-the-agent-paid-web-55op https://dev.to/majesticfranc/building-sluice-a-settlement-layer-for-the-agent-paid-web-55op <p>The web was designed around human visitors, subscriptions and advertising.</p> <p>AI agents operate differently.</p> <p>They search, retrieve, compare, cite, call APIs, process media and make decisions continuously. In many cases, they consume valuable work without a direct payment relationship with the person or service that produced it.</p> <p>That led me to a simple question:</p> <blockquote> <p>What happens when AI agents become paying customers of the web?</p> </blockquote> <p>I built <strong>Sluice</strong> to explore that question.</p> <p>Sluice is a settlement layer for the agent-paid web. It lets creators price the smallest useful unit of their work, while AI agents decide what is worth purchasing and pay for it automatically in USDC.</p> <p>A unit could be:</p> <ul> <li>one citation;</li> <li>one article read;</li> <li>one API request;</li> <li>one second of a stream;</li> <li>one minute of audio;</li> <li>one dataset query;</li> <li>one agent-provided service.</li> </ul> <p>The application is currently running on Arc testnet and uses x402-compatible payment flows with Circle Gateway-style nanopayment settlement.</p> <h2> The problem with the current web </h2> <p>Creators and developers already produce the resources AI agents depend on:</p> <ul> <li>articles and research;</li> <li>structured datasets;</li> <li>APIs;</li> <li>podcasts and transcripts;</li> <li>video;</li> <li>market data;</li> <li>software services;</li> <li>specialist analysis.</li> </ul> <p>However, most monetization systems were built for humans.</p> <p>Subscriptions require long-term commitment. Advertisements require attention. Traditional checkout flows introduce too much friction for a tiny purchase. Normal payment rails are also poorly suited to extremely small and frequent transactions.</p> <p>An agent may only need one paragraph from an article or one response from an API.</p> <p>Charging a monthly subscription for that interaction is excessive. Processing an individual card payment for a fraction of a cent is impractical.</p> <p>Sluice approaches the problem from the unit level:</p> <blockquote> <p>If an action can be counted, it can be priced.</p> </blockquote> <h2> The core Sluice flow </h2> <p>Sluice connects two sides of a small digital economy.</p> <h3> The creator side </h3> <p>A creator or provider can register a resource, choose its measurable unit and set a price.</p> <p>Examples include:</p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code> text Article citation $0.001 per citation API endpoint $0.003 per request Audio stream $0.0002 per second Research dataset $0.01 per query Agent service $0.10 per completed task </code></pre> </div> ai web3 typescript payments