<div class="post-category"><span class="cat-badge cat-tiers">Tiers</span></div>
<p class="lead"><strong>The Pro tier at $100 unlocks the full set of Pro-only features: crypto commands, affiliate tracking, BizBrain, and BizChannel ad marketplace access. It remains API-hosted.</strong></p>
<h2>Overview</h2>
<p>Pro is the most popular subscription tier. It is gated server-side via `@require_tier(TierLevel.PRO)` on 22+ dashboard endpoints. The bot surfaces Pro commands conditionally.</p>
<h2>Key components</h2>
<ul><li>Crypto commands (buy, top-up DZIT, check balance)</li><li>Affiliate program access</li><li>BizBrain advanced automation</li><li>BizChannel ad marketplace</li><li>5 blog posts per month</li></ul>
<h2>Related</h2>
<ul><li>[BizPlus Tier ($150)](/post.php?slug=tier-bizplus)</li><li>[BizChannel Node](/post.php?slug=bizchannel-node)</li><li>[Affiliate Incentives](/post.php?slug=affiliate-incentives)</li></ul>
Adding a new bot feature used to mean editing Python, wiring a `CommandHandler`, and redeploying. With the Feature Manifest Framework it is four steps and about ten lines of YAML — and you get a slash command and a paid network handle from
1BZ bots used to hand-wire every capability as a Python `CommandHandler`. That put even a trivial command one code change and a redeploy away from production. The Feature Manifest Framework replaces that with a declarative YAML file at `bot
Slash commands and handles are related but not identical. A slash command is the owner-facing UI inside a single bot; a handle is a network-facing service endpoint that any other bot, workflow, or API on the 1BZ network can call. The same u