<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Use Examples on SoftDevStudio.com</title>
    <link>https://softdevstudio.com/tags/use-examples/</link>
    <description>Recent content in Use Examples on SoftDevStudio.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 26 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://softdevstudio.com/tags/use-examples/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tokening Adds Measured Cases and Practical Grant Examples</title>
      <link>https://softdevstudio.com/tokening-adds-measured-cases-and-practical-grant-examples/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://softdevstudio.com/tokening-adds-measured-cases-and-practical-grant-examples/</guid>
      <description>&lt;p&gt;The useful question for a permission gateway is what happens when an agent tries the next thing. Tokening.net now has two measured case studies: &lt;a href=&#34;https://tokening.net/inside-the-tokening-wordpress-demo-step-by-step/&#34;&gt;a WordPress edit bounded by post, fields, use count and deadline&lt;/a&gt;, and &lt;a href=&#34;https://tokening.net/how-tokening-stops-parallel-ai-agents-from-spending-one-grant-twice/&#34;&gt;two simultaneous calls competing for one remaining use&lt;/a&gt;. They describe the disposable Docker demonstration and published release tests, rather than invented customer deployments.&lt;/p&gt;&#xA;&lt;p&gt;Two additional guides show how to apply the current permission model. &lt;a href=&#34;https://tokening.net/giving-an-editorial-ai-agent-permission-to-fix-one-article/&#34;&gt;An editorial workflow&lt;/a&gt; issues a short-lived grant for one article without handing over the WordPress account credential. &lt;a href=&#34;https://tokening.net/limiting-a-rest-maintenance-agent-to-one-record-change/&#34;&gt;A REST maintenance example&lt;/a&gt; binds a record path and permits a bounded note field. These are illustrative deployment patterns, with explicit limits around adapter argument shapes, nested JSON and uncertain upstream writes.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
